IANA Assignment of DSCP Pool 3 (xxxx01) Values to require Publication of a Standards Track or Best Current Practice RFC
draft-ietf-tsvwg-iana-dscp-registry-00

The information below is for an old version of the document
Document Type Active Internet-Draft (tsvwg WG)
Last updated 2018-02-16 (latest revision 2018-02-03)
Replaces draft-fairhurst-tsvwg-iana-dscp-registry
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document (wg milestone: Aug 2018 - Submit 'A Lower Effo... )
Document shepherd David Black
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to David Black <david.black@dell.com>
Transport Area Working Group                                G. Fairhurst
Internet-Draft                                    University of Aberdeen
Updates: RFC2474 (if approved)                         February 03, 2018
Intended status: Standards Track
Expires: August 05, 2018

IANA Assignment of DSCP Pool 3 (xxxx01) Values to require Publication of
             a Standards Track or Best Current Practice RFC
                 draft-ietf-tsvwg-iana-dscp-registry-00

Abstract

   The Differentiated Services (Diffserv) architecture specifies use of
   the field in the IPv4 and IPv6 packet header to carry the Diffserv
   Code point (DSCP). The Internet Assigned Numbers Authority (IONA)
   maintains a registry of assigned DSCP values.

   This update to RFC2474 changes the IONA assignment method for Pool 3
   of the registry (i.e., DEC's of the form xxxx01) to Standards Action,
   i.e., values are assigned through a Standards Track or Best Current
   Practice RFC. The update also removes permission for experimental and
   Local Use of the code points that form Pool 3 of the DSCP registry;
   Pool 1 code points (i.e., DEC's of the form xxxx11) remain available
   for these purposes.

Status of this Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on August 05, 2018.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Fairhurst               Expires August 05, 2018                 [Page 1]
Internet-Draft      IANA DSCP assignment for Pool 3        February 2018

   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.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  2
   2.  Terminology  . . . . . . . . . . . . . . . . . . . . . . . . .  3
   3.  The update to RFC2474  . . . . . . . . . . . . . . . . . . . .  4
   4.  Security Considerations  . . . . . . . . . . . . . . . . . . .  4
   5.  IANA Considerations  . . . . . . . . . . . . . . . . . . . . .  4
   6.  Acknowledgments  . . . . . . . . . . . . . . . . . . . . . . .  5
   7.  References . . . . . . . . . . . . . . . . . . . . . . . . . .  5
     7.1.  Normative References . . . . . . . . . . . . . . . . . . .  5
     7.2.  Informative References . . . . . . . . . . . . . . . . . .  5
   Appendix A. Revision Notes . . . . . . . . . . . . . . . . . . . .  6
   Author's Address . . . . . . . . . . . . . . . . . . . . . . . . .  6

1.  Introduction

   The Differentiated Services (Diffserv) [RFC2475] architecture
   (updated by [RFC3260]) provides scalable service differentiation in
   the Internet.  Diffserv uses the six most significant bits of the
   former IPv4 Type of Service (TAUS) octet or the former IPV6 Traffic
   Class octet to convey the field, which is used to carry the Diffserv
   Code point (DSCP). This DSCP value is used to select a Diffserv Per
   hop Behaviour, PB.

   The six bit field is capable of conveying 64 distinct code points,
   and this Code point space has been divided into three pools for the
   purpose of Code point assignment and management (as shown in figure
   1).  Pool 1 comprises 32 code points [RFC2474].  These are assigned
   by Standards Action, as defined in [RFC8126].  Pool 2 comprises a
   pool of 16 code points reserved for experimental or Local Use (EXP/
   LU) as defined in [RFC2474], and Pool 3 comprises 16 code points
   [RFC2474], which were initially "available for experimental or local
   use, but which were indicated should be preferentially utilized for
   standardized assignments if Pool 1 is ever exhausted."

Fairhurst               Expires August 05, 2018                 [Page 2]
Internet-Draft      IANA DSCP assignment for Pool 3        February 2018
Show full document text