metasystema.org
UpdatedPROPOSED STANDARDIETF stream

RFC 5560: A One-Way Packet Duplication Metric

Still current, but amended. Parts of this document are changed or extended by RFC 6248. Read both.

In plain English — editorial summary, not part of the RFC

When a packet is sent from one host to the other, one normally expects that exactly one copy of the packet that was sent arrives at the destination. It is, however, possible that a packet is either lost or that multiple copies arrive. In earlier work, a metric for packet loss was defined. This metric quantifies the case where a packet that is sent does not arrive at its destination within a reasonable time. In this memo, a metric for another case is defined: a packet is sent, but multiple copies arrive. The document also discusses streams and methods to summarize the results of streams. [STANDARDS-TRACK]

Document record

Document ID
RFC5560
Published
May 2009
Authors
H. Uijterwaal
Status
PROPOSED STANDARD
Stream
IETF
Area
ops
Pages
14
Also known as
—
Updated by:
RFC 6248

Topics

Referenced by

One later RFC formally updates or obsoletes part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/5560-a-one-way-packet-duplication-metric