Hi Les, Thanks for your comments.
Although this draft reuses existing TLVs, we found that some usage may not be fully specified in existing RFCs. Please see my recent reply to Peter about the per-topology TE attributes, and the use of MT-ID in L2 bundle. Currently my preference is standard track, while it is open for discussion with the WG. I agree this draft is relevant to draft-dong-lsr-sr-enhanced-vpn, and their relationship is described in the abstract of this document: "I-D.dong-lsr-sr-enhanced-vpn defines the IGP extensions to build a set of Segment Routing (SR) based VTNs. This document describes a simplified mechanism to build the SR based VTNs using IGP multi- topology together with other well-defined IS-IS extensions." As this draft itself describes a stand-alone solution, maybe it is more appropriate to keep it as a separate document. Bet regards, Jie -----Original Message----- From: Les Ginsberg (ginsberg) [mailto:[email protected]] Sent: Friday, March 27, 2020 12:05 AM To: Dongjie (Jimmy) <[email protected]>; Peter Psenak <[email protected]>; [email protected]; lsr <[email protected]> Subject: RE: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing based Virtual Transport Network Trying to avoid piling on...but Peter is certainly correct that there is nothing in this draft that is normative. This may provide useful context for the protocol extensions defined in https://datatracker.ietf.org/doc/draft-dong-lsr-sr-enhanced-vpn/. As such the content would be better incorporated into that draft. Whether the WG decides to take on enhanced VPN or not is still TBD, but there is no reason I can see for this draft to exist independently. Les > -----Original Message----- > From: Lsr <[email protected]> On Behalf Of Dongjie (Jimmy) > Sent: Wednesday, March 25, 2020 11:41 PM > To: Peter Psenak <[email protected]>; > [email protected]; lsr <[email protected]> > Subject: Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment Routing > based Virtual Transport Network > > Hi Peter, > > As described in the abstract, the purpose of this draft is to define a > simplified control plane mechanism to build SR based Virtual Transport > Network (VTN), it is based on the combination of IS-IS Multi-Topology > with other IS-IS extensions, e.g. the extensions for TE, SR and L2 > bundle. In a word, it tries to reuse the existing TLVs as much as possible. > > That said, this document introduces the mechanism of specifying per- > topology TE attributes, which was not covered in the existing IS-IS MT > (RFC 5120). Similarly, it also introduces the mechanism of associating > MT-IDs with a particular member link of L2 bundle, which was not > defined in IS-IS L2 Bundle (RFC 8668). > > Thus we think it is appropriate to be standard track. > > Best regards, > Jie > > > -----Original Message----- > > From: Lsr [mailto:[email protected]] On Behalf Of Peter Psenak > > Sent: Wednesday, March 25, 2020 10:09 PM > > To: [email protected]; lsr <[email protected]> > > Subject: Re: [Lsr] Using IS-IS Multi-Topology (MT) for Segment > > Routing > based > > Virtual Transport Network > > > > Hi Chongfeng, > > > > what exactly is being standardized in this draft? I don't see anything. > > > > thanks, > > Peter > > > > > > On 25/03/2020 14:44, [email protected] wrote: > > > > > > Hello, folks, > > > > > > we have submitted a new draft of > > > https://tools.ietf.org/html/draft-xie-lsr-isis-sr-vtn-mt-00 . > > > > > > It is about Using IS-IS Multi-Topology (MT) for Segment Routing > > > based Virtual Transport Network. Enhanced VPN (VPN+) as defined in > > > I-D.ietf-teas-enhanced-vpn aims to provide enhanced VPN service to > > > support some applications's needs of enhanced isolation and > > > stringent performance requirements. VPN+ requries integration > > > between the overlay VPN and the underlay network. A Virtual > > > Transport Network > > > (VTN) is a virtual network which consists of a subset of the > > > network toplogy and network resources allocated from the underlay > > > network. A VTN could be used as the underlay for one or a group of VPN+ > > > services. > > > This document describes a simplified mechanism to build the SR > > > based VTNs using IGP > > > multi- topology together with other well-defined IS-IS extensions. > > > > > > Comments and suggestions are highly appreciated. > > > > > > Chongfeng Xie > > > > > > > > > > _______________________________________________ > > Lsr mailing list > > [email protected] > > https://www.ietf.org/mailman/listinfo/lsr > _______________________________________________ > Lsr mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/lsr _______________________________________________ Lsr mailing list [email protected] https://www.ietf.org/mailman/listinfo/lsr
