RE: Issue: Zero Tag field in Filter-Rule attribute

["Nelson, David" <dnelson@enterasys.com>]

Bernard Aboba writes...
> With the change, it might look like this:
> 
> The Tag field is one octet, and MUST always be present. It is used to
> identify the filter rule that is represented. Where a single
> filter rule exceeds 253 octets in length, the rule MUST be encoded
> across multiple NAS-Filter-Rule attributes, each with the same
> non-zero Tag value; non-zero Tag values MUST be unique for each
> filter rule present in a RADIUS packet. The value of '0' (0x30) in
> the Tag field indicates that the attribute contains a filter rule
> that does not exceed 253 octets in length; as a result attributes
> with a Tag value of 0x30 MUST NOT be concatenated, and one or more
> Filter-Rule attributes with a tag value of 0x31 may be included
> in a single RADIUS packet, each describing a single filter rule.

Looks good to me, with the change to consistent use of 0x30, noted by
Jouni.


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