Re: [PWE3] Poll for WG adoption of draft-shen-pwe3-endpoint-fast-protection-04

Mingui Zhang <zhangmingui@huawei.com> Tue, 03 September 2013 01:51 UTC

Return-Path: <zhangmingui@huawei.com>
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 B199C21F9263 for <pwe3@ietfa.amsl.com>; Mon, 2 Sep 2013 18:51:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.198
X-Spam-Level:
X-Spam-Status: No, score=-7.198 tagged_above=-999 required=5 tests=[AWL=-0.599, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id gQmul9zGxfXO for <pwe3@ietfa.amsl.com>; Mon, 2 Sep 2013 18:51:28 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id C63D121F91CB for <pwe3@ietf.org>; Mon, 2 Sep 2013 18:51:22 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.5-GA FastPath queued) with ESMTP id AUZ36938; Tue, 03 Sep 2013 01:51:21 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 3 Sep 2013 02:51:09 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.146.0; Tue, 3 Sep 2013 02:51:20 +0100
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.211]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.01.0323.007; Tue, 3 Sep 2013 09:51:15 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: "pwe3@ietf.org" <pwe3@ietf.org>
Thread-Topic: Poll for WG adoption of draft-shen-pwe3-endpoint-fast-protection-04
Thread-Index: AQHOpYzaFKoE4BbeI06zDH61p3nVjZmyNGJQ
Date: Tue, 03 Sep 2013 01:51:14 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7336131DB@nkgeml508-mbx.china.huawei.com>
References: <CE466A08.4F679%matthew.bocci@alcatel-lucent.com>
In-Reply-To: <CE466A08.4F679%matthew.bocci@alcatel-lucent.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.102.175]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Subject: Re: [PWE3] Poll for WG adoption of draft-shen-pwe3-endpoint-fast-protection-04
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: Tue, 03 Sep 2013 01:51:44 -0000

Hi, 

I have read the draft and have the following comments and questions. 

1. When I read the ICCP draft and RFC 6718, I thought PW-RED offered the mechanism for PE and AC protection. Is there any difference between the solution here and the PW-RED?
 
2. Whether providers need manually configure the protector?

3. There seems no detail for the proxy method to be followed by the implementers. Add a reference here or elaborate it?

4. I am glad to see there is some text talking about the " Revertive Behavior ". I was designing a protection mechanism before, knowing that this is not an easy problem to be solved. If the PLR revert to the new primary PW ahead of time (before the convergence). Loops or packet loss may happen. I remember I was asked by the question: how does the PLR determine the time to revertive? Timers are what I can think of. I wonder whether there is any better idea. 

5. A minor issue. What is "control plane repair"? See para3 of the introduction. I think both global repair and local repair involves both data plane and control plane behaviors. 

If I missed anything, please correct me.

Thanks,
Mingui


>-----Original Message-----
>From: pwe3-bounces@ietf.org [mailto:pwe3-bounces@ietf.org] On Behalf Of
>Bocci, Matthew (Matthew)
>Sent: Friday, August 30, 2013 10:26 PM
>To: pwe3@ietf.org
>Subject: [PWE3] Poll for WG adoption of
>draft-shen-pwe3-endpoint-fast-protection-04
>
>This email begins a two week poll to help the chairs determine if there is
>consensus to adopt draft-shen-pwe3-endpoint-fast-protection-04 as an PWE3
>working group draft.
>
>The draft can be found here:
>http://tools.ietf.org/id/draft-shen-pwe3-endpoint-fast-protection-04.txt
>
>Please read the draft and indicate to the list if you support adoption, or if you do
>not support adoption (giving reasons).
>
>Please note that this is only a call for adoption. There needs to be consensus
>that this draft is a good basis for the work, but it does not need to be perfect at
>this stage.
>
>The poll for adoption will close in two weeks time, on Friday 13th September.
>
>Best regards,
>
>Matthew