RFC 7537 on IANA Registries for LSP Ping Code Points
rfc-editor@rfc-editor.org Mon, 11 May 2015 22:19 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 (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4DD9F1A90BA; Mon, 11 May 2015 15:19:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.912
X-Spam-Level:
X-Spam-Status: No, score=-101.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=ham
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 iyctjbJvDtEZ; Mon, 11 May 2015 15:19:22 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 89F901A90CF; Mon, 11 May 2015 15:18:42 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1A103180209; Mon, 11 May 2015 15:17:02 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7537 on IANA Registries for LSP Ping Code Points
X-PHP-Originating-Script: 6000:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20150511221702.1A103180209@rfc-editor.org>
Date: Mon, 11 May 2015 15:17:02 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/CewkhLNZSgXSf8eNiVQjhCmbHp8>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: ietf@ietf.org
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: <http://www.ietf.org/mail-archive/web/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: Mon, 11 May 2015 22:19:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7537
Title: IANA Registries for LSP Ping Code Points
Author: B. Decraene, N. Akiya,
C. Pignataro, L. Andersson,
S. Aldrin
Status: Standards Track
Stream: IETF
Date: May 2015
Mailbox: bruno.decraene@orange.com,
nobo.akiya.dev@gmail.com,
cpignata@cisco.com,
loa@mail01.huawei.com,
aldrin.ietf@gmail.com
Pages: 7
Characters: 11895
Updates: RFC 4379, RFC 6424
I-D Tag: draft-ietf-mpls-lsp-ping-registry-03.txt
URL: https://www.rfc-editor.org/info/rfc7537
RFCs 4379 and 6424 created name spaces for Multi-Protocol Label
Switching (MPLS) Label Switched Path (LSP) Ping. However, those RFCs
did not create the corresponding IANA registries for Downstream
Mapping object Flags (DS Flags), Multipath Types, Pad TLVs, and
Interface and Label Stack Address Types.
There is now a need to make further code point allocations from these
name spaces. This document updates RFCs 4379 and 6424 in that it
creates IANA registries for that purpose.
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/rfc.html
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