RFC 6627: Overview of Pre-Congestion Notification Encoding
In plain English — editorial summary, not part of the RFC
The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. On every link in the PCN-domain, the overall rate of PCN-traffic is metered, and PCN-packets are appropriately marked when certain configured rates are exceeded. Egress nodes provide decision points with information about the PCN-marks of PCN-packets that allows them to take decisions about whether to admit or block a new flow request, and to terminate some already admitted flows during serious \%pre-congestion. The PCN working group explored a number of approaches for encoding this pre-congestion information into the IP header. This document provides details of those approaches along with an explanation of the constraints that apply to any solution. This document is not an Internet Standards Track specification; it is published for informational purposes.
Document record
- Document ID
- RFC6627
- Published
- July 2012
- Authors
- G. Karagiannis; K. Chan; T. Moncaster; M. Menth; P. Eardley; B. Briscoe
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- tsv
- Pages
- 20
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6646DECoupled Application Data Enroute (DECADE) Problem StatementCurrent
July 2012
- RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current
July 2012
- RFC 6661Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of OperationCurrent
July 2012
- RFC 6662Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of OperationCurrent
July 2012
- RFC 6663Requirements for Signaling of Pre-Congestion Information in a Diffserv DomainCurrent
July 2012
- RFC 6584Simple Authentication Schemes for the Asynchronous Layered Coding (ALC) and NACK-Oriented Reliable Multicast (NORM) ProtocolsCurrent
April 2012
- RFC 6581Enhanced Remote Direct Memory Access (RDMA) Connection EstablishmentCurrent
April 2012
- RFC 6580IANA Registries for the Remote Direct Data Placement (RDDP) ProtocolsCurrent
April 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?