RE: Extending RADIUS Attribute Space

["Nelson, David" <dnelson@enterasys.com>]

Avi Lior writes...

> If we want to interoperate with Diameter for example, how would we
address
> the fact that the length of a diameter attribute is 3 octets?
> 
> Is this enough of a justification to allow RADIUS Extended attributes
to
> be longer than 1 octet in length?

Well, I don't know.  I think it once again depends on the actual
attributes and applications under consideration.  If RADIUS has a
well-defined mechanism for achieving application-level fragmentation and
re-assembly of "oversize" attributes, why isn't it sufficient for a
RADIUS-Diameter gateway function to utilize that fragmentation and
re-assembly when translating between RADIUS and Diameter?  Making the
translation simple and straightforward is important, but I think that
requirement can be met with fragmentation and re-assembly.  Execution
efficiency is another matter, of course...

-- Dave




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