RE: REMINDER: RADEXT WG Last call on "Extended RADIUS Attributes"

["Glen Zorn" <glenzorn@comcast.net>]

Alan DeKok <mailto://aland@deployingradius.com> writes:

> Glen Zorn wrote:
> > I believe that he meant that all fragments of a given attribute must
> be
> > contiguous in the original packet...
> 
>   RFC 3579, Section 3.1:
> 
>       If multiple
>       EAP-Message attributes are contained within an Access-Request or
>       Access-Challenge packet, they MUST be in order and they MUST be
>       consecutive attributes in the Access-Request or Access-Challenge
>       packet.
> 
>   Requiring this for Extended-Attribute is a good idea.

Alright, how about this?

   M (More)

      The More Flag is one (1) bit in length and MUST be present.  When
      a value to be transmitted exceeds 246 octets in length it is
      fragmented over two or more Extended Attributes.  If the More Flag
      is set (1), this indicates that the Value field of the Extended
      Attribute contains a fragment of a larger value, which is
      continued in the next Extended Attribute of the same Ext-Type.
      When the More Flag is clear (0), the final (or only) fragment of
      the value is contained in the Extended Attribute.  Any Extended 
	Attributes containing multiple fragments of the same value MUST be 
	in order and MUST be consecutive attributes in the packet.

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



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