[OSPF] 答复: 答复: Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02)

Xuxiaohu <xuxiaohu@huawei.com> Tue, 09 May 2017 02:56 UTC

Return-Path: <xuxiaohu@huawei.com>
X-Original-To: ospf@ietfa.amsl.com
Delivered-To: ospf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 852D1128BB6 for <ospf@ietfa.amsl.com>; Mon, 8 May 2017 19:56:48 -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 5YWC5jwO7F5f for <ospf@ietfa.amsl.com>; Mon, 8 May 2017 19:56:46 -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 8CD1B128A32 for <ospf@ietf.org>; Mon, 8 May 2017 19:56:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO LHREML712-CAH.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DGF74732; Tue, 09 May 2017 02:56:42 +0000 (GMT)
Received: from NKGEML411-HUB.china.huawei.com (10.98.56.70) by LHREML712-CAH.china.huawei.com (10.201.108.35) with Microsoft SMTP Server (TLS) id 14.3.301.0; Tue, 9 May 2017 03:56:41 +0100
Received: from NKGEML515-MBS.china.huawei.com ([169.254.5.200]) by nkgeml411-hub.china.huawei.com ([10.98.56.70]) with mapi id 14.03.0235.001; Tue, 9 May 2017 10:56:36 +0800
From: Xuxiaohu <xuxiaohu@huawei.com>
To: Greg Mirsky <gregimirsky@gmail.com>
CC: "Acee Lindem (acee)" <acee@cisco.com>, OSPF WG List <ospf@ietf.org>
Thread-Topic: =?utf-8?B?562U5aSNOiBbT1NQRl0gQWR2ZXJ0aXNpbmcgVHVubmVsaW5nIENhcGFiaWxp?= =?utf-8?B?dHkgaW4gT1NQRiAoZHJhZnQtaWV0Zi1vc3BmLWVuY2Fwc3VsYXRpb24tY2Fw?= =?utf-8?Q?-02)?=
Thread-Index: AQHSyD0PlShFaFBd2U6mYhYCCy/KAaHqc0SAgADOJRD//4bwgIAAhq/w
Date: Tue, 9 May 2017 02:56:36 +0000
Message-ID: <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C4E8@NKGEML515-MBS.china.huawei.com>
References: <FA749EE9-2DBC-4880-8ECB-A9422EE61F3E@gmail.com> <CA+RyBmUVQ5Z-1J6QrC7dd1j5gmZhKjkG1tOwkz_MNdYrixiAiw@mail.gmail.com> <1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C4A3@NKGEML515-MBS.china.huawei.com> <CA+RyBmUH6h6idjqLDzXd0C6b8aTSk7_6xBvf1nCRP_udvEtDmw@mail.gmail.com>
In-Reply-To: <CA+RyBmUH6h6idjqLDzXd0C6b8aTSk7_6xBvf1nCRP_udvEtDmw@mail.gmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.184.181]
Content-Type: multipart/alternative; boundary="_000_1FEE3F8F5CCDE64C9A8E8F4AD27C19EE2BB9C4E8NKGEML515MBSchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.59112FEB.0122, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.5.200, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32
X-Mirapoint-Loop-Id: 5c3867dc8e2aba536a33ca3780b453a4
Archived-At: <https://mailarchive.ietf.org/arch/msg/ospf/9IC7qbnpHsixIt2CNtDSGzBJ_V4>
Subject: [OSPF] =?utf-8?b?562U5aSNOiDnrZTlpI06ICBBZHZlcnRpc2luZyBUdW5uZWxp?= =?utf-8?q?ng_Capability_in_OSPF_=28draft-ietf-ospf-encapsulation-cap-02?= =?utf-8?q?=29?=
X-BeenThere: ospf@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: The Official IETF OSPG WG Mailing List <ospf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ospf>, <mailto:ospf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ospf/>
List-Post: <mailto:ospf@ietf.org>
List-Help: <mailto:ospf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ospf>, <mailto:ospf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 May 2017 02:56:48 -0000

OK, I will replace “SHOULD ” with “MUST”. Thanks again Greg.

Best regards,
Xiaohu

发件人: Greg Mirsky [mailto:gregimirsky@gmail.com]
发送时间: 2017年5月9日 10:54
收件人: Xuxiaohu
抄送: Acee Lindem (acee); OSPF WG List
主题: Re: 答复: [OSPF] Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02)

Hi Xiaohu,
thank you for your most expedient response and kind consideration of my comments.
I've just noticed typo in my own proposal s/There my/There may/.
And just one more question, why you propose to use SHOULD in "... the first occurrence SHOULD be processed ..." Would MUST be more appropriate here? Or you envision that in some circumstances this policy may be changed?

Regards,
Greg

On Mon, May 8, 2017 at 7:19 PM, Xuxiaohu <xuxiaohu@huawei.com<mailto:xuxiaohu@huawei.com>> wrote:
Hi Greg,

Thanks for your support and your comments. Please see my response inline.

发件人: OSPF [mailto:ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>] 代表 Greg Mirsky
发送时间: 2017年5月9日 5:49
收件人: Acee Lindem (acee)
抄送: OSPF WG List
主题: Re: [OSPF] Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02)

Dear All,
yes/support (readability needs some work)

Couple nits:

  *   Introduction.

     *   Perhaps "Some networks use tunnels for a variety of reasons, such as:" may be re-worded as "There my be number of reasons why different types of tunneling technique has been used in networks, among these are:"
[Xiaohu] Will update it.

     *   "The ingress needs to select a type of tunnel which is supported by the egress." I think that the idea is to find match between set of tunnels supported by the ingress and the egress.
[Xiaohu] Yes. Will add more words to clarify it.

  *   Section 3

     *   s/Routers advertises/Routers advertise/
     *   It is stated that "The Encapsulation Capability TLV SHOULD NOT appear more than once within a given OSPF Router Information (RI) Opaque LSA." What happens when it does appear more than once? Discard LSA? TLV?

[Xiaohu] Thanks for pointing out this. How about adding the following text for clarification “If the Encapsulation Capability TLV appears more than once in an OSPF Router Information LSA, only the first occurrence SHOULD be processed and others MUST be ignored.”
Best regards,
Xiaohu
Regards,
Greg



From: OSPF <ospf-bounces@ietf.org<mailto:ospf-bounces@ietf.org>> on behalf of "Acee Lindem (acee)" <acee@cisco.com<mailto:acee@cisco.com>>
Date: Thursday, April 27, 2017 at 07:45
To: "ospf@ietf.org<mailto:ospf@ietf.org>" <ospf@ietf.org<mailto:ospf@ietf.org>>
Subject: [OSPF] Advertising Tunneling Capability in OSPF (draft-ietf-ospf-encapsulation-cap-02)

This begins the WG last call for the subject draft. Please send your  support and/or
comments to this list prior to 12:00 AM GMT, May 12th, 2017.

For your convenience, here is the URL for the subject document.

https://www.ietf.org/id/draft-ietf-ospf-encapsulation-cap-02.txt

Thanks,
Acee

_______________________________________________ OSPF mailing list OSPF@ietf.org<mailto:OSPF@ietf.org> https://www.ietf.org/mailman/listinfo/ospf

_______________________________________________
OSPF mailing list
OSPF@ietf.org<mailto:OSPF@ietf.org>
https://www.ietf.org/mailman/listinfo/ospf