Resolution to Issue 198: Another attempt

["Bernard Aboba" <bernard_aboba@hotmail.com>]

So as to lessen restrictions on the number of potential rules, here is 
another attempt at text relating to the Tag field.  Is this better?

"  Tag

     The Tag field is used to identify the filter rule that is
     represented; the length of the Tag field is one octet and it MUST
     always be present.

     Where a single filter rule is less than or equal to 252 octets in
     length, it MUST be encoded with a Tag field value of zero (0) and
     MUST NOT be split between multiple NAS-Filter-Rule attributes.  On
     receipt, attributes with a Tag field value of zero (0) MUST NOT be
     concatenated to form a single filter rule.

     Where a single filter rule exceeds 252 octets in length, the rule
     MUST be encoded across multiple NAS-Filter-Rule attributes, each
     with the same Tag value which MUST be in the range 0x01 - 0x3F.
     NAS-Filter-Rule attributes comprising a single filter rule MUST be 
sent
     consecutively, without intervening attributes with another Tag
     field value.  The Tag field value of 0xFF is reserved and 
NAS-Filter-Rule
     attributes containing this Tag field value should be ignored upon 
receipt.

     Adjacent filter rules exceeding 252 octets in length MUST be
     encoded with different non-zero Tag field values; however, the Tag
     field value used for a given filter rule need not be unique within
     the entire RADIUS packet.



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