Re: Fragmentation flag in extended attributed

[Alan DeKok <aland@nitros9.org>]

Glen Zorn wrote:
> It appears to me that this means that /all/ of the fragments are marked
> as such.  If so, suppose that 2 extended attributes of the same extended
> type are adjacent in a packet & both are fragmented.  How can you tell
> where the first ends & the second starts?  I can think of 2 easy ways to
> fix this: either specify that the flag is cleared in the attribute
> containing the first fragment or in the attribute containing the last
> fragment.  Note that the latter option basically turns the bit into a
> "more" flag, which has some precedent in IETF protocols ;-).  Any
> opinions/other suggestions?

  I think the last fragment should have the F bit clear.

  The document should also say that attributes with length less than 246
octets (for VSA content) MUST NOT have the F bit set.  Otherwise, the
fragments could all be 1 byte, giving a bad ratio of overhead to data.

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