[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Consideration of draft-lior-radius-attribute-type-extension-02.txt
Glen Zorn writes...
> [gwz] Everything it says is specific to the existing standard
> attributes. For example: "Attribute Types have a range from 1 to
> 255, and are the scarcest resource in RADIUS, thus must be allocated
> with care." The Extended Attribute scheme provides an essentially
> unlimited type range. Similarly, I can't think of any good reason
> why Extended Attributes need to be allocated by "IETF Consensus"
> instead of "Specification Required".
On first consideration, that seems reasonable.
That being the case, this draft needs to include an IANA Considerations
section that specifies the code-point allocation policy for Extended RADIUS
Attributes that we expect IANA to use going forward.
--
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/>