|
RADEXT WG last call has concluded on draft-ietf-radext-extended-attributes-00.txt. Two comments were received: http://ops.ietf.org/lists/radiusext/2008/msg00095.html http://ops.ietf.org/lists/radiusext/2008/msg00096.html This leaves three open issues on the document (225, 250 and 251): http://www.drizzle.com/~aboba/RADEXT/ A new version of the document has been posted to the archive: http://www.ietf.org/internet-drafts/draft-ietf-radext-extended-attributes-01.txt The major difference between version -00 and -01 appears to be a change to the TLV format: In -00, Section 4 stated: " TLVs are encoded as follows: o The first octet is the Ext-Type field o The second octet is the Ext-Length field, representing of the entire TLV, including the length of the Ext-Type field (1 octet), the length of the Ext-Length field itself (1 octet) and the length of the Value field (1 or more octets)" -01 Section 4 now states: " TLVs are encoded as follows: o The first bit is the Standard or 'S' flag. The Standard flag is set (1) if the TLV is a standard RADIUS attribute (as defined in RFC 2865, for example), otherwise it is clear (0). o The next 2 octets are the Ext-Type field o The next octet is the Ext-Length field, representing of the entire TLV, including the length of the Ext-Type field (2 octets), the length of the Ext-Length field itself (1 octet) and the length of the Value field (1 or more octets) o The Value field consists of one or more octets comprising the actual data." Since previous discussion of these changes on the RADEXT WG mailing list was inconclusive (see http://ops.ietf.org/lists/radiusext/2008/msg00000.html) the Chairs would like to determine whether RADEXT WG consensus exists for the changes or not. We are requesting RADEXT WG participants to review the -01 Extended Attributes draft and to post a note the RADEXT WG mailing list indicating their support (or opposition) to the changes. Specifically: a. Do you support increasing the size of the Extended-Type field to two octets, from one octet? b. Do you support use of the RADIUS Extended Type VSAs to encode standard RADIUS attributes? The Consensus call will last until March 29, 2008. |