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

"HENDERICKX Wim" <wim.henderickx@alcatel-lucent.be> Tue, 05 August 2008 07:54 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 B402A3A69DA; Tue, 5 Aug 2008 00:54:37 -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 574E93A69DA for <l2vpn@core3.amsl.com>; Tue, 5 Aug 2008 00:54:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.063
X-Spam-Level:
X-Spam-Status: No, score=-2.063 tagged_above=-999 required=5 tests=[AWL=0.186, 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 t+BGCio-3BZG for <l2vpn@core3.amsl.com>; Tue, 5 Aug 2008 00:54:35 -0700 (PDT)
Received: from smail5.alcatel.fr (smail5.alcatel.fr [64.208.49.27]) by core3.amsl.com (Postfix) with ESMTP id B6A493A695A for <l2vpn@ietf.org>; Tue, 5 Aug 2008 00:54:34 -0700 (PDT)
Received: from FRVELSBHS03.ad2.ad.alcatel.com (frvelsbhs03.ad2.ad.alcatel.com [155.132.6.75]) by smail5.alcatel.fr (8.13.8/8.13.8/ICT) with ESMTP id m757t1F1007156; Tue, 5 Aug 2008 09:55:01 +0200
Received: from FRVELSMBS22.ad2.ad.alcatel.com ([155.132.6.51]) by FRVELSBHS03.ad2.ad.alcatel.com with Microsoft SMTPSVC(6.0.3790.2499); Tue, 5 Aug 2008 09:55:01 +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: Tue, 05 Aug 2008 09:55:01 +0200
Message-ID: <B128F666D4C8BD4FBF56CEAFB2DB66D70302C095@FRVELSMBS22.ad2.ad.alcatel.com>
In-Reply-To: <27924.1217882240@bhupesh-f8.jnpr.net>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: draft-kompella-l2vpn-vpls-multihoming-01
Thread-Index: Acj2cfusbpP5APx1QhmSP06sW6dyZwATRPJQ
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>
From: HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
To: Bhupesh Kothari <bhupesh@juniper.net>
X-OriginalArrivalTime: 05 Aug 2008 07:55:01.0364 (UTC) FILETIME=[903D8340:01C8F6D0]
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

Bhupesh, thx more in-line

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

Hi Wim,

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

> Bhupesh,
> 
> Thanks, In this case does the solution allows 2 different designated 
> forwarder for 2 different VE(s) on the same PE as per the example
below.
> I would assume it does. PE3 would have to maintain a PW to each PE 
> (PE1 and PE2 in the example).

Not necessary. The existence of PWs is independent of how we will flush
MACs.  Consider that VE1 is VE ID 1, VE2 is VE ID 2 and VE3 for
PE3 is VE ID
3.  

Assumes that PE1 is "better" than PE2 for both VE1 and VE2 (based on
preference).  In this case:

-  PE1 will have one PW to PE3 (between IDs 1 and 3). 
-  PE2 will have no PW.
-  PE3 will have one PW to PE1 (between IDs 3 and 1). 

In this case, for both customer sites, CE1 and CE2, PE1 is the
designated forwarder. 


If PE2 is better for VE2 and PE1 is better for VE1, then:

- PE1 (ID 1) will have a PW to PE2 (ID 2) and PE3 (ID 3)
- PE2 (ID 2) will have a PW to PE1 (ID 1) and PE3 (ID 3)
- PE3 (ID 3) will have a PW to PE1 (ID 1) and PE2 (ID 2)

In this case, CE1 traffic is through PE1 and CE2 traffic is through PE2.

In either case, the goal is to have an implicit or an explicit flush
that will flush only the MACs that need to be.  Note that BGP VPLS has
implicit flush semantics as it is aware of multi-homed sites.

WH> Indeed this is what I meant. Thx for clarifying


> 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 awareness
of the Mac @ belonging to which CE on a given PE.

> 
> Cheers,
> Wim

Thanks
Bhupesh