RFC 7737 on Label Switched Path (LSP) Ping and Traceroute Reply Mode Simplification
rfc-editor@rfc-editor.org Sat, 23 January 2016 00:28 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 0B61A1B2DCC; Fri, 22 Jan 2016 16:28:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.903
X-Spam-Level:
X-Spam-Status: No, score=-106.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, 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 AIgNzjn6zzfb; Fri, 22 Jan 2016 16:28:23 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) by ietfa.amsl.com (Postfix) with ESMTP id 768CA1B2DFF; Fri, 22 Jan 2016 16:27:56 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6300818046A; Fri, 22 Jan 2016 16:26:37 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7737 on Label Switched Path (LSP) Ping and Traceroute Reply Mode Simplification
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160123002637.6300818046A@rfc-editor.org>
Date: Fri, 22 Jan 2016 16:26:37 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/0tEA5Fi6AedaUGb6dbJg6YjTyrA>
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: <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: Sat, 23 Jan 2016 00:28:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 7737
Title: Label Switched Path (LSP) Ping
and Traceroute Reply Mode Simplification
Author: N. Akiya, G. Swallow,
C. Pignataro, L. Andersson, M. Chen
Status: Standards Track
Stream: IETF
Date: January 2016
Mailbox: nobo.akiya.dev@gmail.com,
swallow@cisco.com,
cpignata@cisco.com,
loa@mail01.huawei.com,
mach.chen@huawei.com
Pages: 17
Characters: 35253
Updates: RFC 7110
I-D Tag: draft-ietf-mpls-lsp-ping-reply-mode-simple-05.txt
URL: https://www.rfc-editor.org/info/rfc7737
DOI: http://dx.doi.org/10.17487/RFC7737
The Multiprotocol Label Switching (MPLS) Label Switched Path (LSP)
Ping and Traceroute use the Reply Mode field to signal the method to
be used in the MPLS echo reply. This document updates the procedures
for the "Reply via Specified Path" Reply Mode. The value of this
Reply Mode is 5. The update creates a simple way to indicate that
the reverse LSP should be used as the return path. This document
also adds an optional TLV that can carry an ordered list of Reply
Mode values.
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