Pre-Congestion Notification Using Single Marking for Admission and Termination
draft-charny-pcn-single-marking-03

Document Type Expired Internet-Draft (individual in tsv area)
Last updated 2015-10-14 (latest revision 2007-11-18)
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state Expired (IESG: Dead)
Consensus Boilerplate Unknown
Telechat date
Responsible AD Lars Eggert
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-charny-pcn-single-marking-03.txt

Abstract

Pre-Congestion Notification described in [I-D.eardley-pcn-architecture] and earlier in [I-D.briscoe-tsvwg-cl-architecture] approach proposes the use of an Admission Control mechanism to limit the amount of real-time PCN traffic to a configured level during the normal operating conditions, and the use of a Flow Termination mechanism to tear-down some of the flows to bring the PCN traffic level down to a desirable amount during unexpected events such as network failures, with the goal of maintaining the QoS assurances to the remaining flows. In [I-D.eardley-pcn-architecture], Admission and Flow Termination use two different markings and two different metering mechanisms in the internal nodes of the PCN region. This draft proposes a mechanism using a single marking and metering for both Admission and Flow Termination, and presents an analysis of the tradeoffs. A side- effect of this proposal is that a different marking and metering Admission mechanism than that proposed in [I-D.eardley-pcn-architecture] may be also feasible, and may result in a number of benefits. In addition, this draft proposes a migration path for incremental deployment of this approach as an intermediate step to the dual-marking approach.

Authors

Anna Charny (acharny@cisco.com)
Xinyang Zhang (joyzhang@cisco.com)
Fran├žois Le Faucheur (flefauch@cisco.com)
Vassilis Liatsos (vliatsos@cisco.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)