RFC 7715 on Multipoint LDP (mLDP) Node Protection

rfc-editor@rfc-editor.org Fri, 08 January 2016 19:03 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 []) by ietfa.amsl.com (Postfix) with ESMTP id F39211B2ADF; Fri, 8 Jan 2016 11:03:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.912
X-Spam-Status: No, score=-106.912 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, 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 ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id xCAnkmAgVjK0; Fri, 8 Jan 2016 11:03:24 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org []) by ietfa.amsl.com (Postfix) with ESMTP id 0471C1ABC75; Fri, 8 Jan 2016 11:03:24 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 6E5B0180092; Fri, 8 Jan 2016 11:02:21 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 7715 on Multipoint LDP (mLDP) Node Protection
X-PHP-Originating-Script: 1005:ams_util_lib.php
From: rfc-editor@rfc-editor.org
Message-Id: <20160108190221.6E5B0180092@rfc-editor.org>
Date: Fri, 08 Jan 2016 11:02:21 -0800
Archived-At: <http://mailarchive.ietf.org/arch/msg/ietf-announce/l9zieEw-s1G_HrgdWlj9BIvqd6M>
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: Fri, 08 Jan 2016 19:03:31 -0000

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

        RFC 7715

        Title:      Multipoint LDP (mLDP) Node Protection 
        Author:     IJ. Wijnands, Ed.,
                    K. Raza,
                    A. Atlas,
                    J. Tantsura,
                    Q. Zhao
        Status:     Standards Track
        Stream:     IETF
        Date:       January 2016
        Mailbox:    ice@cisco.com, 
        Pages:      19
        Characters: 39353
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-mldp-node-protection-08.txt

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

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

This document describes procedures to support node protection for
Point-to-Multipoint and Multipoint-to-Multipoint Label Switched Paths
(P2MP and MP2MP LSPs) that have been built by the Multipoint Label
Distribution Protocol (mLDP).  In order to protect a node N, the
Point of Local Repair (PLR) Label Switching Router (LSR) of N must
learn the Merge Point (MPT) LSR(s) of node N such that traffic can be
redirected to them in case node N fails.  Redirecting the traffic
around the failed node N depends on existing Point-to-Point (P2P)
Label Switched Paths (LSPs).  The pre-established LSPs originate from
the PLR LSR and terminate on the MPT LSRs while bypassing LSR N.

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/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