[mpls] RFC 7555 on Proxy MPLS Echo Request

rfc-editor@rfc-editor.org Fri, 19 June 2015 01:28 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E50E81B2A3F; Thu, 18 Jun 2015 18:28:57 -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 jSi-k5b8QqKB; Thu, 18 Jun 2015 18:28:55 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1900:3001:11::31]) by ietfa.amsl.com (Postfix) with ESMTP id 9CEA01B2C6F; Thu, 18 Jun 2015 18:28:55 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 36AD818045A; Thu, 18 Jun 2015 18:26:04 -0700 (PDT)
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
Message-Id: <20150619012604.36AD818045A@rfc-editor.org>
Date: Thu, 18 Jun 2015 18:26:04 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/mpls/Qz8lKV3HqeBIrl_Soy9TWS2STCE>
Cc: drafts-update-ref@iana.org, mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 7555 on Proxy MPLS Echo Request
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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: Fri, 19 Jun 2015 01:28:58 -0000

A new Request for Comments is now available in online RFC libraries.

        
        RFC 7555

        Title:      Proxy MPLS Echo Request 
        Author:     G. Swallow, V. Lim, S. Aldrin
        Status:     Standards Track
        Stream:     IETF
        Date:       June 2015
        Mailbox:    swallow@cisco.com, 
                    vlim@cisco.com, 
                    aldrin.ietf@gmail.com
        Pages:      28
        Characters: 62109
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-proxy-lsp-ping-05.txt

        URL:        https://www.rfc-editor.org/info/rfc7555

        DOI:        http://dx.doi.org/10.17487/RFC7555

This document defines a means of remotely initiating Multiprotocol Label
Switched Protocol (MPLS) Pings on Label Switched Paths.  An MPLS Proxy Ping
Request is sent to any Label Switching Router along a Label Switched Path.
The primary motivations for this facility are first to limit the number of
messages and related processing when using LSP Ping in large
Point-to-Multipoint LSPs, and second to enable tracing from leaf to leaf 
(or root).

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