RFC 8321: 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 9341.
Current version: RFC 9341 — Alternate-Marking Method
In plain English — editorial summary, not part of the RFC
This document describes a method to perform packet loss, delay, and jitter measurements on live traffic. This method is based on an Alternate-Marking (coloring) technique. A report is provided in order to explain an example and show the method applicability. This technology can be applied in various situations, as detailed in this document, and could be considered Passive or Hybrid depending on the application.
Document record
- Document ID
- RFC8321
- Published
- January 2018
- Authors
- G. Fioccola; A. Capello; M. Cociglio; L. Castaldelli; M. Chen; L. Zheng; G. Mirsky; T. Mizrahi
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- ops
- Pages
- 33
- Also known as
- —
- Obsoleted by:
- RFC 9341
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 8326Graceful BGP Session ShutdownCurrent
March 2018
- RFC 8327Mitigating the Negative Impact of Maintenance through BGP Session CullingCurrent
March 2018
- RFC 8313Use of Multicast across Inter-domain Peering PointsCurrent
January 2018
- RFC 8309Service Models ExplainedCurrent
January 2018
- RFC 8334Launch Phase Mapping for the Extensible Provisioning Protocol (EPP)Current
March 2018
- RFC 8305Happy Eyeballs Version 2: Better Connectivity Using ConcurrencyCurrent
December 2017
- RFC 8337Model-Based Metrics for Bulk Transport CapacityCurrent
March 2018
- RFC 8340YANG Tree DiagramsUpdated
March 2018
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?