RIPE Network Coordination Centre
Some thoughts about a
Packet Duplication Metrics
Henk Uijterwaal
RIPE NCC
23 March 2016
http://www.ripe.net
RIPE Network Coordination Centre
Motivation
• Discussion in San Diego about the reporting draft:
- We looked at loss (RFC 2680)
- But we never looked at the opposite case, a packet
arriving twice
-
• Need a definition
- Reporting draft not a good place to define it
• Use existing definitions as much as possible
http://www.ripe.net
RIPE Network Coordination Centre
Type-P-One-Way-Packet-Duplication
• Parameters
- SRC, DST, T
- To: Time Out
• Metrics
- Positive integer number
- Undefined if packet is lost
• Definition
- Number of copies of packet received by DST in the
interval [T, T+To]
- Only uncorrupted packets, resends of corrupted packets
do not count
http://www.ripe.net
RIPE Network Coordination Centre
Type-P-One-way-packet-duplication-poisson-stream
• Stream of packets
- Src, dst, T, To
- Tf (End Time), Rate
• Similar to delay, loss and other metrics
• Metrics
- Series of numbers indicating number of packets received
http://www.ripe.net
RIPE Network Coordination Centre
Statistics
• Stream of packets
• Remove all undefined packets
- Independent from loss
• For the remaining packets: (#received/#sent) – 1
• Output: >0
- 0 if no duplication
- 1 if every packet arrives twice
- 2 if every packet arrives three times
http://www.ripe.net
RIPE Network Coordination Centre
To Do
• Put this in a draft
• Is this useful?
http://www.ripe.net