Re: Proposed Resolution to Issue 198: Attribute Concatenation/Splitting

["Alan DeKok" <aland@nitros9.org>]

  Nit:

> Where a
>       single filter rule exceeds 253 octets in length, the rule MUST be

  Since the Tag field takes one octet, the above text should be '252 octets'.

>       encoded across multiple NAS-Filter-Rule attributes, each with the
>       same Tag value; Tag values MUST be unique for each filter rule
>       present in a RADIUS packet with the exception of a Tag value of
>       '0' (0x30).  The value of '0' (0x30) in the Tag field indicates
>       that the attribute contains a filter rule that does not exceed 253

  Same here.  The NAS-Filter-Rule attribute can hold 253 octets, the
filter rule encapsulated in that attribute can be only 252 octets per
attribute.

  It may also be worth re-iterating the tag requirements from Section
3 of RFC 2882, "The byte value must be in the range 01-3F hex"

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