RFC 8271 on Updates to the Resource Reservation Protocol for Fast Reroute of Traffic Engineering GMPLS Label Switched Paths (LSPs)
rfc-editor@rfc-editor.org Wed, 01 November 2017 04:54 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 6170D13FB54; Tue, 31 Oct 2017 21:54:57 -0700 (PDT)
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 GJEU6FTku5EO; Tue, 31 Oct 2017 21:54:55 -0700 (PDT)
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 5CA4313FB68; Tue, 31 Oct 2017 21:54:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 92F34B81736; Tue, 31 Oct 2017 21:54:13 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8271 on Updates to the Resource Reservation Protocol for Fast Reroute of Traffic Engineering GMPLS 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: <20171101045413.92F34B81736@rfc-editor.org>
Date: Tue, 31 Oct 2017 21:54:13 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/i24xrQtH7H2n5ososZf7cn2uP0M>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 01 Nov 2017 04:54:57 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8271
Title: Updates to the Resource Reservation
Protocol for Fast Reroute of Traffic
Engineering GMPLS Label Switched Paths (LSPs)
Author: M. Taillon,
T. Saad, Ed.,
R. Gandhi, Ed.,
Z. Ali,
M. Bhatia
Status: Standards Track
Stream: IETF
Date: October 2017
Mailbox: mtaillon@cisco.com,
tsaad@cisco.com,
rgandhi@cisco.com,
zali@cisco.com,
manav.bhatia@nokia.com
Pages: 24
Characters: 53407
Updates: RFC 4090
I-D Tag: draft-ietf-teas-gmpls-lsp-fastreroute-12.txt
URL: https://www.rfc-editor.org/info/rfc8271
DOI: 10.17487/RFC8271
This document updates the Resource Reservation Protocol - Traffic
Engineering (RSVP-TE) Fast Reroute (FRR) procedures defined in
RFC 4090 to support Packet Switch Capable (PSC) Generalized
Multiprotocol Label Switching (GMPLS) Label Switched Paths (LSPs).
These updates allow the coordination of a bidirectional bypass tunnel
assignment protecting a common facility in both forward and reverse
directions of a co-routed bidirectional LSP. In addition, these
updates enable the redirection of bidirectional traffic onto bypass
tunnels that ensure the co-routing of data paths in the forward and
reverse directions after FRR and avoid RSVP soft-state timeout in the
control plane.
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