RE: DISCUSS: draft-ietf-radext-fixes

["David B. Nelson" <dnelson@elbrysnetworks.com>]

Glen writes...

> Anyway, this could be easily accomplished w/o modifying legacy 
> clients or servers while nevertheless future-proofing the protocol...

How would a "modified" server decide if a newly received request message,
with a lower Identifier value than the most recently processed request, was
(a) a duplicate or (b) a different request, from a legacy client that
doesn't enforce monotonically increasing Identifier values?



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