[Teas] RFC 8370 on Techniques to Improve the Scalability of RSVP-TE Deployments
rfc-editor@rfc-editor.org Sat, 12 May 2018 00:20 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 BB4CA12D7F3; Fri, 11 May 2018 17:20:58 -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 gVW4QpPzpWks; Fri, 11 May 2018 17:20:57 -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 66688129C5D; Fri, 11 May 2018 17:20:57 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 0A938B82DB4; Fri, 11 May 2018 17:20:54 -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: <20180512002055.0A938B82DB4@rfc-editor.org>
Date: Fri, 11 May 2018 17:20:54 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/teas/k4Vgpre3uGjN7yx16QI9xd5-e5Q>
Subject: [Teas] RFC 8370 on Techniques to Improve the Scalability of RSVP-TE Deployments
X-BeenThere: teas@ietf.org
X-Mailman-Version: 2.1.22
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: Sat, 12 May 2018 00:20:59 -0000
A new Request for Comments is now available in online RFC libraries. RFC 8370 Title: Techniques to Improve the Scalability of RSVP-TE Deployments Author: V. Beeram, Ed., I. Minei, R. Shakir, D. Pacella, T. Saad Status: Standards Track Stream: IETF Date: May 2018 Mailbox: vbeeram@juniper.net, inaminei@google.com, rjs@rob.sh, dante.j.pacella@verizon.com, tsaad@cisco.com Pages: 11 Characters: 21622 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-teas-rsvp-te-scaling-rec-09.txt URL: https://www.rfc-editor.org/info/rfc8370 DOI: 10.17487/RFC8370 Networks that utilize RSVP-TE LSPs are encountering implementations that have a limited ability to support the growth in the number of LSPs deployed. This document defines two techniques, Refresh-Interval Independent RSVP (RI-RSVP) and Per-Peer Flow Control, that reduce the number of processing cycles required to maintain RSVP-TE LSP state in Label Switching Routers (LSRs) and hence allow implementations to support larger scale deployments. 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