RE: REMINDER: RADEXT WG last call on RFC 3576 MIBs

["Romascanu, Dan \(Dan\)" <dromasca@avaya.com>]

Here are my comments:

              draft-ietf-radext-dynauth-client-mib-02.txt

1. It would help to expand RADIUS in the Abstract and to add an
appropriate Informative Reference
2. The first paragraph in Section 3 includes a repeated sentence
3. As 2619bis and 2621bis will be supersets and will obsolete 2619 and
2621, I do not believe that there is any need for the older documents to
be referenced.
4. No need to list in the Security Consideration section the MIB objects
that are considered as non-vulnerable. These are by default all objects,
but the ones listed as potentially vulnerable. 


              draft-ietf-radext-dynauth-server-mib-02.txt

1. It would help to expand RADIUS in the Abstract and to add an
appropriate Informative Reference
2. As 2618bis and 2620bis will be supersets and will obsolete 2618 and
2620, I do not believe that there is any need for the older documents to
be mentioned in section 3 and referenced.
3. No need to list in the Security Consideration section the MIB objects
that are considered as non-vulnerable. These are by default all objects,
but the ones listed as potentially vulnerable. 

The documents are in god shape. In my opinion, they may be forwarded to
the IESG for consideration as Informational, with a note including the
known editorial problems. 

Regards,

Dan



 
 

> -----Original Message-----
> From: owner-mreview@ops.ietf.org 
> [mailto:owner-mreview@ops.ietf.org] On Behalf Of Wijnen, Bert (Bert)
> Sent: Sunday, November 06, 2005 6:33 PM
> To: Mreview (E-mail)
> Subject: FW: REMINDER: RADEXT WG last call on RFC 3576 MIBs
> 
> Here are 2 other MIB documents in that WG to review.
> 
> Bert
> 
> -----Original Message-----
> From: owner-radiusext@ops.ietf.org
> [mailto:owner-radiusext@ops.ietf.org]On Behalf Of Bernard Aboba
> Sent: Wednesday, November 02, 2005 17:00
> To: radiusext@ops.ietf.org
> Subject: REMINDER: RADEXT WG last call on RFC 3576 MIBs
> 
> 
> This is a reminder of an RADEXT WG last call in progress on 
> the RFC 3576 MIBs.  These documents are being considered for 
> publication as Informational RFCs. The documents are 
> available for inspection here:
> 
> http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-
> client-mib-02.txt
> http://www.ietf.org/internet-drafts/draft-ietf-radext-dynauth-
> server-mib-02.txt
> 
> RADEXT WG last call will last until Monday, November 14, 
> 2005. Please send comments to the RADEXT WG mailing list 
> (radiusext@ops.ietf.org) in the format described in the 
> RADEXT Issues list:
> 
> http://www.drizzle.com/~aboba/RADEXT/
> 
> If you have read the documents, please respond to this WG 
> Last Call, if only to say "I have read the documents and I am 
> OK with them."
> 
> 
> 
> --
> 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/>
> 
> 

--
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/>