--- 1/draft-ietf-mpls-spl-terminology-01.txt 2020-05-06 00:13:05.381769276 -0700 +++ 2/draft-ietf-mpls-spl-terminology-02.txt 2020-05-06 00:13:05.393769435 -0700 @@ -1,21 +1,21 @@ 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 +Expires: November 6, 2020 A. Farrel Old Dog Consulting - November 21, 2019 + May 5, 2020 Special Purpose Label terminology - draft-ietf-mpls-spl-terminology-01 + draft-ietf-mpls-spl-terminology-02 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 @@ -25,25 +25,25 @@ 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. + This Internet-Draft will expire on November 6, 2020. Copyright Notice - Copyright (c) 2019 IETF Trust and the persons identified as the + 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 the Trust Legal Provisions and are provided without warranty as @@ -70,25 +70,25 @@ 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. + At the time of writing the first version of this document, 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].