An EF DSCP for Capacity-Admitted Traffic
draft-baker-tsvwg-admitted-voice-dscp-01
| Document | Type |
Replaced Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Fred Baker | ||
| Last updated | 2006-12-15 (Latest revision 2006-10-06) | ||
| Replaced by | draft-ietf-tsvwg-admitted-realtime-dscp | ||
| 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-tsvwg-admitted-realtime-dscp | |
| 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
This document requests a DSCP from the IANA for a class of real-time traffic conforming to the Expedited Forwarding Per Hop Behavior and admitted using a CAC procedure involving authentication, authorization, and capacity admission, as compared to a class of real-time traffic conforming to the Expedited Forwarding Per Hop Behavior but not subject to capacity admission or subject to very coarse capacity admission. One of the reasons behind this is the need for classes of traffic that are handled under special policies, such as the non-preemptive Emergency Telecommunication Service, the US DoD's Assured Service (which is similar to MLPP), or e-911. These do not need separate DSCPs or separate PHBs that are separate from each other, but they need a traffic class from which they can deterministically obtain their service requirements from including SLA matters.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)