[trill] 答复: Shepherd's report on draft-ietf-trill-tree-selection-03

Liyizhou <liyizhou@huawei.com> Thu, 17 March 2016 23:48 UTC

Return-Path: <liyizhou@huawei.com>
X-Original-To: trill@ietfa.amsl.com
Delivered-To: trill@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1055712DDE2 for <trill@ietfa.amsl.com>; Thu, 17 Mar 2016 16:48:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.221
X-Spam-Level:
X-Spam-Status: No, score=-4.221 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 eRjPKsrM2eZO for <trill@ietfa.amsl.com>; Thu, 17 Mar 2016 16:48:39 -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 AA61012DDDE for <trill@ietf.org>; Thu, 17 Mar 2016 16:48:38 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml708-cah.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id CGH11301; Thu, 17 Mar 2016 23:48:36 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by lhreml708-cah.china.huawei.com (10.201.5.202) with Microsoft SMTP Server (TLS) id 14.3.235.1; Thu, 17 Mar 2016 23:48:33 +0000
Received: from NKGEML513-MBX.china.huawei.com ([169.254.1.56]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Fri, 18 Mar 2016 07:48:26 +0800
From: Liyizhou <liyizhou@huawei.com>
To: Susan Hares <shares@ndzh.com>, "trill@ietf.org" <trill@ietf.org>
Thread-Topic: [trill] Shepherd's report on draft-ietf-trill-tree-selection-03
Thread-Index: AdGAXkpusX+D9vmbTeCSmXSUHYHNhwASPLVA
Date: Thu, 17 Mar 2016 23:48:26 +0000
Message-ID: <D408889639FC5E4FADB4E00A3E01FA8F915385B9@nkgeml513-mbx.china.huawei.com>
References: <00f201d18072$b814e820$283eb860$@ndzh.com>
In-Reply-To: <00f201d18072$b814e820$283eb860$@ndzh.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.103.194]
Content-Type: multipart/alternative; boundary="_000_D408889639FC5E4FADB4E00A3E01FA8F915385B9nkgeml513mbxchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.56EB4254.0173, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.1.56, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 06bae78b6268c7ef690a96ad6a7c1ea4
Archived-At: <http://mailarchive.ietf.org/arch/msg/trill/43ifmlF--oC4cHQZha6HH2CzrDo>
Cc: 'Donald Eastlake' <d3e3e3@gmail.com>, "trill-chairs@tools.ietf.org" <trill-chairs@tools.ietf.org>
Subject: [trill] =?gb2312?b?tPC4tDogIFNoZXBoZXJkJ3MgcmVwb3J0IG9uIGRyYWZ0?= =?gb2312?b?LWlldGYtdHJpbGwtdHJlZS1zZWxlY3Rpb24tMDM=?=
X-BeenThere: trill@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Developing a hybrid router/bridge." <trill.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trill>, <mailto:trill-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trill/>
List-Post: <mailto:trill@ietf.org>
List-Help: <mailto:trill-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trill>, <mailto:trill-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Mar 2016 23:48:42 -0000

Hi Sue,
Yes, I will do so.

Thanks,
Yizhou

·¢¼þÈË: trill [mailto:trill-bounces@ietf.org] ´ú±í Susan Hares
·¢ËÍʱ¼ä: 2016Äê3ÔÂ18ÈÕ 1:31
ÊÕ¼þÈË: trill@ietf.org
³­ËÍ: 'Donald Eastlake'; trill-chairs@tools.ietf.org
Ö÷Ìâ: [trill] Shepherd's report on draft-ietf-trill-tree-selection-03

YIzhou, Donald and Weiquo:

Below is the shepherds report for the draft.  Would you take time this week to made these minor editorial changes before the draft deadline?

Sue

Summary:

¡¤         This document is well written, and easy to understand.

¡¤         Authors should consider the editorial comments from the shepherd

¡¤         Authors should answer the RTG-DIR comments.

Shepherd  Editorial issues:

¡¤         Abstract old:/number of trees; however there is limited capacity/

               New proposed/number of trees, but there is a limited hardware capacity/

¡¤         Section 1.1 ¨C English and spelling

¡¤         Old-1/ Every RBridge can specify the trees it will use for multi-destiantion TRILL data packets it originated in the Trees Used Identifiers (TREE-USE-IDs)/

¡¤         New-1/ Every RBridge can specify the trees it will use for multi-destination TRILL data packets it originates in the Trees Used Identifiers (TREE-USE-IDs)/

¡¤         Old-2/ Trees Used Identifiers sub-TLVs are used to build the RPF Check table that is used for reverse path forwarding check; Interested VLANs and Interested Labels sub-TLVs are used for distribution tree pruning and the multi-destination forwarding table with pruning info is built based on that./

¡¤         New-2/ (two sentences makes it clearer.  Trees Used Identifiers sub-TLVs are used to build the RPF Check table that is used for reverse path forwarding check.   Interested VLANs and Interested Labels sub-TLVs are used for distribution tree pruning and the multi-destination forwarding table with pruning info is built based on that RPF Check Table. /

¡¤         Old-3 /    Defaults are provided but it is implementation dependent how many trees to calculate,/

¡¤         New-3 /    Defaults are provided but it depends on the implementation how many trees are calculated,/

1.2 section

¡¤         P. 5 Paragraph 2  Old/For the former/ New/ For the former (one distribution tree root)/

¡¤         P 5. Paragraph 3  Old/for the latter/  New / For the latter (ECMP-Like algorithm)/

¡¤         P 7 paragraph 2 starting ¡°security concerns:

o   Old/advantage of this/ New: /advantage of this leakage of traffic/

o   (if my sentences completion is not correct fill in what ¡°this¡± means¡±
4 section

¡¤         Paragraph 2

o   Old/TREE-USE-IDs and INT-VLAN sub-TLVs are still useful for some purposes other than building multicast forwarding table, for example RPF table building, spanning tree root notification, etc./

o   New / TREE-USE-IDs and INT-VLAN sub-TLVs are still useful for some purposes other than building multicast forwarding table (E.g. example RPF table building, spanning tree root notification, etc.) /

¡¤         Paragraph 3 : Old /tree1 and tree 2 in/tree1 and tree2,/


From the RTG-DIR Review was not responded to:

Section 3.2 ¨C A list of the 4 TLVs with their name and one sentence summarizing its use would improve readability. Same applies in the following to e.g. section 3.2.1 where the paragraph before the figure is not very clear on the usage of the TLV.

Sue