RFC 7837: IPv6 Destination Option for Congestion Exposure (ConEx)

In plain English — editorial summary, not part of the RFC

Congestion Exposure (ConEx) is a mechanism by which senders inform the network about the congestion encountered by packets earlier in the same flow. This document specifies an IPv6 destination option that is capable of carrying ConEx markings in IPv6 datagrams.

Document record

Document ID

RFC7837

Published

May 2016

Authors

S. Krishnan; M. Kuehlewind; B. Briscoe; C. Ralli

Status

EXPERIMENTAL

Stream

IETF

Area

tsv

Pages

13

Also known as

—

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC7837

Topics

• Accountability
• Traffic Management
• Fairness
• Resource Sharing
• Congestion Control
• Quality of Service
• QoS
• Denial of Service

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 7141Byte and Packet Congestion NotificationCurrent

  February 2014

• RFC 7713Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and RequirementsCurrent

  December 2015

• RFC 6660Encoding Three Pre-Congestion Notification (PCN) States in the IP Header Using a Single Diffserv Codepoint (DSCP)Current

  July 2012

• RFC 5559Pre-Congestion Notification (PCN) ArchitectureCurrent

  June 2009

• RFC 9330Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: ArchitectureCurrent

  January 2023

• RFC 9331The Explicit Congestion Notification (ECN) Protocol for Low Latency, Low Loss, and Scalable Throughput (L4S)Current

  January 2023

• RFC 9332Dual-Queue Coupled Active Queue Management (AQM) for Low Latency, Low Loss, and Scalable Throughput (L4S)Current

  January 2023

• RFC 5696Baseline Encoding and Transport of Pre-Congestion InformationObsoleted

  November 2009

Also filed under

• EXPERIMENTAL
• 2016
• IETF stream
• tsv area