Special Purpose Label terminology
draft-ietf-mpls-spl-terminology-01

Document Type Active Internet-Draft (mpls WG)
Last updated 2019-11-21
Replaces draft-andersson-mpls-spl-terminology
Stream IETF
Intended RFC status (None)
Formats plain text pdf htmlized bibtex
Stream WG state WG Document
Document shepherd Nicolai Leymann
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to Nicolai Leymann <n.leymann@telekom.de>
MPLS Working Group                                          L. Andersson
Internet-Draft                                  Bronze Dragon Consulting
Updates: 3032, 7274 (if approved)                            K. Kompella
Intended status: Informational                          Juniper Networks
Expires: May 24, 2020                                          A. Farrel
                                                      Old Dog Consulting
                                                       November 21, 2019

                   Special Purpose Label terminology
                   draft-ietf-mpls-spl-terminology-01

Abstract

   This document discusses and recommends a terminology that may be used
   when MPLS Special Purpose Labels (SPL) are specified and documented.

   This document updates RFC 7274 and RFC 3032.

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 https://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 May 24, 2020.

Copyright Notice

   Copyright (c) 2019 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
   (https://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

Andersson, et al.         Expires May 24, 2020                  [Page 1]
Internet-Draft               SPL Terminology               November 2019

   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Background  . . . . . . . . . . . . . . . . . . . . . . . . .   2
     2.1.  GMPLS Special Purpose Labels  . . . . . . . . . . . . . .   3
   3.  Terminology and Abbreviations . . . . . . . . . . . . . . . .   3
   4.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   5
   6.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   5
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   5
     7.1.  Normative References  . . . . . . . . . . . . . . . . . .   5
     7.2.  Informative References  . . . . . . . . . . . . . . . . .   5
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   6

1.  Introduction

   RFC 7274 [RFC7274] made some changes to the terminology used for MPLS
   Special Purpose Labels, but did not define consistent terminology.

   One thing that RFC 7274 did was to deprecate use use of the term
   "reserved labels" when describing a range of labels allocated from a
   registry maintained by IANA.  The term "Reserved" in such a registry
   means "set aside, not to be used", but that range of labels was
   available for allocation according to the policies set out in the
   registry.  The name "Special Purpose Labels" was introduced in RFC
   7274 in place of the previous term, and the abbreviation SPL was
   recommended.

   At the time of posting this Internet-Draft, the IETF was in the
   process of allocating the very first SPLs from the Extended SPL range
   [RFC8595].  This document discusses and recommends terminology and
   abbreviations to be used when talking about and documenting Special
   Purpose Labels.

   This document updates RFC 3032 [RFC3032] and RFC 7274 [RFC7274] and
   RFC 3032 [RFC3032] in that it changes the terminology for both Base
   SPLs and Extended SPLs.

2.  Background

   Two sets of SPLs are defined for use in MPLS:

      The range of SPLs 0-15 is specified in RFC 3032 [RFC3032].

      The range of SPLs 0-1048575 is specified in RFC 7274 [RFC7274].

Andersson, et al.         Expires May 24, 2020                  [Page 2]
Internet-Draft               SPL Terminology               November 2019

      *  the values 0-15 has been reserved never to be allocated

      *  the values 15-239 are available for allocation

      *  the values 240-255 are for experimental use

      *  the values 256-1048575 are currently not available for
         allocation, and a standard tracks RFC will be needed to make
Show full document text