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

[Alan DeKok <aland@deployingradius.com>]

Stefan Winter wrote:
> One might also do any other split of the data, like if there is a 300
> byte data to be transmitted, 150 in the first fragment, 150 in the second.
> There also is no clarification whether fragmenting should only occur
> when it is needed. Without requiring this, a compliant implementation
> could as well split the 5-byte data "Hello" into five fragments. I
> suggest to add a bit of wording to strongly discourage that.

  I would say:

  The More Flag MUST NOT be set if the Length is less than 255.

> - is it worth mentioning that this encoding is not the only one
> possible, since the order of the struct members doesn't need to be
> preserved during marshalling?

  Yes.  Attributes don't have order in RADIUS.

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