Re: DISCUSS: draft-ietf-radext-fixes

[Barney Wolff <barney@databus.com>]

On Mon, Jul 02, 2007 at 03:10:30PM -0400, David B. Nelson wrote:
> Barney Wolff writes...
> 
> > At the risk of exposing my own lack of imagination, would someone
> > please explain how monotonically increasing ids would actually help
> > duplicate detection?  Specifically, just how does it avoid the cache?
> 
> I believe it means that the server only needs to remember the last value of
> Identifier seen in a successfully processed request, for each NAS IP/UDP
> scope.  Any lower value in a newly received request is a duplicate.  The
> server obviously needs to understand the wrap behavior at the 255 --> 0
> transition, of course.

But what if the request had been lost the first time sent?  Then the
request would be new to the server, despite being a retransmission from
the client.  And in any case, the server is supposed to respond to the
request, unless it is still working on the first instance.

In other words, I don't see how the server can avoid keeping a cache
of requests/responses, so I don't see what requiring monotonicity can gain.
What am I missing?

Regards,
Barney

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