RE: Strawman RADIUSEXT WG charter

[Avi Lior <avi@bridgewatersystems.com>]

Hi Greg,
I am readying an individual submission for AVP extension which could address
your length extension issue.  Take a look at
http://www.lior.org/standards/ietf/radiusext/draft-lior-radius-attribute-typ
e-extension-00-1.rtf

In my proposal if we make the extended attribute length 2 octets then if
Extended Attribute is longer then its container (the specail RADIUS VSAs)
then the attribute would span multiple consecutive VSAs.

Will that work for you?  I would apperciate any comments on this document.

I will be sumitting it shortly.

> -----Original Message-----
> From: Greg Weber [mailto:gdweber@cisco.com] 
> Sent: Wednesday, August 20, 2003 9:59 AM
> To: aboba@internaut.com
> Cc: radiusext@ops.ietf.org
> Subject: Re: Strawman RADIUSEXT WG charter

> > 
> > - Attribute space extension.  The RADIUS protocol, defined in
> >   RFC 2865, has an eight (8) bit attribute space, a good portion
> >   of which has already been allocated or is in use.  In order to
> >   address attribute exhaustion, an extended attribute space will be
> >   defined.
> 
> Will this work item include addressing the attribute size 
> limitation in the extended space?  A number of methods 
> for fragmenting large values across attributes have popped 
> up, e.g. as in the PacketCable 1.0 spec.  It would be nice 
> to have a standard way of doing this.
> 
> Greg
epaid capabilities.

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