IETF Logo Mail Archive

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

"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> Thu, 07 August 2008 04:48 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 24DAD3A6A73; Wed, 6 Aug 2008 21:48:24 -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 8EC893A6A73 for <l2vpn@core3.amsl.com>; Wed, 6 Aug 2008 21:48:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level:
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[AWL=0.152, 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 or6o16pIRGYN for <l2vpn@core3.amsl.com>; Wed, 6 Aug 2008 21:48:21 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [62.23.212.27]) by core3.amsl.com (Postfix) with ESMTP id 4C2943A6A10 for <l2vpn@ietf.org>; Wed, 6 Aug 2008 21:48:20 -0700 (PDT)
Received: from FRVELSBHS04.ad2.ad.alcatel.com (frvelsbhs04.ad2.ad.alcatel.com [155.132.6.76]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m774mTqr022760; Thu, 7 Aug 2008 06:48:32 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS04.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Thu, 7 Aug 2008 06:48:29 +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: draft-kompella-l2vpn-vpls-multihoming-01
Date: Thu, 07 Aug 2008 06:48:33 +0200
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D70302C61A@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <2018.1218049742@bhupesh-f8.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acj39+vcpnJgjlgNRXSgNizg3I220gAUNXmA
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> <2018.1218049742@bhupesh-f8.jnpr.net>
From: HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
To: Bhupesh Kothari <bhupesh@juniper.net>
X-OriginalArrivalTime: 07 Aug 2008 04:48:29.0007 (UTC) FILETIME=[D5E6DDF0:01C8F848]
X-Scanned-By: MIMEDefang 2.57 on 155.132.188.13
Cc: l2vpn@ietf.org
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

Thx for clarification, which BGP message do you envisage to use for this
purpose ?

-----Original Message-----
From: Bhupesh Kothari [mailto:bhupesh@juniper.net] 
Sent: woensdag 6 augustus 2008 21:09
To: HENDERICKX Wim
Cc: l2vpn@ietf.org
Subject: Re: draft-kompella-l2vpn-vpls-multihoming-01

HENDERICKX Wim <wim.henderickx@alcatel-lucent.be> wrote:
> > As you mentioned below we should extend the solution with a MAC 
> > flush capability like LDP does today.
> 
> Yes, we'll add the explicit flush.  The explicit flush capability 
> provides optimization at the expense of more state in the control 
> plane as now the PEs need to track the MACs learned in forwarding so 
> that those can be withdrawn later on.
> 
> 
> WH> How would this work? E.g. in the example we use PE3 has no 
> WH> awareness
> of the Mac @ belonging to which CE on a given PE.
> 

I should have been more clear.  A MAC flush message from PE1 containing
a list of MACs will be sufficient for this purpose.

Bhupesh

v2.23.0 | Report a Bug | By Email