Re: [PWE3] draft-shen-pwe3-endpoint-fast-protection

Yimin Shen <yshen@juniper.net> Fri, 05 August 2011 20:18 UTC

Return-Path: <yshen@juniper.net>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76DCE5E8007 for <pwe3@ietfa.amsl.com>; Fri, 5 Aug 2011 13:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.945
X-Spam-Level:
X-Spam-Status: No, score=-4.945 tagged_above=-999 required=5 tests=[AWL=-0.767, BAYES_00=-2.599, EXTRA_MPART_TYPE=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, SARE_GIF_ATTACH=1.42]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Oz4j0ZP9Xk2Y for <pwe3@ietfa.amsl.com>; Fri, 5 Aug 2011 13:18:17 -0700 (PDT)
Received: from exprod7og103.obsmtp.com (exprod7og103.obsmtp.com [64.18.2.159]) by ietfa.amsl.com (Postfix) with ESMTP id A176421F8B7E for <pwe3@ietf.org>; Fri, 5 Aug 2011 13:18:15 -0700 (PDT)
Received: from P-EMHUB01-HQ.jnpr.net ([66.129.224.36]) (using TLSv1) by exprod7ob103.postini.com ([64.18.6.12]) with SMTP ID DSNKTjxQGQZHc/jJ3VZCdssPJR/5wMMd88hF@postini.com; Fri, 05 Aug 2011 13:18:35 PDT
Received: from p-emfe01-wf.jnpr.net (172.28.145.24) by P-EMHUB01-HQ.jnpr.net (172.24.192.35) with Microsoft SMTP Server (TLS) id 8.2.254.0; Fri, 5 Aug 2011 13:17:10 -0700
Received: from EMBX01-WF.jnpr.net ([fe80::1914:3299:33d9:e43b]) by p-emfe01-wf.jnpr.net ([fe80::d0d1:653d:5b91:a123%11]) with mapi; Fri, 5 Aug 2011 16:17:09 -0400
From: Yimin Shen <yshen@juniper.net>
To: "Shah, Himanshu" <hshah@ciena.com>, "pwe3@ietf.org" <pwe3@ietf.org>
Date: Fri, 05 Aug 2011 16:17:06 -0400
Thread-Topic: draft-shen-pwe3-endpoint-fast-protection
Thread-Index: AcxL2bwGcRIdFPF2To6qN/sR9YKbRQHzpTjA
Message-ID: <DF7F294AF4153D498141CBEFADB17704C2E190C442@EMBX01-WF.jnpr.net>
References: <B37E6A2CE5957F4E83C1D9845A0FFE386E35AB03@MDWEXGMB02.ciena.com>
In-Reply-To: <B37E6A2CE5957F4E83C1D9845A0FFE386E35AB03@MDWEXGMB02.ciena.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: multipart/related; boundary="_004_DF7F294AF4153D498141CBEFADB17704C2E190C442EMBX01WFjnprn_"; type="multipart/alternative"
MIME-Version: 1.0
Subject: Re: [PWE3] draft-shen-pwe3-endpoint-fast-protection
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Pseudo Wires Edge to Edge <pwe3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/pwe3>, <mailto:pwe3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/pwe3>
List-Post: <mailto:pwe3@ietf.org>
List-Help: <mailto:pwe3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/pwe3>, <mailto:pwe3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2011 20:18:18 -0000

Hi Himanshu,

That should be taken care of by global repair. The "local repair" proposed in this draft should be used in conjunction with global repair. The purpose is to provide fast protection before global repair takes effect (slow).

Let's use the AC failure scenario to look at the direction of traffic you mentioned. The CE attached to the failed AC should be able to detect the failure via layer 2 technique or CE-PE OAM, and switch the traffic to the backup AC and backup PW. Meanwhile, the remote CE can also detect the failure via CE-CE OAM, and switch network direction traffic to backup AC and the backup PW. This kind of switching to backup PW and coordination between the CEs are part of global repair. Whatever techniques used here may continue to apply.

Thanks,

-Yimin


From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of Shah, Himanshu
Sent: Tuesday, July 26, 2011 5:20 PM
To: pwe3@ietf.org
Subject: [PWE3] draft-shen-pwe3-endpoint-fast-protection

Yimin -

The draft discusses protection schemes from the network perspective for a dual-homed CE.
In the case of singled-sided protection failover from the networks (which is what is covered
in the draft), how does CE handle the failover for the traffic in network direction (CE->protect-PE).

Do you believe that a protection failover scheme that does not include participation/coordination of dual-homed CE
is a complete solution?

Thanks,
himanshu

[cid:image001.gif@01CC5387.52F17CF0]