[mpls] RFC 8287 on Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
rfc-editor@rfc-editor.org Thu, 21 December 2017 18:00 UTC
Return-Path: <wwwrun@rfc-editor.org>
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 549CA12D778; Thu, 21 Dec 2017 10:00:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level:
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-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 5X6-4ghsOJRD; Thu, 21 Dec 2017 10:00:21 -0800 (PST)
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 A10F3126B71; Thu, 21 Dec 2017 10:00:21 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B3960B81269; Thu, 21 Dec 2017 10:00:18 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
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: <20171221180018.B3960B81269@rfc-editor.org>
Date: Thu, 21 Dec 2017 10:00:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/x8hTy6pjNRe84QHujfQ811pEZ3I>
Subject: [mpls] RFC 8287 on Label Switched Path (LSP) Ping/Traceroute for Segment Routing (SR) IGP-Prefix and IGP-Adjacency Segment Identifiers (SIDs) with MPLS Data Planes
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.22
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, 21 Dec 2017 18:00:23 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8287
Title: Label Switched Path (LSP) Ping/Traceroute
for Segment Routing (SR) IGP-Prefix and
IGP-Adjacency Segment Identifiers (SIDs) with MPLS
Data Planes
Author: N. Kumar, Ed.,
C. Pignataro, Ed.,
G. Swallow,
N. Akiya,
S. Kini,
M. Chen
Status: Standards Track
Stream: IETF
Date: December 2017
Mailbox: naikumar@cisco.com,
cpignata@cisco.com,
swallow.ietf@gmail.com,
nobo.akiya.dev@gmail.com,
sriganeshkini@gmail.com,
mach.chen@huawei.com
Pages: 25
Characters: 49976
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-mpls-spring-lsp-ping-13.txt
URL: https://www.rfc-editor.org/info/rfc8287
DOI: 10.17487/RFC8287
A Segment Routing (SR) architecture leverages source routing and
tunneling paradigms and can be directly applied to the use of a
Multiprotocol Label Switching (MPLS) data plane. A node steers a
packet through a controlled set of instructions called "segments" by
prepending the packet with an SR header.
The segment assignment and forwarding semantic nature of SR raises
additional considerations for connectivity verification and fault
isolation for a Label Switched Path (LSP) within an SR architecture.
This document illustrates the problem and defines extensions to
perform LSP Ping and Traceroute for Segment Routing IGP-Prefix and
IGP-Adjacency Segment Identifiers (SIDs) with an MPLS data plane.
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