RE: updated draft-gs-l3vpn-scaling & agenda request
"Daniel Cohn" <DanielC@orckit.com> Tue, 13 March 2012 08:30 UTC
Return-Path: <DanielC@orckit.com>
X-Original-To: l3vpn@ietfa.amsl.com
Delivered-To: l3vpn@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A533721F8822; Tue, 13 Mar 2012 01:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.239
X-Spam-Level:
X-Spam-Status: No, score=-2.239 tagged_above=-999 required=5 tests=[AWL=-0.240, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Klgi0nvbz4Px; Tue, 13 Mar 2012 01:30:24 -0700 (PDT)
Received: from tlvmail1.orckit.com (tlvmail1.orckit.com [109.226.33.14]) by ietfa.amsl.com (Postfix) with ESMTP id 81FAB21F8821; Tue, 13 Mar 2012 01:30:24 -0700 (PDT)
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: updated draft-gs-l3vpn-scaling & agenda request
Date: Tue, 13 Mar 2012 10:30:23 +0200
Message-ID: <44F4E579A764584EA9BDFD07D0CA081307670B03@tlvmail1>
In-Reply-To: <DCC302FAA9FE5F4BBA4DCAD465693779173B637798@PRVPEXVS03.corp.twcable.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: updated draft-gs-l3vpn-scaling & agenda request
Thread-Index: Acz73jZNIwy3VR2RQveW+x31Ps+7zAFD1zjg
References: <DCC302FAA9FE5F4BBA4DCAD465693779173B637798@PRVPEXVS03.corp.twcable.com>
From: Daniel Cohn <DanielC@orckit.com>
To: "George, Wes" <wesley.george@twcable.com>, l3vpn@ietf.org
Cc: rtgarea-ads@ietf.org, rtgwg-chairs@ietf.org
X-BeenThere: l3vpn@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <l3vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/l3vpn>
List-Post: <mailto:l3vpn@ietf.org>
List-Help: <mailto:l3vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l3vpn>, <mailto:l3vpn-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Mar 2012 08:30:25 -0000
Hi Wes and Rob, First of all thanks for writing this draft, it does a great job of compiling L3VPN scalability issues in one place and I think it will be very helpful for developers and operators. Few questions/comments: - I understand/agree with the general assertion that BGP is inherently more scalable than IGPs, also in PE-CE application. But I don't understand the statement that "(IGPs) invoke additional processes on the router when compared to simply using BGP (which is already going be running on a router using MP-BGP for VPNs"). This is because even if BGP is already running on the router as PE-PE protocol, using BGP as PE-CE protocol will also typically required "additional processes" in the router as each BGP instance will typically run on a separate BGP process. Barring specification implementations, I don't see how BGP and IGPs as PE-CE differ in this aspect. - In the following paragraph: "Where it may be possible to assign a single RD per L3VPN instance, and hence achieve some level of route aggregation on BGP speakers within the solution, this has some consequences for both convergence in the VPN (due to BGP convergence being relied upon) and in its potential to exacerbate geographic distance between PE and Route-reflector and is therefore undesirable in some circumstances" Are you referring to multiple-homed CE scenario, where the same NLRI will be advertised with different BGP next hops if the same RD is used? If yes, I think it should be clarified. If not, can you please explain to which scenario you refer? Also, what do you mean by "exacerbate geographic distance"? I don't understand the meaning of this expression nor the problem it describes. - Regarding the maximum number of routes per VRF limit, I think there should be some discussion on the PE behavior when the limit is reached, e.g.: what do you expect PE-CE and PE-PE protocols should do with routes they receive after the limit has been reached? Should these routes be stored and installed at the VRF when the route count goes below the limit (plus some hysteresis threshold of course)? Or should they also be discarded by the PE-CE/PE-PE routing protocols? If discarded, how will you resync with the neighbors/peers once the route count goes below the limit? Regards, Daniel -----Original Message----- From: l3vpn-bounces@ietf.org [mailto:l3vpn-bounces@ietf.org] On Behalf Of George, Wes Sent: Tuesday, March 06, 2012 11:27 PM To: l3vpn@ietf.org Cc: rtgarea-ads@ietf.org; rtgwg-chairs@ietf.org Subject: updated draft-gs-l3vpn-scaling & agenda request Hello all - Rob and I have completed a revision of our draft discussing L3VPN scaling considerations. We've made some changes to the document structure to make it flow better, and we think that we've added enough of the body that it is ready for discussion during a WG meeting. However, since L3VPN is not meeting during IETF in Paris, we're wondering if we should perhaps ask for time in the Routing area open meeting/RTGAREA WG instead? Either way, comments are still very welcome, especially if you can help us bolster the currently weak section on multicast VPN scale. Abstract This document discusses scaling considerations unique to implementation of Layer 3 (IP) Virtual Private Networks, discusses a few best practices, and identifies gaps in the current tools and techniques which are making it more difficult for operators to cost- effectively scale and manage their L3VPN deployments. http://tools.ietf.org/html/draft-gs-vpn-scaling-01 Thanks, Wes George This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
- updated draft-gs-l3vpn-scaling & agenda request George, Wes
- RE: updated draft-gs-l3vpn-scaling & agenda reque… stephane.litkowski
- RE: updated draft-gs-l3vpn-scaling & agenda reque… Rajiv Asati (rajiva)
- RE: updated draft-gs-l3vpn-scaling & agenda reque… George, Wes
- RE: updated draft-gs-l3vpn-scaling & agenda reque… George, Wes
- Re: updated draft-gs-l3vpn-scaling & agenda reque… Robert Raszuk
- RE: updated draft-gs-l3vpn-scaling & agenda reque… Daniel Cohn
- Re: updated draft-gs-l3vpn-scaling & agenda reque… Robert Raszuk
- RE: updated draft-gs-l3vpn-scaling & agenda reque… Daniel Cohn
- Re: updated draft-gs-l3vpn-scaling & agenda reque… Robert Raszuk
- RE: updated draft-gs-l3vpn-scaling & agenda reque… George, Wes
- Re: updated draft-gs-l3vpn-scaling & agenda reque… Robert Raszuk