Baseline Encoding and Transport of Pre-Congestion Information
Metadata
- Publisher
- IETF
- Doc Type
- Standard
- Pages
- 15
- 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]
- Publication Date
- 2009-11-01
- Status Note
- Proposed Standard
- DOI
10.17487/RFC5696- Link
- https://doi.org/10.17487/RFC5696
- Author(s)
- T MoncasterBob BriscoeMichael Menth
- Keyword(s)
- Quality Of Service, QoS, DiffServ, Admission Control, Code Point, Protocol
Latest version of IETF RFC 5696
Document Versions — IETF RFC 5696
-
▶ IETF RFC 5696 (2009-11-01)THIS DOC [SUPERSEDED] [LATEST VERSION]
Superseded by:
- RFC6660 NOT IN REGISTRY
Normative Reference(s)
- IETF RFC 2119 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 4774 [Active*]
- IETF RFC 5670 [Active*]
Bibliographic Reference(s)
- Moncaster, T., Briscoe, B., and M. Menth, "A PCN encoding using 2 DSCPs to provide 3 or more states", Work in Progress, April 2009. EXTERNAL
- Briscoe, B., "Tunnelling of Explicit Congestion Notification", Work in Progress, July 2009. EXTERNAL
- IETF RFC 2474 [Active*]
- IETF RFC 2597 [Active*]
- IETF RFC 3246 [Active*]
- IETF RFC 3540 [Active*]
- IETF RFC 4301 [Active, Amended*]
- RFC4594 — SERV-CLASS EXTERNAL
- RFC5127 — RFC5127 EXTERNAL
- IETF RFC 5559 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC5696.json
Reference Tree
Explore all references and references to this document, as a navigable tree.
Open Reference TreeReference this Doc
Plain text (ISO 690 compliant)
Preview:
IETF RFC 5696, Baseline Encoding and Transport of Pre-Congestion Information. Available at https://doi.org/10.17487/RFC5696
Snippet:
IETF RFC 5696, Baseline Encoding and Transport of Pre-Congestion Information. Available at https://doi.org/10.17487/RFC5696
HTML (ISO 690 compliant)
Preview:
IETF RFC 5696, Baseline Encoding and Transport of Pre-Congestion Information. Available at https://doi.org/10.17487/RFC5696
Snippet:
<span class="citation"><cite>IETF RFC 5696</cite>, Baseline Encoding and Transport of Pre-Congestion Information. Available at <a href="https://doi.org/10.17487/RFC5696" target="_blank" rel="noopener">https://doi.org/10.17487/RFC5696</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 5696, Baseline Encoding and Transport of Pre-Congestion Information
doi: 10.17487/RFC5696
url: https://doi.org/10.17487/RFC5696
doi: 10.17487/RFC5696
url: https://doi.org/10.17487/RFC5696
Snippet:
<li> <cite id="bib-rfc5696">IETF RFC 5696</cite>, Baseline Encoding and Transport of Pre-Congestion Information <span class="doi">10.17487/RFC5696</span> </li>
Referenced By
- IETF RFC 5670 [Active*]
- IETF RFC 6040 [Active*]