RFC 8537 on Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)
rfc-editor@rfc-editor.org Sat, 16 February 2019 01: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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61BFA1289FA; Fri, 15 Feb 2019 17:03:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gfLwBu4lD_xT; Fri, 15 Feb 2019 17:03:27 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [4.31.198.49]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4845E12F1A6; Fri, 15 Feb 2019 17:03:04 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id B28C6B80E87; Fri, 15 Feb 2019 17:02:51 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8537 on Updates to the Fast Reroute Procedures for Co-routed Associated Bidirectional Label Switched Paths (LSPs)
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, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20190216010251.B28C6B80E87@rfc-editor.org>
Date: Fri, 15 Feb 2019 17:02:51 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/rEzF72HnsaejL1qEmU8ZpUqGpj0>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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: <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: Sat, 16 Feb 2019 01:03:31 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8537
Title: Updates to the Fast Reroute
Procedures for Co-routed Associated Bidirectional
Label Switched Paths (LSPs)
Author: R. Gandhi, Ed.,
H. Shah,
J. Whittaker
Status: Standards Track
Stream: IETF
Date: February 2019
Mailbox: rgandhi@cisco.com,
hshah@ciena.com,
jeremy.whittaker@verizon.com
Pages: 16
Characters: 36970
Updates: RFC 4090, RFC 7551
I-D Tag: draft-ietf-teas-assoc-corouted-bidir-frr-07.txt
URL: https://www.rfc-editor.org/info/rfc8537
DOI: 10.17487/RFC8537
Resource Reservation Protocol (RSVP) association signaling can be
used to bind two unidirectional Label Switched Paths (LSPs) into an
associated bidirectional LSP. When an associated bidirectional LSP
is co-routed, the reverse LSP follows the same path as its forward
LSP. This document updates the fast reroute procedures defined in
RFC 4090 to support both single-sided and double-sided provisioned
associated bidirectional LSPs. This document also updates the
procedure for associating two reverse LSPs defined in RFC 7551 to
support co-routed bidirectional LSPs. The fast reroute procedures
can ensure that, for the co-routed LSPs, traffic flows on co-routed
paths in the forward and reverse directions after a failure event.
This document is a product of the Traffic Engineering Architecture and Signaling 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
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
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