RE: Issue: Attribute concatenation/splitting

[<Pasi.Eronen@nokia.com>]

rajithr@huawei.com wrote:
> 
> IMHO, split/concatenate logic for multiple, potentially long data
> items of the same type should be attribute type insensitive. One
> such option could be split at 253th byte boundary of the payload and
> add them successively to the RADIUS message. If the last (split)
> RADIUS attribute also happens to be of attribute length = 255, add a
> delimiter attribute (of the same type) with attribute length as 2.

Yes, this would work as well: an attribute length 255 would mean that
the data item continues to the next attribute; attribute length less
than 255 would indicate the final piece of this data item.

The only catch might be that RFC 2865 prohibits string/text attributes
with length 2 (=string length 0). But on the other hand, at least 
draft-aboba-radext-fixes talks about User-Name attributes with string 
length 0, so perhaps this could be used anyway...?

Best regards,
Pasi

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