RE: Extended attributes support for structured data (was RE: Consideration of draft-lior-radius-attribute-type-extension-02.txt)

["Glen Zorn" <glenzorn@comcast.net>]

-----Original Message-----
From: owner-radiusext@ops.ietf.org [mailto:owner-radiusext@ops.ietf.org] On
Behalf Of David B. Nelson
Sent: Tuesday, August 28, 2007 12:24 PM
To: radiusext@ops.ietf.org
Subject: Extended attributes support for structured data (was RE:
Consideration of draft-lior-radius-attribute-type-extension-02.txt)

Glen Zorn writes...

> Actually, it does (as illustrated in the examples), it's just not
> very explicit about it.

Right.  I certainly missed it.

> ...the problem with "subattributes" as described in RFC 2865 is
> that they must fit in a single VSA.  With this draft, we open up 
> the possibility (with the "continuation" bit) of having really huge
> attributes containing subattributes that themselves are larger than
> a single VSA.  It seems like we either need to restrict the usage
> of subattributes or decide on one or the other.

One or the other what?  Could you please elaborate?
[gwz] 
Sorry, either really big attributes w/really big subattributes or grouped
attributes.  They seem to both serve the same purpose.



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