RFC 6662: Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
In plain English — editorial summary, not part of the RFC
Pre-Congestion Notification (PCN) is a means for protecting the quality of service for inelastic traffic admitted to a Diffserv domain. The overall PCN architecture is described in RFC 5559. This memo is one of a series describing possible boundary-node behaviors for a PCN-domain. The behavior described here is that for a form of measurement-based load control using two PCN marking states: not- marked and excess-traffic-marked. This behavior is known informally as the Single Marking (SM) PCN-boundary-node behavior. This document defines an Experimental Protocol for the Internet community.
Document record
- Document ID
- RFC6662
- Published
- July 2012
- Authors
- A. Charny; J. Zhang; G. Karagiannis; M. Menth; T. Taylor
- Status
- EXPERIMENTAL
- Stream
- IETF
- Area
- tsv
- Pages
- 31
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6661Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of OperationCurrent
July 2012
- RFC 6663Requirements for Signaling of Pre-Congestion Information in a Diffserv DomainCurrent
July 2012
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
- RFC 6681Raptor Forward Error Correction (FEC) Schemes for FECFRAMECurrent
August 2012
- RFC 6682RTP Payload Format for Raptor Forward Error Correction (FEC)Current
August 2012
- RFC 6683Guidelines for Implementing Digital Video Broadcasting - IPTV (DVB-IPTV) Application-Layer Hybrid Forward Error Correction (FEC) ProtectionCurrent
August 2012
- RFC 6695Methods to Convey Forward Error Correction (FEC) Framework Configuration InformationCurrent
August 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?