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

[qinfengwei <[e-mail]>]

Hi all,

 

I support the adoption of this document. It describes a useful mechanism for
distributing the information of virtual underlay networks to the network
controller. 

 

And here are my answers to the questions:

 

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

 

Yes.

 

2) Should IDR recommend the global VTN-ID? 

 

This document proposes to reuse MT-IDs, thus it does not rely on global
VTN-ID. The global ID based mechanism may be helpful in some other cases,
and the discussion can happen in TEAS WG first. 

 

 

 

 

Thanks & BR,

 

Fengwei Qin

 

 

发件人: Idr [mailto:[e-mail]] 代表 Susan Hares
发送时间: 2021年12月19日 00:33
收件人: [e-mail]
主题: [Idr] draft-xie-idr-bgpls-sr-vtn-mt-03.txt - Call for WG adoption:
12/18/2021 to 1/7/2022

 

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