Re: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

["Les Ginsberg (ginsberg)" <[e-mail]>]

Chongfeng –

Just to clarify my position…

IMO there is no substantive content in this draft that warrants it becoming an RFC – Informational track or otherwise. It is simply a set of pointers to other documents/registries.

If the authors find the content in some way helpful, I think the more suitable path for you is to publish a white paper and post it on whatever web site seems appropriate to you.
I just do not see any content in the draft that warrants a standards body like IETF producing a new document.

Thanx.

   Les


From: Chongfeng Xie <[e-mail]>
Sent: Thursday, March 04, 2021 5:04 AM
To: Les Ginsberg (ginsberg) <[e-mail]>; Acee Lindem (acee) <[e-mail]>; [e-mail]
Subject: Re: Re: [Lsr]WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03


Hi， Les,

Thanks for the review of this document.

As the current document type is informational, it does not introduce new TLV to IS-IS. While it describes the mechanisms of using existing TLVs to distribute the information of SR based VTNs, which can have customized topology and a set of dedicated network resources. It also describes the forwarding behaviors based on the SIDs and the resources allocated to each VTN.

IS-IS MT as defined in RFC 5120 provides the mechanisms to build multiple logical topologies and perform independent path computation for each topology. RFC 5120 mentions that the TE attributes TLVs can be inherited by the MT TLVs “if traffic engineering or some other applications are being applied per topology level later”. While it does not specify what the topology-specific TE attributes mean, and how traffic in different topologies are forwarded on a shared outgoing interface. These are described in section 3 and section 4 of this document.

RFC8667 and draft-ietf-lsr-isis-srv6-extensions defines the encoding of SR SIDs/SRv6 Locators in IS-IS, while the usage of the topology-specific SIDs and Locators are not specified, especially when the SIDs are associated with different set of network resources.

Section 5 gives the analysis about the scalability of this mechanism, and talks about a case where two VTNs have the same logical topology, but with different set of resources.

IMO the value of this document is that it provides an option to build SR VTNs with no IS-IS protocol extensions, which could be useful for some network scenarios.

Best regards,
Chongfeng

________________________________
[e-mail]<mailto:[e-mail]>

发件人： Les Ginsberg \(ginsberg\)<mailto:ginsberg=[e-mail]>
发送时间： 2021-03-04 11:52
收件人： Acee Lindem (acee)<mailto:acee=[e-mail]>; [e-mail]<mailto:[e-mail]>
主题： Re: [Lsr]WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03
I oppose WG adoption for this draft.

I note that the authors – following significant comments received on V0 - have removed much of the material that was considered confusing and/or inappropriate – notably discussion of L2 bundle link members.
I also note the draft has moved from Standards track to Informational track.

Let’s consider what content remains (ignoring boilerplate sections):

Section 2 notes that MT TLVs (RFC 5120) can support:
   o Topology specific SR-MPLS SIDs (defined in RFC 8667)
   o Topology specific SRv6 Locators and SIDs (defined in draft-ietf-lsr-isis-srv6-extensions)

Section 3 notes that MT TLVs can also support link attribute advertisements (defined in RFC 5305 and RFC 8570)

Also note that the IANA registries:

https://www.iana.org/assignments/isis-tlv-codepoints/isis-tlv-codepoints.xhtml#isis-tlv-codepoints-22-23-25-141-222-223 and
https://www.iana.org/assignments/isis-tlv-codepoints/isis-tlv-codepoints.xhtml#isis-tlv-codepoints-135-235-236-237

also clearly document what is discussed in Sections 2 and 3.

Section 4 notes that topology specific forwarding entries can be installed in the forwarding plane based on topology specific routing calculations – something which was discussed in RFC 5120.

Section 5 notes that two different MTIDs could operate on the same physical topology - something clearly discussed in RFC 5120.

All of this adds nothing new to our understanding of the protocol. The only “new” content is the statement that VTNs could map to MTIDs.
But the substance of VTN and how it might be used is better discussed in a number of other drafts including:

   draft-ietf-spring-sr-for-enhanced-vpn
   draft-ietf-teas-enhanced-vpn
   draft-dong-lsr-sr-enhanced-vpn

The last draft is most notable because it proposes new IGP protocol encodings in support of VTN. Whether the encodings in that draft are accepted as currently defined or evolve to something different – it would be the authoritative draft on VTN IGP extensions.

The end result is that there is no meaningful content in draft-xie-lsr-isis-sr-vtn-mt. What it states is either already stated in existing RFCs or will be stated authoritatively in whatever draft-dong-lsr-sr-enhanced-vpn  evolves to (if indeed this work on VTNs is adopted by the WG).

Let’s please not waste WG time on this draft.

   Les


From: Lsr <[e-mail]<mailto:[e-mail]>> On Behalf Of Acee Lindem (acee)
Sent: Tuesday, March 02, 2021 3:28 PM
To: [e-mail]<mailto:[e-mail]>
Subject: [Lsr] WG Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03

This information draft describes how MT could be used for VTN segmentation. The authors have asked for WG adoption.

This begins a three week LSR Working Group Adoption Poll for “Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network” - draft-xie-lsr-isis-sr-vtn-mt-03. I’m giving it three weeks due to the IETF next week. Please register your support or objection on this list prior to the end of the adoption poll on 3/24/2020.

Thanks,
Acee