Re: Issues with draft-ietf-radext-extended-attributes-05.txt

[Alan DeKok <aland@deployingradius.com>]

Bernard Aboba wrote:
> There are multiple issues here, I think:
> 
> a. Whether existing implementations will have a problem with a vendor-id
> of zero, regardless of the size of the type code space, and the attribute
> numbering;  

  I can think of at least one that does.  I'm not sure anyone else is
going to admit that their implementation is less than perfect. :)

> b. Whether the *combination* of a vendor-id of zero along with attribute
> usage 1-255 can cause problems; 
>
> If we have problem a, then the fix would be to assign the IETF a non-zero
> Vendor-Id; merely prohibiting attributes 1-255 would not do the trick. 
> 
> If we only have problem b, then we could prohibit attributes 1-255 from
> being assigned. 

  That would be the solution with the minimum changes.

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