Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 7713

Congestion Exposure (ConEx) Concepts, Abstract Mechanism, and Requirements,December 2015

File formats:
icon for text fileicon for PDFicon for HTML
Status:
INFORMATIONAL
Authors:
M. Mathis
B. Briscoe
Stream:
IETF
Source:
conex (tsv)

Cite this RFC:TXT  | XML  |  BibTeX

DOI:  https://doi.org/10.17487/RFC7713

Discuss this RFC: Send questions or comments to the mailing listconex@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 7713


Abstract

This document describes an abstract mechanism by which senders informthe network about the congestion recently encountered by packets inthe same flow. Today, network elements at any layer may signalcongestion to the receiver by dropping packets or by ExplicitCongestion Notification (ECN) markings, and the receiver passes thisinformation back to the sender in transport-layer feedback. Themechanism described here enables the sender to also relay thiscongestion information back into the network in-band at the IP layer,such that the total amount of congestion from all elements on thepath is revealed to all IP elements along the path, where it could,for example, be used to provide input to traffic management. Thismechanism is called Congestion Exposure, or ConEx. The companiondocument, "Congestion Exposure (ConEx) Concepts and Use Cases"(RFC 6789), provides the entry point to the set of ConEx documentation.


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp