RE: Issue 278

["D. B. Nelson" <d.b.nelson@comcast.net>]

> Issue 278 -- The remaining portion of this issue relates to whether
> IANA can allocate Extended Attributes 0-255, and if by doing so, 
> confusion would be created with respect to existing RADIUS attributes.

> In general, we have not seen confusion relating to use of VSAs with
> Type Code values which overlap the standards range (which most do).

I think that Extended Attributes (for implementations which _know_ that they
_are_ Extended Attributes) are clearly not the same thing as Vendor Specific
Attributes.  Assuming that VSA rules and practices apply to Extended
Attributes is probably not the best way to go.   Carving out a reservation
for the legacy codes of 0-255 seems reasonable, especially in light of the
extended type code field.



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