MPLS IANA Registries Structure
draft-andersson-mpls-iana-registries-structure-00

Document Type Active Internet-Draft (individual)
Author Loa Andersson 
Last updated 2020-11-02
Stream (None)
Intended RFC status (None)
Formats plain text pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
MPLS Working Group                                          L. Andersson
Internet-Draft                                  Bronze Dragon Consulting
Intended status: Standards Track                        November 2, 2020
Expires: May 6, 2021

                     MPLS IANA Registries Structure
           draft-andersson-mpls-iana-registries-structure-00

Abstract

   The structure of the MPLS IANA registries is not entirely intuitive.
   This document proposes a clarification.  The intention is to make a
   structure that is implicit in the MPLS IANA registries clearly
   visible.

   This document does not change any RFC, nor are the content of any
   registry touched.

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 6, 2021.

Copyright Notice

   Copyright (c) 2020 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                  Expires May 6, 2021                  [Page 1]
Internet-Draft            MPLS IANA registries             November 2020

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

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
     1.1.  Requirement Language  . . . . . . . . . . . . . . . . . .   2
     1.2.  Terminology Used in this Document . . . . . . . . . . . .   2
   2.  MPLS IANA Registry Structure  . . . . . . . . . . . . . . . .   3
     2.1.  Lack of Structure . . . . . . . . . . . . . . . . . . . .   3
     2.2.  Implicit Structure  . . . . . . . . . . . . . . . . . . .   4
     2.3.  Structure made Explicit . . . . . . . . . . . . . . . . .   5
   3.  Multiprotocol Label Switching Architecture (MPLS) . . . . . .   5
   4.  Comments on Section 3 . . . . . . . . . . . . . . . . . . . .   7
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   8
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   8
   7.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   8
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   9
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   9
     8.2.  Informative References  . . . . . . . . . . . . . . . . .  10
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .  10

1.  Introduction

   This document describes a re-organization of the IANA web pages that
   hold the MPLS IANA registries [MPLS-code-points].  The intent is to
   make the structure of the MPLS IANA registries clearer, and
   registries and code points easier to find.

1.1.  Requirement Language

   The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
   "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
   "OPTIONAL" in this document are to be interpreted as described in BCP
   14 [RFC2119] [RFC8174] when, and only when, they appear in all
   capitals, as shown here.

1.2.  Terminology Used in this Document

   This document uses some terms that relates to IANA registries in this
   way:

      Top Level Registry
      E.g. the entry to the MPLS IANA registries [MPLS-code-points] as
      captured on the main IANA web page [IANA-prot-reg].
      Note: It might be that we want to call the IANA Protocol Registry
      "Top Level", in which case we call this level "First Level
      Registry".

Andersson                  Expires May 6, 2021                  [Page 2]
Internet-Draft            MPLS IANA registries             November 2020

      IANA Name Space,
      a name space is an optional grouping immediately below top level
      registry.  An example could be "Multiprotocol Label Switching
      (MPLS) Label Switched Paths (LSPs) Ping Parameters"
      [IANA-LSP-PING].  A name space is most often a container for
      registries that hold code points that share some affinity.

      IANA Registry,
Show full document text