Re: [Idr] 答复: WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

"Ketan Talaulikar (ketant)" <ketant@cisco.com> Wed, 11 April 2018 11:59 UTC

Return-Path: <ketant@cisco.com>
X-Original-To: idr@ietfa.amsl.com
Delivered-To: idr@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE4CE124207 for <idr@ietfa.amsl.com>; Wed, 11 Apr 2018 04:59:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.51
X-Spam-Level:
X-Spam-Status: No, score=-14.51 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 r1zZtxblegcb for <idr@ietfa.amsl.com>; Wed, 11 Apr 2018 04:59:42 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 59FC4120724 for <idr@ietf.org>; Wed, 11 Apr 2018 04:59:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=48498; q=dns/txt; s=iport; t=1523447982; x=1524657582; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=wDwqrf8ImSj1HJqPsw23GaFq5XIWpTV9FWMUubLyFAo=; b=LRJdr13QvzvGE+cnI4c98WHKjLX8n8DERXQSj47nmiqWT95T9QZ/R3o+ pxbTUX1o12kpnsmSGuucoGE5UJzG3HOE45p5NDw0RlHfPLzptvggT6yOn nBnMg1ZBZ9xpsPhlSycyQo5zJ9CDwj9NzFSEazRHX14b11hp41v0VdHQ3 8=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0DNAAD1981a/5hdJa1cGQEBAQEBAQE?= =?us-ascii?q?BAQEBAQcBAQEBAYJNRgQrYW8oCoNYiAGNEoF0dRqKXYgEFIFmCyWEXgIagjY?= =?us-ascii?q?hNBgBAgEBAQEBAQJsHAyFIgEBAQEDIwpHBRACAQYCEQQBASEBBgMCAgIwFAY?= =?us-ascii?q?DCAIEDgUIhCFkDwOLDpoggSCBS1GIS4IaBYdugVQ/gQsBglA0gUGBUAEBAgE?= =?us-ascii?q?BFoEFCgELBAICAUQQgkqCVAKHFIRuC4RRhn4IAoVUglCDe4IOgTuDWoYngRC?= =?us-ascii?q?BaYVBgXaGSAIREwGBJAEcOGFxcBWCfYIdAxcRGVABCIdWhT5vinICJIEIgRc?= =?us-ascii?q?BAQ?=
X-IronPort-AV: E=Sophos; i="5.48,436,1517875200"; d="scan'208,217"; a="97279208"
Received: from rcdn-core-1.cisco.com ([173.37.93.152]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Apr 2018 11:59:41 +0000
Received: from XCH-RCD-010.cisco.com (xch-rcd-010.cisco.com [173.37.102.20]) by rcdn-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id w3BBxffs006731 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Wed, 11 Apr 2018 11:59:41 GMT
Received: from xch-aln-008.cisco.com (173.36.7.18) by XCH-RCD-010.cisco.com (173.37.102.20) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 11 Apr 2018 06:59:40 -0500
Received: from xch-aln-008.cisco.com ([173.36.7.18]) by XCH-ALN-008.cisco.com ([173.36.7.18]) with mapi id 15.00.1320.000; Wed, 11 Apr 2018 06:59:40 -0500
From: "Ketan Talaulikar (ketant)" <ketant@cisco.com>
To: Aijun Wang <wangaijun@tsinghua.org.cn>
CC: Susan Hares <shares@ndzh.com>, idr wg <idr@ietf.org>
Thread-Topic: =?utf-8?B?W0lkcl0g562U5aSNOiAgV0cgTEMgZm9yIGRyYWZ0LWlldGYtaWRyLWJncC1s?= =?utf-8?Q?s-segment-routing-ext-04_(March_7_to_March_21)?=
Thread-Index: AQHT0UQR7hV61FNvMEOM6SQc0BTamKP7RfNggAB9QYD//7AEMA==
Date: Wed, 11 Apr 2018 11:59:40 +0000
Message-ID: <d338bac6f74d49d197dca5fa0f1a279a@XCH-ALN-008.cisco.com>
References: <011201d3b633$0b5fee60$221fcb20$@ndzh.com> <005901d3d144$02ea09b0$08be1d10$@org.cn> <2ac4f73831924749aa53edcd1adb52be@XCH-ALN-008.cisco.com> <50FE988A-A9DD-435A-BC25-F1729768747E@tsinghua.org.cn>
In-Reply-To: <50FE988A-A9DD-435A-BC25-F1729768747E@tsinghua.org.cn>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.65.72.140]
Content-Type: multipart/alternative; boundary="_000_d338bac6f74d49d197dca5fa0f1a279aXCHALN008ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/idr/XnhxO98dlygJWmYYpfZpuad2ZCE>
Subject: Re: [Idr] =?utf-8?b?562U5aSNOiAgV0cgTEMgZm9yIGRyYWZ0LWlldGYtaWRyLWJn?= =?utf-8?q?p-ls-segment-routing-ext-04_=28March_7_to_March_21=29?=
X-BeenThere: idr@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Inter-Domain Routing <idr.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idr>, <mailto:idr-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idr/>
List-Post: <mailto:idr@ietf.org>
List-Help: <mailto:idr-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idr>, <mailto:idr-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 11 Apr 2018 11:59:45 -0000

Hi Aijun,

Many thanks for your review comments and helping their closure.

I do not agree, however, with your point about the Source Router-ID TLV. This draft does allow the TLV to be also used for OSPF. It is definitely not specific to Inter-AS situation – it is quite pervasive with multiple use-cases including SR use-cases (allows determination of the originator node for the SR Prefix SID in inter-level leaking with ISIS).

It does not make any sense to me to take this TLV (that is implemented and deployed) out of this draft which is close to being sent to IESG in order to put it in the Inter-AS draft which is an individual draft and has many questions raised about it in the WG. Such instabilities and uncertainties do affect implementation and deployment.

In any case, I will leave it to the WG and chairs as well to respond to your proposal.

I’ve posted the 06 version of the draft with all your other comments addressed.

Thanks,
Ketan


The IETF datatracker status page for this draft is:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext/



There are also htmlized versions available at:

https://tools.ietf.org/html/draft-ietf-idr-bgp-ls-segment-routing-ext-06

https://datatracker.ietf.org/doc/html/draft-ietf-idr-bgp-ls-segment-routing-ext-06



A diff from the previous version is available at:

https://www.ietf.org/rfcdiff?url2=draft-ietf-idr-bgp-ls-segment-routing-ext-06



From: Aijun Wang <wangaijun@tsinghua.org.cn>
Sent: 11 April 2018 17:04
To: Ketan Talaulikar (ketant) <ketant@cisco.com>
Cc: Susan Hares <shares@ndzh.com>om>; idr wg <idr@ietf.org>
Subject: Re: [Idr] 答复: WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

Hi, Ketan:
I think the revised version is more clear.

Regarding the Source Router Identifier (Source Router-ID) TLV”, I think stripped it from the current draft did not influence the implementation on the device. We just reorganize the reference for this TLV, put it into the most suitable document for BGP-LS extension.
This TLV is more relevant to the Inter-AS situation and should be extended to cover all IGP scenarios, not just for ISIS in current document.
If possible, I can invite the author of this draft to be the co-authors of the BGP-LS inter-as extension draft.

Except this point, I fully agree with you the updates.



在 2018年4月11日,17:59,Ketan Talaulikar (ketant) <ketant@cisco.com<mailto:ketant@cisco.com>> 写道:
Hi Aijun,

Please check inline below in your email for responses. Do let me know if this addresses your comments and I will post the updates accordingly.

Thanks,
Ketan

From: Idr <idr-bounces@ietf.org<mailto:idr-bounces@ietf.org>> On Behalf Of Aijun Wang
Sent: 11 April 2018 08:50
To: 'Susan Hares' <shares@ndzh.com<mailto:shares@ndzh.com>>; 'idr wg' <idr@ietf.org<mailto:idr@ietf.org>>
Subject: [Idr] 答复: WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

Hi, Susan and Authors of this draft:

Sorry to reply this LC so late.  The followings are my suggestions to this draft based on the discussion related to the mail thread https://mailarchive.ietf.org/arch/msg/idr/vSeflAMCMPL25N4nBOZu8yG19HA
Is it too late to response?  Please see the reply below in line.

Best Regards.

Aijun Wang
Network R&D and Operation Support Department
China Telecom Corporation Limited Beijing Research Institute,Beijing, China.

发件人: Susan Hares [mailto:shares@ndzh.com]
发送时间: 2018年3月8日 0:41
收件人: 'idr wg'
主题: [Idr] WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

This begins a 2 week WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04.txt from March 7th to March 21.  During your discussion in the WG LC, please indicate the following things:


1)     Do you think BGP should carry these link state information regarding segment routing,
“Source Router Identifier (Source Router-ID) TLV” should be stripped off this draft, because there are other situations(more general scenarios besides SR) that requires the source router of the prefixes, as described in https://datatracker.ietf.org/doc/draft-wang-idr-bgpls-inter-as-topology-ext/ and discussed in mail thread https://mailarchive.ietf.org/arch/msg/idr/-T7U1yg8DmSdDmtyfqBgtnkO4I0
[KT] You are right that Source Router-ID TLV is not SR specific. SR was one of the key use-cases where this was felt this was necessary especially in ISIS (see rfc7794). The authors of the BGP-LS SR draft felt it was necessary to introduce and cover it as part of this draft given the use-cases. It has been part of this draft since many years and even before it was adopted by the WG. It has implementations and deployments. I would say you are too late in bringing forward such a comment at this stage. With regards to the inter-AS draft, you have seen the responses on the WG mailer as well as at London and I do not have anything further to add.

2)     Are there any technical issues with this draft?

Some clarifications should be added in the following sections:
a) Regarding the usage of SID/Label sub-TLV:
“2.1.2 SR-Capabilities TLV”, “2.1.4 SR Local Block TLV” requires all the presence of “SID/Label sub-TLV”.  It is more clear to indicate  this “SID/Label sub-TLV” represent the base of the “Range Size”.
[KT] How about instead of “SID/Label sub-TLV (as defined in Section 2.1.1).” we change it to “SID/Label sub-TLV (as defined in Section 2.1.1) which encodes the first label in the range.”? Would this help clarify?

b) Regarding the inconsistence definition among “ISIS/OSPF/OSPFv3/BGP-LS” :
    “2.2.1 Adjacency SID”, “2.2.2 LAN Adjacency SID TLV”,”2.3.1 Prefix-SID TLV”
Note for “Length” field:   2-bytes “Reserved” filed should be added when copying the corresponding fields from IS-IS protocol
[KT] Now about for Length, we say for Adj-SID & Prefix-SID – “Variable, 7 or 8 depending on Label or Index encoding of the SID” and for LAN-Adj-SID we say “Variable. For ISIS it would be 13 or 14 depending on Label or Index encoding of the SID. For OSPF it would be 11 or 12 depending on Label or Index encoding of the SID.”

                c) Regarding the definition “Range TLV”:
                    if the “Length” filed is 4, how to detect the existence of “sub-TLV?”
[KT] You are right. The length should be variable since we have sub-TLVs and also the Prefix SID sub-TLV SHOULD be present to indicate the first label of the Range. I will correct this.

                    Is it more clear to rename the “Range TLV” as “Mapping-Range TLV”, so as to distinguish it from the previous “Range filed” in  “2.1.2 SR-Capabilities TLV”?
[KT] I am not sure if we should make this name change at this stage. I don’t see the confusion between the two TLVs. However, if there is WG consensus to make this change then I would do so.

                d) Regarding  the contents for “3. Procedures”:
                   Suggest to delete this section, because:
-------Contents in section 3.1, 3.2 has been mentioned in corresponding TLV definition(section 2.3.1), there is no more new information in this section.
[KT] OK will do.

-------Contents in  section 3.3 and 3.4 should be merged with section 2.3.4 to eliminate the inconsistence arose in future when update parts of them.
[KT] Sure, I will update it in that way too since it will be all info in one place for the reader.


3)     Is this draft is ready for publication?
If the above issued is solved, it is ready for publication.

For your quick access to this draft, click on the link below:

https://datatracker.ietf.org/doc/draft-ietf-idr-bgp-ls-segment-routing-ext/


Susan Hares