RFC 8889: Multipoint Alternate-Marking Method for Passive and Hybrid Performance Monitoring
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9342.
Current version: RFC 9342 — Clustered Alternate-Marking Method
In plain English — editorial summary, not part of the RFC
The Alternate-Marking method, as presented in RFC 8321, can only be applied to point-to-point flows, because it assumes that all the packets of the flow measured on one node are measured again by a single second node. This document generalizes and expands this methodology to measure any kind of unicast flow whose packets can follow several different paths in the network -- in wider terms, a multipoint-to-multipoint network. For this reason, the technique here described is called "Multipoint Alternate Marking".
Document record
- Document ID
- RFC8889
- Published
- August 2020
- Authors
- G. Fioccola; M. Cociglio; A. Sapio; R. Sisto
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- ops
- Pages
- 23
- Also known as
- —
- Obsoleted by:
- RFC 9342
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.
- RFC 8886Secure Device InstallCurrent
September 2020
- RFC 8893Resource Public Key Infrastructure (RPKI) Origin Validation for BGP ExportCurrent
September 2020
- RFC 8895Application-Layer Traffic Optimization (ALTO) Incremental Updates Using Server-Sent Events (SSE)Current
November 2020
- RFC 8896Application-Layer Traffic Optimization (ALTO) Cost CalendarCurrent
November 2020
- RFC 8897Requirements for Resource Public Key Infrastructure (RPKI) Relying PartiesCurrent
September 2020
- RFC 8901Multi-Signer DNSSEC ModelsCurrent
September 2020
- RFC 8906A Common Operational Problem in DNS Servers: Failure to CommunicateCurrent
September 2020
- RFC 8907The Terminal Access Controller Access-Control System Plus (TACACS+) ProtocolUpdated
September 2020
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?