RE: Consideration of draft-lior-radius-attribute-type-extension-02.txt

["Avi Lior" <avi@bridgewatersystems.com>]

> The Extended Attribute scheme provides an essentially 
> unlimited type range.

The extended-type is 8 bits.  Hardly "essentially unlimited"

Unlimited in the sense that we can use new Vendor-Ids.


-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org]
On Behalf Of David B. Nelson
Sent: Thursday, September 06, 2007 4:51 PM
To: radiusext@ops.ietf.org
Subject: 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/>

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