Last Call: <draft-ietf-mpls-ri-rsvp-frr-07.txt> (Refresh-interval Independent FRR Facility Protection) to Proposed Standard
The IESG <iesg-secretary@ietf.org> Tue, 22 October 2019 19:18 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietf.org
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 184F71208E8; Tue, 22 Oct 2019 12:18:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: Last Call: <draft-ietf-mpls-ri-rsvp-frr-07.txt> (Refresh-interval Independent FRR Facility Protection) to Proposed Standard
X-Test-IDTracker: no
X-IETF-IDTracker: 6.107.0
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
CC: mpls@ietf.org, db3546@att.com, draft-ietf-mpls-ri-rsvp-frr@ietf.org, mpls-chairs@ietf.org, n.leymann@telekom.de, Nicolai Leymann <n.leymann@telekom.de>
Content-Transfer-Encoding: 7bit
Reply-To: last-call@ietf.org
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Message-ID: <157177189902.2858.15375992162460587321.idtracker@ietfa.amsl.com>
Date: Tue, 22 Oct 2019 12:18:19 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/aXsjKBdly5T6LALfSlsfBUkwM2g>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Oct 2019 19:18:19 -0000
The IESG has received a request from the Multiprotocol Label Switching WG (mpls) to consider the following document: - 'Refresh-interval Independent FRR Facility Protection' <draft-ietf-mpls-ri-rsvp-frr-07.txt> as Proposed Standard The IESG plans to make a decision in the next few weeks, and solicits final comments on this action. Please send substantive comments to the last-call@ietf.org mailing lists by 2019-11-05. Exceptionally, comments may be sent to iesg@ietf.org instead. In either case, please retain the beginning of the Subject line to allow automated sorting. Abstract RSVP-TE Fast ReRoute extensions specified in RFC 4090 defines two local repair techniques to reroute Label Switched Path (LSP) traffic over pre-established backup tunnel. Facility backup method allows one or more LSPs traversing a connected link or node to be protected using a bypass tunnel. The many-to-one nature of local repair technique is attractive from scalability point of view. This document enumerates facility backup procedures in RFC 4090 that rely on refresh timeout and hence make facility backup method refresh- interval dependent. The RSVP-TE extensions defined in this document will enhance the facility backup protection mechanism by making the corresponding procedures refresh-interval independent and hence compatible with Refresh-interval Independent RSVP (RI-RSVP) specified in RFC 8370. Hence, this document updates RFC 4090 in order to support RI-RSVP capability specified in RFC 8370. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-mpls-ri-rsvp-frr/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-mpls-ri-rsvp-frr/ballot/ The following IPR Declarations may be related to this I-D: https://datatracker.ietf.org/ipr/3672/ https://datatracker.ietf.org/ipr/2580/ https://datatracker.ietf.org/ipr/3671/ The document contains these normative downward references. See RFC 3967 for additional information: draft-ietf-mpls-summary-frr-rsvpte: RSVP-TE Summary Fast Reroute Extensions for LSP Tunnels (None - IETF stream)