Encoding Three Pre-Congestion Notification States in the IP Header Using a Single Diffserv Codepoint
RFC 6660, “Encoding Three Pre-Congestion Notification States in the IP Header Using a Single Diffserv Codepoint”, is a Proposed Standard document published in July 2012 by B. Briscoe, T. Moncaster, M. Menth. It obsoletes RFC 5696. The canonical text is published by the RFC Editor.
Abstract
The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. The overall rate of PCN-traffic is metered on every link in the PCN- domain, and PCN-packets are appropriately marked when certain configured rates are exceeded. Egress nodes pass information about these PCN-marks to Decision Points that then decide whether to admit or block new flow requests or to terminate some already admitted flows during serious pre-congestion.
This document specifies how PCN-marks are to be encoded into the IP header by reusing the Explicit Congestion Notification (ECN) codepoints within a PCN-domain. The PCN wire protocol for non-IP protocol headers will need to be defined elsewhere. Nonetheless, this document clarifies the PCN encoding for MPLS in an informational appendix. The encoding for IP provides for up to three different PCN marking states using a single Diffserv codepoint (DSCP): not-marked (NM), threshold-marked (ThM), and excess-traffic-marked (ETM). Hence, it is called the 3-in-1 PCN encoding. This document obsoletes RFC 5696. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 6660 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 6659 Considerations for Deploying the Rapid Acquisition of Multicast RTP Sessions Method
- RFC 6661 Pre-Congestion Notification Boundary-Node Behavior for the Controlled Load Mode of Operation
- RFC 6658 Packet Pseudowire Encapsulation over an MPLS PSN
- RFC 6662 Pre-Congestion Notification Boundary-Node Behavior for the Single Marking Mode of Operation
- RFC 6657 Update to MIME regarding "charset" Parameter Handling in Textual Media Types
- RFC 6663 Requirements for Signaling of Pre-Congestion Information in a Diffserv Domain
- RFC 6656 Description of Cisco Systems' Subnet Allocation Option for DHCPv4
- RFC 6664 S/MIME Capabilities for Public Key Definitions