Re: [Idr] draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption: 12/18/2021 to 1/7/2022

[Gyan Mishra <[e-mail]>]

Hi Sue / All

I support WG Adoption of this draft.

TEAS WG has had extensive discussions on how to best identify the underlay
underpinning of overlay VPN to instantiate NSC network slice and has now
changed the naming convention to NRP “Network Resource Partition”.   Jie
and authors are now planning to change all references to VTN and VTN-ID to
NRP and NRP-ID to maintain consistency with TEAS Network slicing document
below.

https://datatracker.ietf.org/doc/html/draft-ietf-teas-ietf-network-slices-05

In this draft the concept of VTN-ID is irrelevant.

While reviewing the document consider the following questions:

1)  Does this informational draft aid operation of 5G networks for new
applications?



New 5G services require stringent  performance requirements for
applications.  This information draft describes how to use existing segment
routing (SR) mechanisms to allow a centralized control to allocate a set of
 virtual transport networks (VTNs) which are resource aware.  Isolation
between resources for multi-AS transport may be necessary to protect the
application.

 Gyan> Yes.  This document describes a mechanism to distribute the VTN or
NRP (Network Resource Partitions) logical underlay represented by ISIS MTID
topology partition that maps to VPN+ Enhanced VPN overlay network slice for
5G services instantiatio*n.*




*This draft being adopted maps ISIS MT draft below to TEAS network slice
via centralized
controller https://datatracker.ietf.org/doc/html/draft-xie-lsr-isis-sr-vtn-mt
<https://datatracker.ietf.org/doc/html/draft-xie-lsr-isis-sr-vtn-mt>*

Intra-domain:

a) Uses MT-ID which identifies 1 or more ISIS/OSPF topologies.

MTID “multi topology ID” RFC 5120 is only relevant to ISIS not OSPF.  Both
OSPFv3 and ISIS have the concept of instances and multi instance ISIS MI
RFC 6822 and OSPF address families RFC 5838 respectively.  MT is separate
control plane and common data plane where Multi Instance is separate
control plane and data plane.  So the intent of the authors I believe is
mapping of ISIS MT and OSPF multi instance concepts to a network slice.

drafts referenced:  draft-ietf-idr-rfc7752bis,
draft-ietf-idr-bgp-ls-segment-routing-ext,  draft-ietf-idr-bgpls-srv6-ext]


Intra domain topology advertisement of MT-ID TLV in BGP LS attribute

BGP-LS extension for SR is now RFC 9085 ( intra-as)

BGP-LS extension for inter-as SR egress peering is now RFC 9086 (inter-as)

b) New VTN-ID which specifies resources associated with each VTN

[draft referenced: draft-ietf-lsr-isis-sr-vtn-mt]

 This draft distributes to centralized controller using BGP-LS networks
graph of logical underlay MTID control plane sub layer for Network Slice
Controller (NSC) instantiation of a 5G networks slice

Inter-Domain mechanisms used include:

a) Isolation of certain VTNs to specific inter-domain links or BGP peers,

Yes using MT-ID advertisement


Inter domain topology advertisement of MT-ID TLV in BGP LS attribute for
E2E network slice instantiation


b) consistent use of MT-ID across multiple domains or use of VTN-ID TLV

 Only ISIS MTID or OSPF instance control plane network graph for
instantiation of 5G network slice.  In this draft VTN ID is not relevant.

VTN-ID TLV is a bgp-ls TLV that specifies unique set of resources per VTN.
Again, VTN-ID is not relevant.

[existing WG drafts referenced: draft-ietf-idr-bgpls-segment-routing-epe,
draft-ietf-idr-bgpls-srv6-ext, draft-ietf-idr-rfc7752bis]

New drafts referenced: draft-dong-idr-bgpls-sr-enhanced-vpn-03.txt]



2) Should IDR recommend the global VTN-ID?

 Again VTN-ID is not relevant here only MT-ID mapping to TEAS 5G Network
slice

The MT-ID is not an IANA registered named space.  VTN-ID is proposed as a
global name space, but does not have any proposed IANA registry text.
Should VTN-ID become a register global name space that identifies a set of
MT-IDs and other resources?
No as VTN-ID is not relevant here. Only ISIS MT-ID or OSPF instance is
relevant to map to 5G network slice.

Kind Regards

Gyan

On Sat, Dec 18, 2021 at 11:33 AM Susan Hares <[e-mail]> wrote:

> This begins a WG Adoption call for draft-xie-idr-bgpls-sr-vtn-mt-03.txt
> from 12/18 2021 to 1/7/2022.  The longer period is due to the Holiday/New
> Year time period.
>
>
>
> The draft can be found at:
>
> https://datatracker.ietf.org/doc/draft-xie-idr-bgpls-sr-vtn-mt/
>
>
>
> While reviewing the document consider the following questions:
>
>
>
> 1)  Does this informational draft aid operation of 5G networks for new
> applications?
>
>
>
> New 5G services require stringent  performance requirements for
> applications.  This information draft describes how to use existing segment
> routing (SR)
>
> mechanisms to allow a centralized control to allocate a set of  virtual
> transport networks (VTNs) which are resource aware.  Isolation between
> resources for multi-AS transport may be necessary to protect the
> application.
>
>
>
> Intra-domain:
>
> a) Uses MT-ID which identifies 1 or more ISIS/OSPF topologies.
>
> [drafts referenced:  draft-ietf-idr-rfc7752bis,
> draft-ietf-idr-bgp-ls-segment-routing-ext,  draft-ietf-idr-bgpls-srv6-ext]
>
> b) New VTN-ID which specifies resources associated with each VTN
>
> [draft referenced: draft-ietf-lsr-isis-sr-vtn-mt]
>
>
>
> Inter-Domain mechanisms used include:
>
> a) Isolation of certain VTNs to specific inter-domain links or BGP peers,
>
> b) consistent use of MT-ID across multiple domains or use of VTN-ID TLV
>
>
>
> VTN-ID TLV is a bgp-ls TLV that specifies unique set of resources per
> VTN.
>
>
>
> [existing WG drafts referenced: draft-ietf-idr-bgpls-segment-routing-epe,
> draft-ietf-idr-bgpls-srv6-ext, draft-ietf-idr-rfc7752bis]
>
> New drafts referenced: draft-dong-idr-bgpls-sr-enhanced-vpn-03.txt]
>
>
>
> 2) Should IDR recommend the global VTN-ID?
>
>
>
> The MT-ID is not an IANA registered named space.  VTN-ID is proposed as a
> global name space, but does not have any proposed IANA registry text.
> Should VTN-ID become a register global name space that identifies a set of
> MT-IDs and other resources?
>
>
>
> Cheers, Sue
>
>
> _______________________________________________
> Idr mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/idr
>
-- 

<http://www.verizon.com/>

*Gyan Mishra*

*Network Solutions A**rchitect *

*Email [e-mail] <[e-mail]>*



*M 301 502-1347*