A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic
RFC 5865
Document | Type | RFC - Proposed Standard (May 2010; Errata) | |
---|---|---|---|
Authors | James Polk , Fred Baker , Martin Dolly | ||
Last updated | 2015-10-14 | ||
Replaces | draft-baker-tsvwg-admitted-voice-dscp | ||
Stream | IETF | ||
Formats | plain text html pdf htmlized bibtex | ||
Reviews | |||
Stream | WG state | (None) | |
Document shepherd | No shepherd assigned | ||
IESG | IESG state | RFC 5865 (Proposed Standard) | |
Action Holders |
(None)
|
||
Consensus Boilerplate | Unknown | ||
Telechat date | |||
Responsible AD | Magnus Westerlund | ||
Send notices to | (None) |
Internet Engineering Task Force (IETF) F. Baker Request for Comments: 5865 J. Polk Updates: 4542, 4594 Cisco Systems Category: Standards Track M. Dolly ISSN: 2070-1721 AT&T Labs May 2010 A Differentiated Services Code Point (DSCP) for Capacity-Admitted Traffic Abstract This document requests one Differentiated Services Code Point (DSCP) from the Internet Assigned Numbers Authority (IANA) for a class of real-time traffic. This traffic class conforms to the Expedited Forwarding Per-Hop Behavior. This traffic is also admitted by the network using a Call Admission Control (CAC) procedure involving authentication, authorization, and capacity admission. This differs from a real-time traffic class that conforms to the Expedited Forwarding Per-Hop Behavior but is not subject to capacity admission or subject to very coarse capacity admission. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc5865. Baker, et al. Standards Track [Page 1] RFC 5865 DSCP for Capacity-Admitted Traffic May 2010 Copyright Notice Copyright (c) 2010 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1. Definitions . . . . . . . . . . . . . . . . . . . . . . . 4 1.2. Problem . . . . . . . . . . . . . . . . . . . . . . . . 6 2. Candidate Implementations of the Admitted Telephony Service Class . . . . . . . . . . . . . . . . . . . . . . . 7 2.1. Potential implementations of EF in this model . . . . . . 7 2.2. Capacity admission control . . . . . . . . . . . . . . . 9 2.3. Recommendations on implementation of an Admitted Telephony Service Class . . . . . . . . . . . . . . . . . 10 3. Summary: changes from RFC 4594 . . . . . . . . . . . . . . . 11 4. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 11 5. Security Considerations . . . . . . . . . . . . . . . . . . . 12 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 12 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 13 7.1. Normative References . . . . . . . . . . . . . . . . . . 13 7.2. Informative References . . . . . . . . . . . . . . . . . 13 Baker, et al. Standards Track [Page 2] RFC 5865 DSCP for Capacity-Admitted Traffic May 2010 1. Introduction This document requests one Differentiated Services Code Point (DSCP) from the Internet Assigned Numbers Authority (IANA) for a class of real-time traffic. This class conforms to the Expedited Forwarding (EF) [RFC3246] [RFC3247] Per-Hop Behavior. It is also admitted using a CAC procedure involving authentication, authorization, and capacityShow full document text