RE: no overall type in Extended Attributes

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

Alan DeKok [mailto:aland@deployingradius.com] writes:

> Glen Zorn wrote:
> > Alan DeKok [mailto:aland@deployingradius.com] writes:
> >
> >> Glen Zorn wrote:
> >>> OK, so I've run into a situation when working on a set of
> attributes
> >> for
> >>> WiMAX that just begs for a named, multi-TLV attribute.
> >>   Could you be more specific?
> >
> > About what?
> 
>   A named, multi-TLV attribute.

Maybe I didn't say it correctly.  I want to name a group of TLVs, I guess.
to get a structure like that of, say the MS-CHAP-CPW-1 Attribute only using
the TLV construct,

> 
>   Most attributes have names.  Most attributes are TLV's.  The
> Extended-Attribute encapsulates multiple TLV's.
> 
>   So... what's a "named, multi-TLV attribute"?  An attribute inside of
> the Extended-Attribute that can carry other TLV's?  Like what's done in
> WiMAX?

Maybe, I'm open; that's why I asked :-).

> 
>   It's a good idea.  And if most vendors have to add WiMAX support
> anyways, much of the code will already exist.
> 
>   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/>