[mpls] RFC 6424 on Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels

rfc-editor@rfc-editor.org Sat, 05 November 2011 01:47 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 74C4A21F891D; Fri, 4 Nov 2011 18:47:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102
X-Spam-Level:
X-Spam-Status: No, score=-102 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4w38iSH+oxU2; Fri, 4 Nov 2011 18:47:13 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 1A1B121F88B7; Fri, 4 Nov 2011 18:47:13 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 1DC5672F0F8; Fri, 4 Nov 2011 18:29:51 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20111105012951.1DC5672F0F8@rfc-editor.org>
Date: Fri, 04 Nov 2011 18:29:51 -0700
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
Subject: [mpls] RFC 6424 on Mechanism for Performing Label Switched Path Ping (LSP Ping) over MPLS Tunnels
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 05 Nov 2011 01:47:13 -0000

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

        
        RFC 6424

        Title:      Mechanism for Performing Label Switched 
                    Path Ping (LSP Ping) over MPLS 
                    Tunnels 
        Author:     N. Bahadur, K. Kompella,
                    G. Swallow
        Status:     Standards Track
        Stream:     IETF
        Date:       November 2011
        Mailbox:    nitinb@juniper.net, 
                    kireeti@juniper.net, 
                    swallow@cisco.com
        Pages:      23
        Characters: 48270
        Updates:    RFC4379

        I-D Tag:    draft-ietf-mpls-lsp-ping-enhanced-dsmap-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6424.txt

This document describes methods for performing LSP ping (specified in
RFC 4379) traceroute over MPLS tunnels and for traceroute of stitched
MPLS Label Switched Paths (LSPs).  The techniques outlined in RFC
4379 are insufficient to perform traceroute Forwarding Equivalency
Class (FEC) validation and path discovery for an LSP that goes over
other MPLS tunnels or for a stitched LSP.  This document deprecates
the Downstream Mapping TLV (defined in RFC 4379) in favor of a new
TLV that, along with other procedures outlined in this document, can
be used to trace such LSPs.  [STANDARDS-TRACK]

This document is a product of the Multiprotocol Label Switching Working Group of the IETF.

This is now a Proposed Standard Protocol.

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 Internet
Official Protocol Standards (STD 1) 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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://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