L2VPN (Re-)charter: Service Convergence
Shane Amante <shane@castlepoint.net> Wed, 02 April 2008 14:02 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 core3.amsl.com (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5DA3D28C1C9; Wed, 2 Apr 2008 07:02:39 -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 A32D828C218 for <l2vpn@core3.amsl.com>; Wed, 2 Apr 2008 07:02:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.573
X-Spam-Level:
X-Spam-Status: No, score=-0.573 tagged_above=-999 required=5 tests=[AWL=-0.056, BAYES_00=-2.599, DNS_FROM_RFC_BOGUSMX=1.482, J_CHICKENPOX_41=0.6]
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 T2nytxhmeHDD for <l2vpn@core3.amsl.com>; Wed, 2 Apr 2008 07:02:37 -0700 (PDT)
Received: from dog.tcb.net (dog.tcb.net [64.78.150.133]) by core3.amsl.com (Postfix) with ESMTP id A85F728C1C9 for <l2vpn@ietf.org>; Wed, 2 Apr 2008 07:02:37 -0700 (PDT)
Received: by dog.tcb.net (Postfix, from userid 0) id BAFD92680CE; Wed, 2 Apr 2008 08:02:38 -0600 (MDT)
Received: from [127.0.0.1] (dog.tcb.net [64.78.150.133]) (authenticated-user smtp) (TLSv1/SSLv3 DHE-RSA-AES256-SHA 256/256) by dog.tcb.net with SMTP; for l2vpn@ietf.org; Wed, 02 Apr 2008 08:02:38 -0600 (MDT) (envelope-from shane@castlepoint.net)
X-Avenger: version=0.7.8; receiver=dog.tcb.net; client-ip=64.78.150.133; client-port=42820; data-bytes=0
Message-ID: <47F391FE.6040804@castlepoint.net>
Date: Wed, 02 Apr 2008 08:02:38 -0600
From: Shane Amante <shane@castlepoint.net>
User-Agent: Thunderbird 2.0.0.12 (Windows/20080213)
MIME-Version: 1.0
To: l2vpn@ietf.org
Subject: L2VPN (Re-)charter: Service Convergence
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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-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
Loa, Florin, Ali, ------Loa wrote------ > - I'm a bit uncertain about whether there are one or two multi-homing > scenarios in the text > -- VPLS using multi-homed CEs > -- multi-homed VPLS solutions See Florin's suggested text below. I think Florin is suggesting to clarify that we need both, (if I interpret your 2nd bullet correctly). ------Florin wrote------ > The L2VPN WG scope includes the following: > [..] > 6. Improved service convergence for multi-homed CE's to VPLS PE's. > Specifically, upon failure of a primary path from a CE to VPLS PE, > initiate a rapid switch-over to an alternate path. If required, > interactions with native service-layer resiliency mechanisms will be > provided via solutions from other IETF WG's such as PWE3. > > FB> Suggest we modify the text to include also multi-homing between 2 > VPLS domains, see below an example of text: > 6. Improved service convergence for multi-homing solutions: CEs to VPLS > PEs or between VPLS domains. Can you clarify this further? Specifically, do you mean the following two cases: a) One CE to two different VPLS PE's in a single AS; and, b) One CE to two different VPLS PE's, each in a different AS? Also, correct me if I'm wrong, but PWE3 has already covered multi-homing of a MTU-s to two, different PE-rs'es in draft-muley-pwe3-redundancy-02? Or, is there addt'l work that L2VPN WG needs to take care of specifically for that case? > Specifically, upon failure of a primary > path from a between CEs and VPLS PEs or between VPLS domains, initiate a > rapid switch-over to an alternate path. If required, interactions with > native service-layer resiliency mechanisms will be provided via > solutions from other IETF WG's such as PWE3. > FB> > > > The L2VPN WG currently works on the following tasks: > [..] > - Identify requirements for multi-homing of CE's to VPLS PE's. > elements. Based on these requirements, define solutions for > achieving fast convergence after a switchover to an alternate path, > for example through optimized MAC flushing within a VPLS domain. > > FB> Suggest changing this one to the following text: > - Identify requirements for different multi-homing solutions: i.e. CEs > to VPLS Pes or between VPLS domains. Based on these requirements, define > solutions for achieving fast convergence after a switchover to an > alternate path, for example through optimized MAC flushing within a VPLS > domain. > FB> I have the same question here as I do above. Once we're on the same page, then I think we can tighten the suggested text a little further. ------Ali wrote------ > v) "6. Improved service convergence for multi-homed CE's to VPLS PE's. > Specifically, upon failure of a primary path from a CE to VPLS PE, > initiate a rapid switch-over to an alternate path. If required, > interactions with native service-layer resiliency mechanisms will be > provided via solutions from other IETF WG's such as PWE3." > > AS> We should create another bullet to include multi-homing between two > or more VPLS networks. Ali: I think you're asking for the same thing as Florin, (see above). If not, please clarify further. Thanks, -shane
- L2VPN (Re-)charter: Service Convergence Shane Amante
- RE: L2VPN (Re-)charter: Service Convergence BALUS Florin
- Re: L2VPN (Re-)charter: Service Convergence Shane Amante
- RE: L2VPN (Re-)charter: Service Convergence BALUS Florin
- Re: L2VPN (Re-)charter: Service Convergence Shane Amante