RFC 6426 on MPLS On-Demand Connectivity Verification and Route Tracing
rfc-editor@rfc-editor.org Wed, 16 November 2011 09:42 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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B01AE21F959B; Wed, 16 Nov 2011 01:42:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.659
X-Spam-Level:
X-Spam-Status: No, score=-104.659 tagged_above=-999 required=5 tests=[AWL=0.418, BAYES_00=-2.599, HELO_MISMATCH_ORG=0.611, HOST_MISMATCH_COM=0.311, J_CHICKENPOX_93=0.6, RCVD_IN_DNSWL_MED=-4, 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 Bya4mOdEf3gn; Wed, 16 Nov 2011 01:42:09 -0800 (PST)
Received: from rfc-editor.org (rfcpa.amsl.com [12.22.58.47]) by ietfa.amsl.com (Postfix) with ESMTP id 1CC9821F959C; Wed, 16 Nov 2011 01:42:09 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 03BCAB1E008; Wed, 16 Nov 2011 01:36:56 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 6426 on MPLS On-Demand Connectivity Verification and Route Tracing
From: rfc-editor@rfc-editor.org
Message-Id: <20111116093656.03BCAB1E008@rfc-editor.org>
Date: Wed, 16 Nov 2011 01:36:56 -0800
Cc: mpls@ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Wed, 16 Nov 2011 09:42:09 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 6426
Title: MPLS On-Demand Connectivity Verification and
Route Tracing
Author: E. Gray, N. Bahadur,
S. Boutros, R. Aggarwal
Status: Standards Track
Stream: IETF
Date: November 2011
Mailbox: eric.gray@ericsson.com,
nitinb@juniper.net,
sboutros@cisco.com,
raggarwa_1@yahoo.com
Pages: 22
Characters: 46539
Updates: RFC4379
I-D Tag: draft-ietf-mpls-tp-on-demand-cv-07.txt
URL: http://www.rfc-editor.org/rfc/rfc6426.txt
Label Switched Path Ping (LSP ping) is an existing and widely
deployed Operations, Administration, and Maintenance (OAM) mechanism
for Multi-Protocol Label Switching (MPLS) Label Switched Paths
(LSPs). This document describes extensions to LSP ping so that LSP
ping can be used for on-demand connectivity verification of MPLS
Transport Profile (MPLS-TP) LSPs and pseudowires. This document also
clarifies procedures to be used for processing the related OAM
packets. Further, it describes procedures for using LSP ping to
perform connectivity verification and route tracing functions in
MPLS-TP networks. Finally, this document updates RFC 4379 by adding
a new address type and creating an IANA registry. [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