Re: [PWE3] PWE3 WG last call for draft-ietf-pwe3-iccp-stp-01

Mingui Zhang <zhangmingui@huawei.com> Fri, 16 May 2014 07:40 UTC

Return-Path: <zhangmingui@huawei.com>
X-Original-To: pwe3@ietfa.amsl.com
Delivered-To: pwe3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124E11A00D4 for <pwe3@ietfa.amsl.com>; Fri, 16 May 2014 00:40:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.852
X-Spam-Level:
X-Spam-Status: No, score=-4.852 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id K9d1HzFZ9cGj for <pwe3@ietfa.amsl.com>; Fri, 16 May 2014 00:40:38 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CF8331A00C9 for <pwe3@ietf.org>; Fri, 16 May 2014 00:40:35 -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.7-GA FastPath queued) with ESMTP id BEF11726; Fri, 16 May 2014 07:40:27 +0000 (GMT)
Received: from LHREML402-HUB.china.huawei.com (10.201.5.241) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 16 May 2014 08:39:22 +0100
Received: from NKGEML401-HUB.china.huawei.com (10.98.56.32) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 16 May 2014 08:40:24 +0100
Received: from NKGEML508-MBX.china.huawei.com ([169.254.7.73]) by nkgeml401-hub.china.huawei.com ([10.98.56.32]) with mapi id 14.03.0158.001; Fri, 16 May 2014 15:40:15 +0800
From: Mingui Zhang <zhangmingui@huawei.com>
To: Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>
Thread-Topic: [PWE3] PWE3 WG last call for draft-ietf-pwe3-iccp-stp-01
Thread-Index: AQHPYDZEld3QSIBOQU+hJWPbTgqRFZs7e3wAgAKfigCAAB+eAIAETnPw///KtQCAAIteAA==
Date: Fri, 16 May 2014 07:40:14 +0000
Message-ID: <4552F0907735844E9204A62BBDD325E7336E3CF8@nkgeml508-mbx.china.huawei.com>
References: <CAA=duU2Rw=EyKV4OC9CfytCMdX9VoTP0EEk5iaoOz3O2=E1Oew@mail.gmail.com> <CAA=duU3oCX2E=ifoAkibr9m3Labgp35_-jzy_YgO8rauzEur6Q@mail.gmail.com> <CAA=duU0KSG-z3kesW--jdYYwAAqHdbXmz84ExP2egssudD=FfA@mail.gmail.com> <4e5ff4f0223e4a2296cacede2fc74c9f@AM3PR03MB612.eurprd03.prod.outlook.com>, <4552F0907735844E9204A62BBDD325E7336E3C2A@nkgeml508-mbx.china.huawei.com> <1400220467943.91281@ecitele.com>
In-Reply-To: <1400220467943.91281@ecitele.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
Archived-At: http://mailarchive.ietf.org/arch/msg/pwe3/1SKfNdRlgi3kaHv_czZQgR9ASLU
Cc: "pwe3@ietf.org" <pwe3@ietf.org>, "hujie@ctbri.com.cn" <hujie@ctbri.com.cn>
Subject: Re: [PWE3] PWE3 WG last call for draft-ietf-pwe3-iccp-stp-01
X-BeenThere: pwe3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Pseudowire Emulation 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, 16 May 2014 07:40:40 -0000

Hi Sasha,

Thanks for your feedback. We become much clear about some issues this time.

> And you did not explain what happens to customer traffic received by PE1/PE2
> from the "non-bridge" ports shown in the diagram. 
> I agree that with a suitable extension the black-holing issue would become 
> relevant - but *not with the topology that is actually depicted in the draft*.

<MINGUI> OK. I can extend the figure to make it clearer.


> [[Sasha]] I do not think that PWE3 should deal with improvements to STP. 
>This protocol (in all its flavors) is owned by IEEE 802.1, and if it requires any 
>improvements, they should be discussed there.  

<MINGUI> This document will not do any change to the STP. It's the proprietary solution that slows down the convergence of STP.


>[[Sasha]] The sentence you have mentioned does not, by and of itself, mean that all PEs run STP.

<MINGUI>If you read the following sentence on page 6, you will realize it.
"... PEs "participate" in the STP calculation..."

I can include a separate section to discuss about the theory of operation. I think this will be helpful for a "reasonably qualified engineer".

Thanks,
Mingui