RFC 5670: Metering and Marking Behaviour of PCN-Nodes

The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain in a simple,…

Read RFC 5670 on the RFC Editor

Outgoing relationships (8 related RFCs)

Informative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Informative reference — RFC 3168: The Addition of Explicit Congestion Notification (ECN) to IP
Informative reference — RFC 2474: Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers
Informative reference — RFC 2475: An Architecture for Differentiated Services
Informative reference — RFC 5559: Pre-Congestion Notification (PCN) Architecture
Informative reference — RFC 5127: Aggregation of Diffserv Service Classes
Informative reference — RFC 4778: Operational Security Current Practices in Internet Service Provider Environments
Informative reference — RFC 5696: Baseline Encoding and Transport of Pre-Congestion Information

Incoming relationships (8 related RFCs)

Normatively referenced by — RFC 6660: Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)
Normatively referenced by — RFC 5696: Baseline Encoding and Transport of Pre-Congestion Information
Normatively referenced by — RFC 6661: Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Controlled Load (CL) Mode of Operation
Normatively referenced by — RFC 6662: Pre-Congestion Notification (PCN) Boundary-Node Behavior for the Single Marking (SM) Mode of Operation
Informatively referenced by — RFC 6040: Tunnelling of Explicit Congestion Notification
Informatively referenced by — RFC 7141: Byte and Packet Congestion Notification
Informatively referenced by — RFC 9330: Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
Informatively referenced by — RFC 6627: Overview of Pre-Congestion Notification Encoding