Re: REMINDER: RADEXT WG last call on RFC 2618bis-2621bis

["Alan DeKok" <aland@ox.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/>