Pre-Congestion Notification marking
draft-briscoe-tsvwg-cl-phb-03
| Document | Type | Expired Internet-Draft (individual in tsv area) | |
|---|---|---|---|
| Author | Bob Briscoe | ||
| Last updated | 2015-10-14 (Latest revision 2006-10-22) | ||
| Stream | Internet Engineering Task Force (IETF) | ||
| Formats |
Expired & archived
|
||
| Stream | WG state | (None) | |
| Document shepherd | (None) | ||
| IESG | IESG state | Expired (IESG: Dead) | |
| Consensus boilerplate | Unknown | ||
| Telechat date | (None) | ||
| Responsible AD | Lars Eggert | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Pre-Congestion Notification (PCN) builds on the concepts of RFC 3168, "The addition of Explicit Congestion Notification to IP". However, Pre-Congestion Notification aims at providing notification before any congestion actually occurs. Pre-Congestion Notification is applied to real-time flows (such as voice, video and multimedia streaming) in DiffServ networks. As described in [CL-DEPLOY], it enables "pre" congestion control through two procedures, flow admission control and flow pre-emption. The draft proposes algorithms that determine when a PCN-enabled router writes Admission Marking and Pre-emption Marking in a packet header, depending on the traffic level. The draft also proposes how to encode these markings. We present simulation results with PCN working in an edge-to-edge scenario using the marking algorithms described. Other marking algorithms will be investigated in the future.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)