Subject: draft-ietf-disman-script-mib-08.txt (changes)

From: Juergen Schoenwaelder <[email-masked]>
Date: Tue, 23 Feb 1999 11:02:51 +0100

I just submitted another ID of the script MIB. As a "belated" IETF
Last Call comments, we found two data type / range inconsistencies in
draft-ietf-disman-script-mib-07.txt:
 
> 1) smLaunchRunIndex : Unsigned32 (1..4294967295)
>    smLaunchRunIndexNext : Unsigned32
>    smLaunchStart : Integer32 (0..2147483647)
>
>    Note that smLaunchStart should be Integer32 in order to let the
>    scheduling MIB "push the button". smLaunchRunIndexNext can
>    currently return values that can not be used to launch a script
>    and it might even return a value which is illegal for
>    smLaunchRunIndex.
 
> 2) smLangIndex : Unsigned32 (1..4294967295)
>    smScriptLanguage : Integer32 (0..2147483647)
>
>    This means that you can have languages you can not refer to.

These two problems were fixed by going back to the data types / ranges
we had in draft-ietf-disman-script-mib-03.txt:

a) smLangIndex : Integer32 (1..2147483647)
   smExtsnIndex : Integer32 (1..2147483647)
   smScriptLanguage : Integer32 (0..2147483647)

b) smLaunchStart : Integer32 (0..2147483647)
   smLaunchRunIndexNext : Integer32 (1..2147483647)
   smLaunchRunIndex : Integer32 (1..2147483647)

These data types / ranges are consistent and the ranges are still
large enough for the foreseeable future. Nothing else was changed in
the ID (except some administrative things). I expect that this is
really the last ID before Proposed Standard...
							Juergen
-- 
Juergen Schoenwaelder  [email-masked] http://www.cs.tu-bs.de/~schoenw
Technical University Braunschweig, Dept. Operating Systems & Computer Networks
Bueltenweg 74/75, 38106 Braunschweig, Germany.        (Tel. +49 531 / 391 3289)