[mpls] RFC 8029 on Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures

rfc-editor@rfc-editor.org Fri, 17 March 2017 23:09 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: mpls@ietfa.amsl.com
Delivered-To: mpls@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 5E60312964F; Fri, 17 Mar 2017 16:09:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id H_ZiLn6eFgCV; Fri, 17 Mar 2017 16:09:52 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DBBCA12952D; Fri, 17 Mar 2017 16:09:52 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 07876B80D87; Fri, 17 Mar 2017 16:09:40 -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
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, mpls@ietf.org
Message-Id: <20170317230940.07876B80D87@rfc-editor.org>
Date: Fri, 17 Mar 2017 16:09:40 -0700 (PDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/JKGyHbFKRSrXgaEwmJgmkb7wbD4>
Subject: [mpls] RFC 8029 on Detecting Multiprotocol Label Switched (MPLS) Data-Plane Failures
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: Fri, 17 Mar 2017 23:09:54 -0000

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

        RFC 8029

        Title:      Detecting Multiprotocol Label Switched (MPLS) 
                    Data-Plane Failures 
        Author:     K. Kompella, 
                    G. Swallow,
                    C. Pignataro, Ed.,
                    N. Kumar, 
                    S. Aldrin,
                    M. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2017
        Mailbox:    kireeti.kompella@gmail.com, 
        Pages:      78
        Characters: 174158
        Obsoletes:  RFC 4379, RFC 6424, RFC 6829, RFC 7537
        Updates:    RFC 1122

        I-D Tag:    draft-ietf-mpls-rfc4379bis-09.txt

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

        DOI:        10.17487/RFC8029

This document describes a simple and efficient mechanism to detect
data-plane failures in Multiprotocol Label Switching (MPLS) Label
Switched Paths (LSPs).  It defines a probe message called an "MPLS                       
echo request" and a response message called an "MPLS echo reply" for
returning the result of the probe.  The MPLS echo request is intended
to contain sufficient information to check correct operation of the
data plane and to verify the data plane against the control plane,
thereby localizing faults.

This document obsoletes RFCs 4379, 6424, 6829, and 7537, and updates
RFC 1122.

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

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