Re: [ippm] Next version of the duplicate draft

Hi,

> so this says that the source and destination IP address need to be the 
> same for packet to be duplicates, but it's still vague about which 
> fields in the next header ("transport" header, usually) need to be 
> identical. I'm not convinced that this text will lead to implementations 
> that will come up with the same measurement results for the same packet 
> sequence. Can we be more precise?

I think it does as long as you don't look at any other fields than source,
destination and information.

Each packet has source, destination, a bunch of other headers and finally
the information that it carries.  On the receiving side, one records the
packets and for each arriving packet, one checks if one has arrived before
with the same source, destination and information (within  the time-out
interval).  If so, it is a duplicate.  If not, it isn't.

The real question, I think, is whether there can be cases where the source
intentionally sends multiple packets with the same src, dst and information
(but something different in the other headers).

Henk

-- 
------------------------------------------------------------------------------
Henk Uijterwaal                           Email: henk.uijterwaal(at)ripe.net
RIPE Network Coordination Centre          http://www.amsterdamned.org/~henk
P.O.Box 10096          Singel 258         Phone: +31.20.5354414
1001 EB Amsterdam      1016 AB Amsterdam  Fax: +31.20.5354445
The Netherlands        The Netherlands    Mobile: +31.6.55861746
------------------------------------------------------------------------------

Is one of the choices leaving the office open?
                                       Alan Greenspan on the next elections
_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm