[mpls] RFC 9214 on OSPFv3 Code Point for MPLS LSP Ping
rfc-editor@rfc-editor.org Thu, 14 April 2022 05:06 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18FC63A07CE; Wed, 13 Apr 2022 22:06:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.659
X-Spam-Level:
X-Spam-Status: No, score=-6.659 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 denyrb0NIxvP; Wed, 13 Apr 2022 22:06:36 -0700 (PDT)
Received: from rfcpa.amsl.com (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6B7063A07A7; Wed, 13 Apr 2022 22:06:36 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 2AB02EB6B4; Wed, 13 Apr 2022 22:06:36 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20220414050636.2AB02EB6B4@rfcpa.amsl.com>
Date: Wed, 13 Apr 2022 22:06:36 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/2VO9oQbcq_dFeSW_s1S_lbx10Go>
Subject: [mpls] RFC 9214 on OSPFv3 Code Point for MPLS LSP Ping
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Multi-Protocol Label Switching WG <mpls.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/mpls>, <mailto:mpls-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/mpls/>
List-Post: <mailto:mpls@ietf.org>
List-Help: <mailto:mpls-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/mpls>, <mailto:mpls-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Apr 2022 05:06:44 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9214
Title: OSPFv3 Code Point for MPLS LSP Ping
Author: N. Nainar,
C. Pignataro,
M. Aissaoui
Status: Standards Track
Stream: IETF
Date: April 2022
Mailbox: naikumar@cisco.com,
cpignata@cisco.com,
mustapha.aissaoui@nokia.com
Pages: 6
Updates: RFC 8287
I-D Tag: draft-ietf-mpls-lsp-ping-ospfv3-codepoint-06.txt
URL: https://www.rfc-editor.org/info/rfc9214
DOI: 10.17487/RFC9214
IANA has created "Protocol in the Segment ID Sub-TLV" and "Protocol
in Label Stack Sub-TLV of Downstream Detailed Mapping TLV" registries
under the "Multiprotocol Label Switching (MPLS) Label Switched Paths
(LSPs) Ping Parameters" registry. RFC 8287 defines the code points
for Open Shortest Path First (OSPF) and Intermediate System to
Intermediate System (IS-IS) protocols.
This document specifies the code point to be used in the Segment ID
sub-TLV and Downstream Detailed Mapping (DDMAP) TLV when the Interior
Gateway Protocol (IGP) is OSPFv3. This document also updates RFC 8287
by clarifying that the existing "OSPF" code point is to be used only
to indicate OSPFv2 and by defining the behavior when the Segment ID
sub-TLV indicates the use of IPv6.
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