Re: REMINDER: RADEXT WG last call on RFC 2618bis-2621bis
"Alan DeKok" <aland@ox.org> Wed, 09 November 2005 21:26 UTC
Envelope-to: radiusext-data@psg.com
Delivery-date: Wed, 09 Nov 2005 21:23:36 +0000
From: Alan DeKok <aland@ox.org>
To: radiusext@ops.ietf.org
Subject: Re: REMINDER: RADEXT WG last call on RFC 2618bis-2621bis
Date: Wed, 09 Nov 2005 16:26:28 -0500
Message-Id: <20051109212628.239ED17122@mail.nitros9.org>
"Bernard Aboba" <bernard_aboba@hotmail.com> wroteL > http://www.ietf.org/internet-drafts/draft-ietf-radext-rfc2618bis-01.txt There's a typo on Page 12, radiusAuthServerInetAddress ... the version neutral IP adddess format." ^ The same typo exists in rfc2619bis page 14, rfc2620bis page 11, and rfc2621bis page 13. rfc2619bis, radiusAuthServConfigReset has MAX-ACCESS of read-write. Yet the "Security Considerations" section says: There are no management objects defined in this MIB that have a MAX- ACCESS clause of read-write and/or read-create. This text should be updated to reflect the MAX-ACCESS clause in radiusAuthServConfigReset. rfc2621bis has the same issue. I suggest re-using the text from the first paragraph of RFC 2619, section 6. Other than that, the documents look OK. Alan DeKok. -- 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/>
- RE: REMINDER: RADEXT WG last call on RFC 2618bis-… Romascanu, Dan (Dan)
- Re: REMINDER: RADEXT WG last call on RFC 2618bis-… Alan DeKok
- REMINDER: RADEXT WG last call on RFC 2618bis-2621… Bernard Aboba