[Teas] RFC 8424 on Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) Protection
rfc-editor@rfc-editor.org Mon, 20 August 2018 23:56 UTC
Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: teas@ietfa.amsl.com
Delivered-To: teas@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DD0E5130E96; Mon, 20 Aug 2018 16:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 5iGrVAa5pKkF; Mon, 20 Aug 2018 16:56:37 -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 CCEE6130E6C; Mon, 20 Aug 2018 16:56:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id ED7A2B80500; Mon, 20 Aug 2018 16:56:24 -0700 (PDT)
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, teas@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20180820235624.ED7A2B80500@rfc-editor.org>
Date: Mon, 20 Aug 2018 16:56:24 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/jEEysCh_8drZME-Lrp126c7lrOk>
Subject: [Teas] RFC 8424 on Extensions to RSVP-TE for Label Switched Path (LSP) Ingress Fast Reroute (FRR) Protection
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Traffic Engineering Architecture and Signaling working group discussion list <teas.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/teas>, <mailto:teas-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/teas/>
List-Post: <mailto:teas@ietf.org>
List-Help: <mailto:teas-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/teas>, <mailto:teas-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 20 Aug 2018 23:56:53 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 8424
Title: Extensions to RSVP-TE for Label Switched Path (LSP)
Ingress Fast Reroute (FRR) Protection
Author: H. Chen, Ed.,
R. Torvi, Ed.
Status: Experimental
Stream: IETF
Date: August 2018
Mailbox: huaimo.chen@huawei.com,
rtorvi@juniper.net
Pages: 28
Characters: 62022
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-teas-rsvp-ingress-protection-17.txt
URL: https://www.rfc-editor.org/info/rfc8424
DOI: 10.17487/RFC8424
This document describes extensions to Resource Reservation Protocol -
Traffic Engineering (RSVP-TE) for locally protecting the ingress node
of a Point-to-Point (P2P) or Point-to-Multipoint (P2MP) Traffic
Engineered (TE) Label Switched Path (LSP). It extends the Fast
Reroute (FRR) protection for transit nodes of an LSP to the ingress
node of the LSP. The procedures described in this document are
experimental.
This document is a product of the Traffic Engineering Architecture and Signaling Working Group of the IETF.
EXPERIMENTAL: This memo defines an Experimental Protocol for the
Internet community. It does not specify an Internet standard of any
kind. Discussion and suggestions for improvement are requested.
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