overview comments RFC3576 MIBs received until now

[stefaan.de_cnodder@alcatel.be]

Hi,

The RFC3576 MIBs are currently in IETF last call, so far there are 2 
comments that will be included in the next version of the draft when the 
last call is finished. An overview:

* draft-ietf-dynauth-client-mib-06.txt

1) issue 193: change SYNTAX of radiusDynAuthServerClientPortNumber from 
"InetPortNumber" to "InetPortNumber (1..65535)"

   radiusDynAuthServerClientPortNumber OBJECT-TYPE
          SYNTAX     InetPortNumber (1..65535)
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
                "The UDP destination port that the RADIUS Dynamic
                 Authorization Client is using to send requests to this
                 server. The value zero is invalid."
          ::= { radiusDynAuthServerEntry 4 }

2) remove radiusDynAuthClientCounterDiscontinuity as a scaler and put it 
as last attribute in the table. Description has been updated slightly as 
well as a small update in the conformance statement to reflect the move 
of this attribute into the table. Also a small update of the overview 
section that describes high level the scalars and table.

   radiusDynAuthClientCounterDiscontinuity OBJECT-TYPE
          SYNTAX TimeTicks
          UNITS  "hundredths of a second"
          MAX-ACCESS read-only
          STATUS current
          DESCRIPTION
                "The time (in hundredths of a second) since the
                 last counter discontinuity. A discontinuity may
                 be the result of a reinitialization of the DAC
                 module within the managed entity."
          ::= { radiusDynAuthServerEntry 32 }

3) update date of draft and also inside the MIB

* draft-ietf-dynauth-server-mib-06.txt

1) remove radiusDynAuthServerCounterDiscontinuity as a scaler and put it 
as last attribute in the table. Description has been updated slightly as 
well as a small update in the conformance statement to reflect the move 
of this attribute into the table. Also a small update of the overview 
section that describes high level the scalars and table.

   radiusDynAuthServerCounterDiscontinuity OBJECT-TYPE
          SYNTAX TimeTicks
          UNITS  "hundredths of a second"
          MAX-ACCESS read-only
          STATUS current
          DESCRIPTION
                "The time (in hundredths of a second) since the
                 last counter discontinuity. A discontinuity may
                 be the result of a reinitialization of the DAS
                 module within the managed entity."
          ::= { radiusDynAuthClientEntry 27 }

2) update date of draft and also inside the MIB

regards,

Stefaan

--
to unsubscribe send a message to radiusext-request@ops.ietf.org with
the word 'unsubscribe' in a single line as the message text body.
archive: <http://psg.com/lists/radiusext/>