RFC 5696: Baseline Encoding and Transport of Pre-Congestion Information

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…

Read RFC 5696 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 4774: Specifying Alternate Semantics for the Explicit Congestion Notification (ECN) Field
Normative reference — RFC 5670: Metering and Marking Behaviour of PCN-Nodes
Informative reference — RFC 4301: Security Architecture for the Internet Protocol
Informative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informative reference — RFC 3246: An Expedited Forwarding PHB (Per-Hop Behavior)
Informative reference — RFC 2597: Assured Forwarding PHB Group
Informative reference — RFC 4594: Configuration Guidelines for DiffServ Service Classes
Informative reference — RFC 3540: Robust Explicit Congestion Notification (ECN) Signaling with Nonces
Informative reference — RFC 5559: Pre-Congestion Notification (PCN) Architecture
Informative reference — RFC 5127: Aggregation of Diffserv Service Classes

Incoming relationships (4 related RFCs)

Obsoleted by, Informatively referenced by — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Informatively referenced by — RFC 6040: Tunnelling of Explicit Congestion Notification
Informatively referenced by — RFC 5670: Metering and Marking Behaviour of PCN-Nodes
Informatively referenced by — RFC 6627: Overview of Pre-Congestion Notification Encoding