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

Bhupesh Kothari <bhupesh@juniper.net> Wed, 06 August 2008 19:08 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 9D6D33A6B05; Wed, 6 Aug 2008 12:08:38 -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 52C603A6972 for <l2vpn@core3.amsl.com>; Wed, 6 Aug 2008 12:08:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.267
X-Spam-Level:
X-Spam-Status: No, score=-6.267 tagged_above=-999 required=5 tests=[AWL=0.332, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 vY1iKdCf6iE1 for <l2vpn@core3.amsl.com>; Wed, 6 Aug 2008 12:08:36 -0700 (PDT)
Received: from exprod7og104.obsmtp.com (exprod7og104.obsmtp.com [64.18.2.161]) by core3.amsl.com (Postfix) with ESMTP id 0202F3A6B26 for <l2vpn@ietf.org>; Wed, 6 Aug 2008 12:08:31 -0700 (PDT)
Received: from source ([66.129.228.6]) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP; Wed, 06 Aug 2008 12:07:47 PDT
Received: from p-emlb02-sac.jnpr.net ([66.129.254.47]) by p-emsmtp03.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Aug 2008 12:09:04 -0700
Received: from emailsmtp55.jnpr.net ([172.24.18.132]) by p-emlb02-sac.jnpr.net with Microsoft SMTPSVC(6.0.3790.3959); Wed, 6 Aug 2008 12:09:03 -0700
Received: from magenta.juniper.net ([172.17.27.123]) by emailsmtp55.jnpr.net with Microsoft SMTPSVC(6.0.3790.1830); Wed, 6 Aug 2008 12:09:03 -0700
Received: from bhupesh-f8.jnpr.net (bhupesh-f8.jnpr.net [172.24.24.195]) by magenta.juniper.net (8.11.3/8.11.3) with ESMTP id m76J93u24282; Wed, 6 Aug 2008 12:09:03 -0700 (PDT) (envelope-from bhupesh@juniper.net)
Received: from bhupesh-f8.jnpr.net (localhost6.localdomain6 [127.0.0.1]) by bhupesh-f8.jnpr.net (8.14.2/8.14.2) with ESMTP id m76J92ud002019; Wed, 6 Aug 2008 12:09:03 -0700
To: HENDERICKX Wim <wim.henderickx@alcatel-lucent.be>
Subject: Re: draft-kompella-l2vpn-vpls-multihoming-01
In-reply-to: <B128F666D4C8BD4FBF56CEAFB2DB66D70302C095@FRVELSMBS22.ad2.ad.alcatel.com>
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>
X-Mailer: MH-E 8.0.3; nmh 1.2-20070115cvs; GNU Emacs 22.1.1
Date: Wed, 06 Aug 2008 12:09:02 -0700
Message-ID: <2018.1218049742@bhupesh-f8.jnpr.net>
From: Bhupesh Kothari <bhupesh@juniper.net>
X-OriginalArrivalTime: 06 Aug 2008 19:09:03.0727 (UTC) FILETIME=[E42E1FF0:01C8F7F7]
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

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 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