Pseudowire (PW) Endpoint Fast Failure Protection (RFC8104)
Original Publication Date: 2017-Mar-01
Included in the Prior Art Database: 2017-Mar-16
Internet Society Requests For Comment (RFCs)
Y. Shen: AUTHOR [+4]
Per [RFC3985], [RFC8077], and [RFC5659], a pseudowire (PW) or PW segment can be thought of as a connection between a pair of forwarders hosted by two PEs, carrying an emulated Layer 2 service over a packet switched network (PSN). In the single-segment PW (SS-PW) case, a forwarder binds a PW to an attachment circuit (AC). In the multi-segment PW (MS-PW) case, a forwarder on a terminating PE (T-PE) binds a PW segment to an AC, while a forwarder on a switching PE (S-PE) binds one PW segment to another PW segment. In each direction between the PEs, PW packets are transported by a PSN tunnel, which is also called a transport tunnel.
Internet Engineering Task Force (IETF) Y. Shen Request for Comments: 8104 Juniper Networks Category: Standards Track R. Aggarwal ISSN: 2070-1721 Arktan, Inc. W. Henderickx Nokia Y. Jiang Huawei Technologies Co., Ltd. March 2017
Pseudowire (PW) Endpoint Fast Failure Protection
This document specifies a fast mechanism for protecting pseudowires (PWs) transported by IP/MPLS tunnels against egress endpoint failures, including egress attachment circuit (AC) failure, egress provider edge (PE) failure, multi-segment PW terminating PE failure, and multi-segment PW switching PE failure. Operating on the basis of multihomed customer edge (CE), redundant PWs, upstream label assignment, and context-specific label switching, the mechanism enables local repair to be performed by the router upstream adjacent to a failure. The router can restore a PW in the order of tens of milliseconds, by rerouting traffic around the failure to a protector through a pre-established bypass tunnel. Therefore, the mechanism can be used to reduce traffic loss before global repair reacts to the failure and the network converges on the topology changes due to the failure.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8104.
Shen, et al. Standards Track [Page 1]
RFC 8104 PW Endpoint Fast Failure Protection March 2017
Copyright (c) 2017 IETF Tru...