RFC 6802: Ericsson Two-Way Active Measurement Protocol (TWAMP) Value-Added Octets
In plain English — editorial summary, not part of the RFC
This memo describes an extension to the Two-Way Active Measurement Protocol (TWAMP). Specifically, it extends the TWAMP-Test protocol, which identifies and manages packet trains, in order to measure capacity metrics like the available path capacity, tight section capacity, and UDP delivery rate in the forward and reverse path directions. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6802
- Published
- November 2012
- Authors
- S. Baillargeon; C. Flinta; A. Johnsson
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 15
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 5136Defining Network CapacityCurrent
February 2008
- RFC 7419Common Interval Support in Bidirectional Forwarding DetectionCurrent
December 2014
- RFC 7830The EDNS(0) Padding OptionCurrent
May 2016
- RFC 6808Test Plan and Results Supporting Advancement of RFC 2679 on the Standards TrackCurrent
December 2012
- RFC 6791Stateless Source Address Mapping for ICMPv6 PacketsCurrent
November 2012
- RFC 6815Applicability Statement for RFC 2544: Use on Production Networks Considered HarmfulCurrent
November 2012
- RFC 6820Address Resolution Problems in Large Data Center NetworksCurrent
January 2013
- RFC 6782Wireline Incremental IPv6Current
November 2012
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?