[mpls] RFC 8679 on MPLS Egress Protection Framework

rfc-editor@rfc-editor.org Fri, 06 December 2019 21:54 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 4B94F120B74; Fri, 6 Dec 2019 13:54:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 JsE-Zm_qUk28; Fri, 6 Dec 2019 13:54:22 -0800 (PST)
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 240D8120B75; Fri, 6 Dec 2019 13:54:07 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 690A4F4073B; Fri, 6 Dec 2019 13:54:01 -0800 (PST)
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
Content-type: text/plain; charset="UTF-8"
Message-Id: <20191206215401.690A4F4073B@rfc-editor.org>
Date: Fri, 06 Dec 2019 13:54:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/mpls/xjIQ5-CNuVkR034Dee0cLtmaT04>
Subject: [mpls] RFC 8679 on MPLS Egress Protection Framework
X-BeenThere: mpls@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Dec 2019 21:54:27 -0000

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

        RFC 8679

        Title:      MPLS Egress Protection Framework 
        Author:     Y. Shen, 
                    M. Jeganathan,
                    B. Decraene, 
                    H. Gredler,
                    C. Michel,
                    H. Chen
        Status:     Standards Track
        Stream:     IETF
        Date:       December 2019
        Mailbox:    yshen@juniper.net, 
        Pages:      25
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-mpls-egress-protection-framework-07.txt

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

        DOI:        10.17487/RFC8679

This document specifies a fast reroute framework for protecting
IP/MPLS services and MPLS transport tunnels against egress node and
egress link failures. For each type of egress failure, it defines the
roles of Point of Local Repair (PLR), protector, and backup egress
router and the procedures of establishing a bypass tunnel from a PLR
to a protector. It describes the behaviors of these routers in
handling an egress failure, including local repair on the PLR and
context-based forwarding on the protector. The framework can be used
to develop egress protection mechanisms to reduce traffic loss before
global repair reacts to an egress failure and control-plane protocols
converge on the topology changes due to the egress failure.

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