Re: Status of Issue 278

[Alan DeKok <aland@deployingradius.com>]

Bernard Aboba wrote:
> During the RADEXT WG last call on the RADIUS Extended Attributes draft,
> you filed Issue 278:
> http://www.drizzle.com/~aboba/RADEXT/
>  
> The editor of the document, Glen Zorn, has now listed Issue 278 as
> resolved.  However, before
> closing this issue, we wanted to get your consent.   Please send a note
> to the RADEXT WG
> mailing list indicating whether Issue 278 is in fact resolved to your
> satisfaction,

  The latest version of the draft addresses most of my comments.  The
remaining issue that should be addressed is:

---
8.  IANA Considerations
...
   It also requires that IANA set up a new registry for the RADIUS
   Extended Attribute Types.

  I suggest leaving the first 0..255 attributes as unallocated, in order
to avoid confusion with legacy RADIUS attributes.
---

  Without this text, IANA may allocate 0..255 to the new extended-type,
potentially confusing people with conflicts between that and the
standard attribute space.

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