RE: Issue: Attribute concatenation/splitting

[Rajith R <rajithr@huawei.com>]

See comments inline

****************************************************************************
This e-mail and attachments contain confidential information from HUAWEI,
which is intended only for the person or entity whose address is listed
above. Any use of the information contained herein in any way (including,
but not limited to, total or partial disclosure, reproduction, or
dissemination) by persons other than the intended recipient's) is
prohibited. If you receive this e-mail in error, please notify the sender by
phone or email immediately and delete it!
>-----Original Message-----
>From: aland@nitros9.org [mailto:aland@nitros9.org]
>Sent: Tuesday, July 04, 2006 10:30 PM
>To: Pasi.Eronen@nokia.com
>Cc: rajithr@huawei.com; radiusext@ops.ietf.org
>Subject: Re: Issue: Attribute concatenation/splitting
>
>Pasi.Eronen@nokia.com wrote:
>> Yes, this would work as well: an attribute length 255 would mean that
>> the data item continues to the next attribute;
>
>  If the next attribute exists.
>
>> attribute length less than 255 would indicate the final piece of
>> this data item.
>
>  Or, if there is no next attribute.
>
>> The only catch might be that RFC 2865 prohibits string/text attributes
>> with length 2 (=string length 0).
>
>  Attributes of length 2 are unnecessary if the above conditions are met.

In a RADIUS packet, there are 2 successive NAS-Filter-Rule attributes of
length 255 & 50 respectively. How do you determine they are 2 separate
attributes or a single attribute split?

Rajith

>
>  Alan DeKok.


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