Overview of Pre-Congestion Notification Encoding
Metadata
- Publisher
- IETF
- Doc Type
- Informational
- Pages
- 20
- Abstract
- The objective of Pre-Congestion Notification (PCN) is to protect the quality of service (QoS) of inelastic flows within a Diffserv domain. On every link in the PCN-domain, the overall rate of PCN-traffic is metered, and PCN-packets are appropriately marked when certain configured rates are exceeded. Egress nodes provide decision points with information about the PCN-marks of PCN-packets that allows them to take decisions about whether to admit or block a new flow request, and to terminate some already admitted flows during serious \%pre-congestion. The PCN working group explored a number of approaches for encoding this pre-congestion information into the IP header. This document provides details of those approaches along with an explanation of the constraints that apply to any solution. This document is not an Internet Standards Track specification; it is published for informational purposes.
- Publication Date
- 2012-07-01
- Status Note
- Informational
- DOI
10.17487/RFC6627- Link
- https://doi.org/10.17487/RFC6627
- Author(s)
- Georgios KaragiannisKwok Ho ChanToby MoncasterMichael MenthPhilip EardleyBob Briscoe
Latest version of IETF RFC 6627
Document Versions — IETF RFC 6627
-
▶ IETF RFC 6627 (2012-07-01)THIS DOC [ACTIVE] [LATEST VERSION]
Normative Reference(s)
- IETF RFC 793 [Superseded*]
- IETF RFC 2474 [Active*]
- IETF RFC 3168 [Active*]
- IETF RFC 4774 [Active*]
Bibliographic Reference(s)
- Menth, M. and R. Geib, "Admission Control Using PCN- Marked Signaling", Work in Progress, February 2011. EXTERNAL
- Menth, M. and F. Lehrieder, "PCN-Based Measured Rate Termination", Computer Networks Journal, vol. 54, no. 3, Sept. 2010 EXTERNAL
- Menth, M., Babiarz, J., and P. Eardley, "Pre-Congestion Notification Using Packet-Specific Dual Marking", IEEE Proceedings of the International Workshop on the Network of the Future (Future-Net), Dresden/Germany, June 2009. EXTERNAL
- Menth, M., Babiarz, J., Moncaster, T., and B. Briscoe, "PCN Encoding for Packet-Specific Dual Marking (PSDM Encoding)", Work in Progress, March 2012. EXTERNAL
- Briscoe, B., Moncaster, T., and M. Menth, "A PCN Encoding Using 2 DSCPs to Provide 3 or More States", Work in Progress, March 2012. EXTERNAL
- Menth, M. and F. Lehrieder, "Performance of PCN-Based Admission Control under Challenging Conditions", IEEE/ACM Transactions on Networking, vol. 20, no. 2, April 2012. EXTERNAL
- IETF RFC 2205 [Active*]
- IETF RFC 2983 [Active*]
- IETF RFC 3260 [Active*]
- IETF RFC 3540 [Active*]
- IETF RFC 4301 [Active, Amended*]
- IETF RFC 5559 [Active*]
- IETF RFC 5670 [Active*]
- IETF RFC 5696 [Superseded*]
- IETF RFC 6040 [Active*]
- IETF RFC 6660 [Active*]
- IETF RFC 6661 [Active*]
- IETF RFC 6662 [Active*]
Source Data (JSON)
Full registry record with provenance metadata. Open directly: /api/doc/RFC6627.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 6627, Overview of Pre-Congestion Notification Encoding. Available at https://doi.org/10.17487/RFC6627
Snippet:
IETF RFC 6627, Overview of Pre-Congestion Notification Encoding. Available at https://doi.org/10.17487/RFC6627
HTML (ISO 690 compliant)
Preview:
IETF RFC 6627, Overview of Pre-Congestion Notification Encoding. Available at https://doi.org/10.17487/RFC6627
Snippet:
<span class="citation"><cite>IETF RFC 6627</cite>, Overview of Pre-Congestion Notification Encoding. Available at <a href="https://doi.org/10.17487/RFC6627" target="_blank" rel="noopener">https://doi.org/10.17487/RFC6627</a></span>
SMPTE's HTML Pub
Preview:
IETF RFC 6627, Overview of Pre-Congestion Notification Encoding
doi: 10.17487/RFC6627
url: https://doi.org/10.17487/RFC6627
doi: 10.17487/RFC6627
url: https://doi.org/10.17487/RFC6627
Snippet:
<li> <cite id="bib-rfc6627">IETF RFC 6627</cite>, Overview of Pre-Congestion Notification Encoding <span class="doi">10.17487/RFC6627</span> </li>
Referenced By
- IETF RFC 6660 [Active*]