RFC 5439 on An Analysis of Scaling Issues in MPLS-TE Core Networks
rfc-editor@rfc-editor.org Tue, 10 February 2009 00:15 UTC
Return-Path: <rfc-editor@rfc-editor.org>
X-Original-To: ietf-announce@core3.amsl.com
Delivered-To: ietf-announce@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0DA983A6CC9 for <ietf-announce@core3.amsl.com>; Mon, 9 Feb 2009 16:15:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -16.823
X-Spam-Level:
X-Spam-Status: No, score=-16.823 tagged_above=-999 required=5 tests=[AWL=0.776, BAYES_00=-2.599, USER_IN_DEF_WHITELIST=-15]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1xevZQcOZ1R4 for <ietf-announce@core3.amsl.com>; Mon, 9 Feb 2009 16:15:55 -0800 (PST)
Received: from bosco.isi.edu (bosco.isi.edu [128.9.168.207]) by core3.amsl.com (Postfix) with ESMTP id 3C4C03A6C2F for <ietf-announce@ietf.org>; Mon, 9 Feb 2009 16:15:55 -0800 (PST)
Received: by bosco.isi.edu (Postfix, from userid 70) id 1CD4621465B; Mon, 9 Feb 2009 16:15:58 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 5439 on An Analysis of Scaling Issues in MPLS-TE Core Networks
From: rfc-editor@rfc-editor.org
Message-Id: <20090210001558.1CD4621465B@bosco.isi.edu>
Date: Mon, 09 Feb 2009 16:15:58 -0800
Cc: mpls@lists.ietf.org, rfc-editor@rfc-editor.org
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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, 10 Feb 2009 00:15:56 -0000
A new Request for Comments is now available in online RFC libraries. RFC 5439 Title: An Analysis of Scaling Issues in MPLS-TE Core Networks Author: S. Yasukawa, A. Farrel, O. Komolafe Status: Informational Date: February 2009 Mailbox: s.yasukawa@hco.ntt.co.jp, adrian@olddog.co.uk, femi@cisco.com Pages: 45 Characters: 93845 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-mpls-te-scaling-analysis-05.txt URL: http://www.rfc-editor.org/rfc/rfc5439.txt Traffic engineered Multiprotocol Label Switching (MPLS-TE) is deployed in providers' core networks. As providers plan to grow these networks, they need to understand whether existing protocols and implementations can support the network sizes that they are planning. This document presents an analysis of some of the scaling concerns for the number of Label Switching Paths (LSPs) in MPLS-TE core networks, and examines the value of two techniques (LSP hierarchies and multipoint-to-point LSPs) for improving scaling. The intention is to motivate the development of appropriate deployment techniques and protocol extensions to enable the application of MPLS-TE in large networks. This document only considers the question of achieving scalability for the support of point-to-point MPLS-TE LSPs. Point-to-multipoint MPLS-TE LSPs are for future study. This memo provides information for the Internet community. This document is a product of the Multiprotocol Label Switching Working Group of the IETF. INFORMATIONAL: This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF-Announce and rfc-dist lists. To subscribe or unsubscribe, see http://www.ietf.org/mailman/listinfo/ietf-announce http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html. For downloading RFCs, see http://www.rfc-editor.org/rfc.html. 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 USC/Information Sciences Institute