RFC 9017 on Special-Purpose Label Terminology
rfc-editor@rfc-editor.org Fri, 09 April 2021 22:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FC813A16D8; Fri, 9 Apr 2021 15:56:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id lURw9LvEaeCx; Fri, 9 Apr 2021 15:56:24 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7B4F83A1640; Fri, 9 Apr 2021 15:56:15 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 6F4D3F40790; Fri, 9 Apr 2021 15:56:05 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9017 on Special-Purpose Label Terminology
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20210409225605.6F4D3F40790@rfc-editor.org>
Date: Fri, 09 Apr 2021 15:56:05 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/w4xoCA4H3rIk1-Y2mP7ueShmTTw>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 09 Apr 2021 22:56:36 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9017
Title: Special-Purpose Label Terminology
Author: L. Andersson,
K. Kompella,
A. Farrel
Status: Standards Track
Stream: IETF
Date: April 2021
Mailbox: loa@pi.nu,
kireeti@juniper.net,
adrian@olddog.co.uk
Pages: 8
Updates: RFC 3032, RFC 7274
I-D Tag: draft-ietf-mpls-spl-terminology-06.txt
URL: https://www.rfc-editor.org/info/rfc9017
DOI: 10.17487/RFC9017
This document discusses and recommends terminology that may be used
when MPLS Special-Purpose Labels (SPLs) are specified and documented.
This document applies that terminology change to the relevant IANA
registry and also clarifies the use of the Entropy Label Indicator
(7) when immediately preceded by the Extension Label (15).
This document updates RFCs 3032 and 7274.
This document is a product of the Multiprotocol Label Switching Working Group of the IETF.
This is now a Proposed Standard.
STANDARDS TRACK: This document specifies an Internet Standards Track
protocol for the Internet community, and requests discussion and suggestions
for improvements. Please refer to the current edition of the Official
Internet Protocol Standards (https://www.rfc-editor.org/standards) for the
standardization state and status of this protocol. Distribution of this
memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC