RE: no overall type in Extended Attributes

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

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?

> 
> >  I guess it does seem
> > that the extended attributes should be able to handle this situation,
> fixing
> > one of the inadequacies (IMHO) of legacy RADIUS attributes, but right
> now
> > they can't.  Any suggestions for fixing this problem (as painlessly
> as
> > possible :-)?
> 
>   Painlessly killing RADIUS has been off of the table for a while.

Who's talking about "killing RADIUS"?  Do we have differing definitions of a
"dead" protocol?

> We're stuck with painful solutions.
> 
>   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/>