RE: Issue 272 resolution

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

Bernard Aboba [mailto:Bernard_Aboba@hotmail.com] writes:

> > I was sure the idea was brought up on this list, too.  What was the
> > result of that discussion?
> 
> The result of that discussion was not to go forward with it.

Just to refresh the memory, the idea in question was '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'.  As I pointed
out in a previous message, both RFC 2865 VSAs and the current extended
attribute draft also allow this, just in a (perhaps predictably) half-assed
fashion: instead of (for example) defining & referring to an Extended
Attribute called MS-CHAP-CPW-2 which encapsulates various TLVs corresponding
to Old-NT-Hash, Old-LM-Hash, etc. one would either a) define a bunch of new
Extended Attributes corresponding to the fields in the MS-CAP-CPW-2
attribute and refer to it as the set of extended attributes containing the
same (unknown, run-time assigned) value in the Tag field or b) merely
replicate the RFC 2548 definition of MS-CHAP-CPW-2 with an Extended
Attribute header.  The latter approach, of course, forces the continued use
of the so-called "complex" Attributes that Alan (?!) so reviles in
http://www.ietf.org/internet-drafts/draft-ietf-radext-design-05.txt, while
the former forces the receiver to grovel through the entire message to find
the tagged attributes, check that all are present and check the validity of
each instead of just checking the validity of a single attribute.  I love
this idea!  Certainly far better to accept it than tamper with WG Consensus
(which apparently has become as holy as "backward compatibility" in this WG.
In any case, I'm not married to this solution; I've repeatedly requested
suggestions for a solution to the problem but nobody else has brought any
forward.  



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