Baseline Encoding and Transport of Pre-Congestion Information
RFC 5696, “Baseline Encoding and Transport of Pre-Congestion Information”, is a Proposed Standard document published in November 2009 by T. Moncaster, B. Briscoe, M. Menth. It has been obsoleted by RFC 6660 — refer to the newer document for the authoritative version. The canonical text is published by the RFC Editor.
Abstract
The objective of the Pre-Congestion Notification (PCN) architecture is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. It achieves this by marking packets belonging to PCN-flows when the rate of traffic exceeds certain configured thresholds on links in the domain. These marks can then be evaluated to determine how close the domain is to being congested. This document specifies how such marks are encoded into the IP header by redefining the Explicit Congestion Notification (ECN) codepoints within such domains. The baseline encoding described here provides only two PCN encoding states: Not-marked and PCN-marked. Future extensions to this encoding may be needed in order to provide more than one level of marking severity. [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 5696 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5695 MPLS Forwarding Benchmarking Methodology for IP Flows
- RFC 5697 Other Certificates Extension
- RFC 5694 Peer-to-Peer Architecture: Definition, Taxonomies, Examples, and Applicability
- RFC 5698 Data Structure for the Security Suitability of Cryptographic Algorithms
- RFC 5693 Application-Layer Traffic Optimization Problem Statement
- RFC 5692 Transmission of IP over Ethernet over IEEE 802.16 Networks
- RFC 5691 RTP Payload Format for Elementary Streams with MPEG Surround Multi- Channel Audio
- RFC 5701 IPv6 Address Specific BGP Extended Community Attribute