[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 272 resolution

Glen Zorn wrote:
> Look at RFC 2548, in particular the MS-CHAP*-Response, MS-CHAP-CPW-?, etc.
> attributes.  Those are perfect examples of what cannot be done with Extended
> Attributes as currently defined.  

  They can be carried in legacy RADIUS.  The extended types are just
legacy RADIUS attributes with 16-bit types.

  Or do you mean de-capsulating the contents of the MS-CHAP-* attributes
into multiple attributes?  e.g. MS-CHAP(foo=1, bar=2, ...)  3GPP does
this, WiMAX does this.

  I was sure the idea was brought up on this list, too.  What was the
result of that discussion?

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