RE: FW: HTTP digest and RADIUS; new version of the Sterman draft

[Bernard Aboba <aboba@internaut.com>]

> If tagged attributes are sufficient, then I see no reason to add new
> sub-types.

Note that RFC 2867 and 2868 make use of "tagged" attributes.  These RFCs
do *not* define sub-types because the attributes are designed to fit
within an existing data type - 4-octet Integer.

Having said that, new code typically *was* required to implement RFC 2867
and 2868, so as to allow the creation of UI to enable entering of Tunnel
attributes in an easy-to-use way.  However, existing products could have
been used without code changes, by manually entering appropriate
Integer values.


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