On Oct 6, 2009, at 5:14 PM, Wojciech Dec (wdec) wrote:
That same RFC 2865, in section 5, states:
string 1-253 octets containing binary data (values 0 through
255 decimal, inclusive). Strings of length zero (0)
MUST NOT be sent; omit the entire attribute instead.
With that, Ipv6 Prefix, Route options, Auth-IPv6-Prefix-User-ID, etc
would be pretty much covered by using the string term.
With all due respect, the String data type is just a string of undistinguished octets. While you may conceptually overlay it with a structure, i.e define sub-fields, that action creates a new data type. In other words, the String type is just a string. You may lament the fact that RADIUS, as defined in RFCs up through 2865, has no method to formally define structured data, but the fact is that it has none.
-- 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/>