--- 1/draft-ietf-mpls-spl-terminology-00.txt 2019-11-21 19:13:13.185267428 -0800 +++ 2/draft-ietf-mpls-spl-terminology-01.txt 2019-11-21 19:13:13.197267739 -0800 @@ -1,103 +1,98 @@ MPLS Working Group L. Andersson Internet-Draft Bronze Dragon Consulting Updates: 3032, 7274 (if approved) K. Kompella Intended status: Informational Juniper Networks -Expires: January 8, 2020 A. Farrel +Expires: May 24, 2020 A. Farrel Old Dog Consulting - July 7, 2019 + November 21, 2019 Special Purpose Label terminology - draft-ietf-mpls-spl-terminology-00 + 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. - Note: The rest of the text in this section is not really part of the - abstract even though the text is placed here. It is working notes. - - Note: At least at the moment it is not the intention to take this - document to an RFC, but it might be polled to become a wg document to - see if the MPLS working group agree on the proposed terminology. - - Note: The changes we propose are minor, but we might have to progress - the document to RFC since there is a proposed change to the "Special- - Purpose Multiprotocol Label Switching (MPLS) Label Values" registry. + 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 January 8, 2020. + 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 the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 - 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 3 + 2. Background . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1. GMPLS Special Purpose Labels . . . . . . . . . . . . . . 3 3. Terminology and Abbreviations . . . . . . . . . . . . . . . . 3 - 4. Security Considerations . . . . . . . . . . . . . . . . . . . 5 + 4. Security Considerations . . . . . . . . . . . . . . . . . . . 4 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5 6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 5 7. References . . . . . . . . . . . . . . . . . . . . . . . . . 5 7.1. Normative References . . . . . . . . . . . . . . . . . . 5 - 7.2. Informative References . . . . . . . . . . . . . . . . . 6 + 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 is in the + 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 - [I-D.ietf-mpls-sfc]. This document discusses and recommends - terminology and abbreviations to be used when talking about and - documentating Special Purpose Labels. + [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]. * the values 0-15 has been reserved never to be allocated @@ -196,48 +191,48 @@ 6. Acknowledgements The authors of this document would like to thank Stewart Bryant for careful review and constructive suggestions. 7. References 7.1. Normative References [bSPL] "Special-Purpose MPLS Label Values", - . + . [eSPL] "Extended Special-Purpose MPLS Label Values", - . + . [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, . [RFC7274] Kompella, K., Andersson, L., and A. Farrel, "Allocating and Retiring Special-Purpose MPLS Labels", RFC 7274, DOI 10.17487/RFC7274, June 2014, . [SPL-NAME-SPACE] "Special-Purpose Multiprotocol Label Switching (MPLS) - Label Values", . + Label Values", . 7.2. Informative References - [I-D.ietf-mpls-sfc] - Farrel, A., Bryant, S., and J. Drake, "An MPLS-Based - Forwarding Plane for Service Function Chaining", draft- - ietf-mpls-sfc-07 (work in progress), March 2019. + [RFC8595] Farrel, A., Bryant, S., and J. Drake, "An MPLS-Based + Forwarding Plane for Service Function Chaining", RFC 8595, + DOI 10.17487/RFC8595, June 2019, + . Authors' Addresses Loa Andersson Bronze Dragon Consulting Email: loa@pi.nu Kireeti Kompella Juniper Networks