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

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

David B. Nelson <mailto:// dnelson@elbrysnetworks.com> writes:

> Alan DeKok writes...
> 
> >   Inserting *other* attributes in between a fragemented attribute
> > is annoying and pointless.  It's better to forbid this, and to
> > declare that packets failing this test are malformed, and SHOULD
> > be silently discarded.
> 
> I think this would introduce a new, non-backwards-compatible
> requirement.
> Today, RADIUS requires that attributes of the same type not be re-
> ordered in
> the PDU, e.g. by proxies. There is no such requirement for attributes
> of
> differing types.

I believe that he meant that all fragments of a given attribute must be
contiguous in the original packet...

> 
> >   What does "Foo(0,4)" mean?
> 
> I suppose it means the TLV with Type Code 4, assigned within the IETF
> allocation, i.e. Attribute 26, Vendor-ID 0.

This would be a perfectly reasonable interpretation, but it actually means
"octets 0-4 of attribute Foo".

...



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