Baseline Encoding and Transport of Pre-Congestion Information
draft-moncaster-pcn-baseline-encoding-02
Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | T Moncaster , Bob Briscoe , Michael Menth | ||
Last updated | 2008-10-02 (Latest revision 2008-07-11) | ||
Replaced by | draft-ietf-pcn-baseline-encoding | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Replaced by draft-ietf-pcn-baseline-encoding | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
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) provides information to support admission control and flow termination in order to protect the Quality of Service of inelastic flows. It does this by marking packets when traffic load on a link is approaching or has exceeded a threshold below the physical link rate. This document specifies how such marks are to be encoded into the IP header. The baseline encoding described here provides for only two PCN encoding states. Other documents describe extended encoding schemes that allow for three encoding states. Status This memo is posted as an Internet-Draft with an intent to eventually progress to standards track.
Authors
T Moncaster
Bob Briscoe
Michael Menth
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)