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

["Ketan Talaulikar (ketant)" <[e-mail]>]

Hi Aijun,

Regarding your point (1), I would suggest that you read https://tools.ietf.org/html/rfc7794 - the very introduction mentions the SR use-case.

That should make it crystal clear of the applicability of Source Router-ID and Prefix Attribute Flag TLVs in Segment Routing.

Thanks,
Ketan

From: Aijun Wang <[e-mail]>
Sent: 12 April 2018 08:50
To: Acee Lindem (acee) <[e-mail]>; Ketan Talaulikar (ketant) <[e-mail]>
Cc: 'idr wg' <[e-mail]>; 'Susan Hares' <[e-mail]>
Subject: 答复: [Idr] 答复: WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

Hi, Acee:

I prefer to strip the ambiguous definition of “2.3.3.  Source Router Identifier (Source Router-ID) TLV” from the current draft. The reasons are the followings:

1)      It has no relation to the SR technology.

2)      The main use case for this TLV that defined in RFC7794 is for the IS-IS redistribute between different levels

3)      There is no semantic description for the OSPF protocol(although it say ” The Source Router-ID TLV may be used to carry the OSPF Router-ID of the prefix originator.”)

4)      As you have pointed out, the “local node descriptors” associated with “prefix descriptors” can be used to identify the IGP router advertising the prefix, is this overlap with the “2.3.3.  Source Router Identifier (Source Router-ID) TLV” definition(as the LC document states: “The Source Router-ID TLV contains the IPv4 or IPv6 Router-ID of the  originator of the Prefix.  For IS-IS protocol this is as defined in  [RFC7794].  The Source Router-ID TLV may be used to carry the OSPF  Router-ID of the prefix originator.”)?

For inter-as scenarios, the process to get the inter-as topology is similar no matter whether there is BGP between those ASes or not, although normally the BGP will run between different AS.


Best Regards.

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

发件人: Acee Lindem (acee) [mailto:[e-mail]]
发送时间: 2018年4月11日 20:04
收件人: Aijun Wang; Ketan Talaulikar (ketant)
抄送: idr wg; Susan Hares
主题: Re: [Idr] 答复: WG LC for draft-ietf-idr-bgp-ls-segment-routing-ext-04 (March 7 to March 21)

Hi Aijun, Sue,

As you fully know, I don’t agree that you need to even use the Source Router-ID TLV for your use case as the Local Node Descriptors identify the IGP router advertising the prefix in the IGP domain. Furthermore, your use case is somewhat limited to the topology in figure 1 of your draft where you have a controller with visibility of multiple ASes but there is no BGP between those ASes.

Thanks,
Acee

From: Idr <[e-mail]<mailto:[e-mail]>> on behalf of Aijun Wang <[e-mail]<mailto:[e-mail]>>
Date: Wednesday, April 11, 2018 at 7:35 AM
To: "Ketan Talaulikar (ketant)" <[e-mail]<mailto:[e-mail]>>
Cc: IDR List <[e-mail]<mailto:[e-mail]>>, Susan Hares <[e-mail]<mailto:[e-mail]>>
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) <[e-mail]<mailto:[e-mail]>> 写道：
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 <[e-mail]<mailto:[e-mail]>> On Behalf Of Aijun Wang
Sent: 11 April 2018 08:50
To: 'Susan Hares' <[e-mail]<mailto:[e-mail]>>; 'idr wg' <[e-mail]<mailto:[e-mail]>>
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:[e-mail]]
发送时间: 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