IETF Logo Mail Archive

RE: Concern regarding draft-kompella-l2vpn-vpls-multihoming-01

"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> Sat, 30 August 2008 06:45 UTC

Return-Path: <l2vpn-bounces@ietf.org>
X-Original-To: l2vpn-archive@megatron.ietf.org
Delivered-To: ietfarch-l2vpn-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 783FA3A688C; Fri, 29 Aug 2008 23:45:00 -0700 (PDT)
X-Original-To: l2vpn@core3.amsl.com
Delivered-To: l2vpn@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id DA3A53A688C for <l2vpn@core3.amsl.com>; Fri, 29 Aug 2008 23:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_FR=0.35]
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 GbLLAqiV4Kag for <l2vpn@core3.amsl.com>; Fri, 29 Aug 2008 23:44:59 -0700 (PDT)
Received: from smail6.alcatel.fr (gc-na5.alcatel.fr [64.208.49.5]) by core3.amsl.com (Postfix) with ESMTP id E2DB83A681E for <l2vpn@ietf.org>; Fri, 29 Aug 2008 23:44:58 -0700 (PDT)
Received: from FRVELSBHS02.ad2.ad.alcatel.com (frvelsbhs02.ad2.ad.alcatel.com [155.132.6.74]) by smail6.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m7U6iKhO020099; Sat, 30 Aug 2008 08:44:20 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.54]) by FRVELSBHS02.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Sat, 30 Aug 2008 08:44:20 +0200
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: Concern regarding draft-kompella-l2vpn-vpls-multihoming-01
Date: Sat, 30 Aug 2008 08:44:50 +0200
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D70326585D@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <8633.1220036492@bhupesh-f8.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Concern regarding draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: AckKEBtGLbn+HdYgRNuNqd0QCqpv5AAW3Bqg
References: <B128F666D4C8BD4FBF56CEAFB2DB66D702F859BF@FRVELSMBS22.ad2.ad.alcatel.com><21222.1217875881@bhupesh-f8.jnpr.net><B128F666D4C8BD4FBF56CEAFB2DB66D70302C011@FRVELSMBS22.ad2.ad.alcatel.com><27924.1217882240@bhupesh-f8.jnpr.net> <B128F666D4C8BD4FBF56CEAFB2DB66D70302C095@FRVELSMBS22.ad2.ad.alcatel.com> <483F121CD2155B43B56DB71228DBAF1502209660@xmb-sjc-239.amer.cisco.com> <B128F666D4C8BD4FBF56CEAFB2DB66D703265842@FRVELSMBS22.ad2.ad.alcatel.com> <8633.1220036492@bhupesh-f8.jnpr.net>
From: HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
To: Bhupesh Kothari <bhupesh@juniper.net>
X-OriginalArrivalTime: 30 Aug 2008 06:44:20.0924 (UTC) FILETIME=[D51177C0:01C90A6B]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.84
Cc: l2vpn@ietf.org, "Ali Sajassi (sajassi)" <sajassi@cisco.com>
X-BeenThere: l2vpn@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <l2vpn.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=unsubscribe>
List-Archive: <https://www.ietf.org/mailman/private/l2vpn>
List-Post: <mailto:l2vpn@ietf.org>
List-Help: <mailto:l2vpn-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/l2vpn>, <mailto:l2vpn-request@ietf.org?subject=subscribe>
Sender: l2vpn-bounces@ietf.org
Errors-To: l2vpn-bounces@ietf.org

Bhupesh,

My main open concern is the modeling of MAC flush in BGP. How do we
ensure with this proposal that the amount of messages remains low.

So in essence I would like to see a proposal how the MAC flush operation
in BGP would be modeled.

Cheers,
Wim

-----Original Message-----
From: Bhupesh Kothari [mailto:bhupesh@juniper.net] 
Sent: vrijdag 29 augustus 2008 21:02
To: HENDERICKX Wim
Cc: Ali Sajassi (sajassi); l2vpn@ietf.org
Subject: Re: Concern regarding draft-kompella-l2vpn-vpls-multihoming-01

Hi Wim,

HENDERICKX Wim <wim.henderickx@alcatel-lucent.be> wrote:

> Ali,
> 
> This is the same concern I raised in the emails before and will be 
> difficult to solve if you let the remote PE(s) make a decision for 
> multi-homing.

I thought I addressed all you MAC flush concerns. :-) 

As I said, MAC flush capability in BGP based VPLS will be added to
address the concern you pointed out (with multiple VE IDs) and other
cases where MAC flush is needed.

Can you be specific on what is your open concern. 

> 
> Cheers,
> Wim

Thanks
Bhupesh

v2.23.0 | Report a Bug | By Email