Therefore, my proposal is the following. L2 is unnecessary, so we drop it. The format is now: T L T2 data... We still have the problem of data length, though. We can solve this by saying "if T2 is zero, then the data for this extended type is concatenated to the data for the previous one". e.g. T L T2 data1... T L 0000 data2... The format of Extended-Type is now always 'T2 data...', which seems good to me. The length of T2 is derived from from the lengths of the encapsulating Extended-Type attribute. And the concatatenation can only occur if the first Extended-Type attribute has L=255, and even then, only if the next Extended-Type attribute exists, AND has T2 != 0000. I hope that's a little clearer.
Yes. So your proposal looks like this, no?
0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | Extended-Type |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Value...
+-+-+-+-+-+-+-+-+
Type
TBD (not 26)
Length
>= 4
Extended-Type
Two octets.
0: Concatenation
1-255: Reserved
255-65530: Allocated by IANA
65531-65535: Reserved
Value
0-251 octets (Length - 4).
Only a single RADIUS Extended-Type attribute may be included within
a RADIUS attribute of Type TBD. Where the value of the Extended-Type
field is zero (0), this indicates that the content of the value field
is to
be concatenated with the contents of the value field in the previous
attribute of Type TBD.
--
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/>