RFC 8796 on RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) Tunnels
rfc-editor@rfc-editor.org Tue, 14 July 2020 23:24 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 66D963A0645; Tue, 14 Jul 2020 16:24:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 i1PsM9wpOf_1; Tue, 14 Jul 2020 16:24:22 -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 E35BF3A003B; Tue, 14 Jul 2020 16:24:22 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id E3AF8F40743; Tue, 14 Jul 2020 16:24:19 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 8796 on RSVP-TE Summary Fast Reroute Extensions for Label Switched Path (LSP) Tunnels
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: <20200714232419.E3AF8F40743@rfc-editor.org>
Date: Tue, 14 Jul 2020 16:24:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/jarjZaV9L65Flar57V0bQTq06fA>
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: Tue, 14 Jul 2020 23:24:25 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8796
Title: RSVP-TE Summary Fast Reroute Extensions
for Label Switched Path (LSP) Tunnels
Author: M. Taillon,
T. Saad, Ed.,
R. Gandhi,
A. Deshmukh,
M. Jork,
V. Beeram
Status: Standards Track
Stream: IETF
Date: July 2020
Mailbox: mtaillon@cisco.com,
tsaad@juniper.net,
rgandhi@cisco.com,
adeshmukh@juniper.net,
mjork@128technology.com,
vbeeram@juniper.net
Pages: 18
Updates: RFC 4090
I-D Tag: draft-ietf-mpls-summary-frr-rsvpte-09.txt
URL: https://www.rfc-editor.org/info/rfc8796
DOI: 10.17487/RFC8796
This document updates RFC 4090 for the Resource Reservation Protocol
(RSVP) Traffic Engineering (TE) procedures defined for facility
backup protection. The updates include extensions that reduce the
amount of signaling and processing that occurs during Fast Reroute
(FRR); as a result, scalability when undergoing FRR convergence after
a link or node failure is improved. These extensions allow the RSVP
message exchange between the Point of Local Repair (PLR) and the
Merge Point (MP) nodes to be independent of the number of protected
Label Switched Paths (LSPs) traversing between them when facility
bypass FRR protection is used. The signaling extensions are fully
backwards compatible with nodes that do not support them.
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
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