Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

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

Hi Robin,

Please see inline for some comments.

From: Idr <[e-mail]> On Behalf Of Lizhenbin
Sent: 06 May 2019 07:05
To: li zhenqiang <[e-mail]>; Susan Hares <[e-mail]>; [e-mail]
Cc: draft-ietf-teas-enhanced-vpn <[e-mail]>; draft-dong-lsr-sr-enhanced-vpn <[e-mail]>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

Hi Zhenqiang,
Please refer to my reply inline.

Best Regards,
Zhenbin (Robin)

From: Idr [mailto:[e-mail]] On Behalf Of li zhenqiang
Sent: Wednesday, April 24, 2019 3:51 PM
To: Susan Hares <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>
Cc: draft-ietf-teas-enhanced-vpn <[e-mail]<mailto:[e-mail]>>; draft-dong-lsr-sr-enhanced-vpn <[e-mail]<mailto:[e-mail]>>
Subject: Re: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call

Hi Sue and All,

Zhenqiang Li from China Mobile.

I see the value to allocate SIDs in a centralized way, especially for the SIDs representing network resources as proposed in https://datatracker.ietf.org/doc/draft-ietf-teas-enhanced-vpn/ and https://datatracker.ietf.org/doc/draft-dong-lsr-sr-enhanced-vpn/.

However, I want to know why BGP-LS is chosen to to complete this work, not PCEP or netconf? BGP-LS is mainly used to collect information from network, other than configure network from a controller.
[Robin]
1. To be honest, there is much concern about the standardization process, inter-operability, performance on Netconf/YANG. It is necessary to think about the other option. Just like topology collection, there existed the way to use SNMP/MIB or Netconf/YANG to collect topology info from the network, later BGP-LS was proposed.
[KT] Topology by it’s very nature is dynamic and changes due to planned and unplanned network events. That presents the case to advertise it via BGP-LS. The provisioning use-case is not quite on the same lines.

2. There is already PCE work to allocate SID in the centralized way (Refer to PCECC work proposed by https://tools.ietf.org/html/draft-ietf-teas-pcecc-use-cases-02) But there truly exists the BGP-only scenarios. It is difficult to introduce one more control protocol which may increase the complexity of network operation and maintenance. That is the reason why we introduced the BGP extension to allocate SID which also can reduce the possible complexity.
[KT] PCEP is a p2p connection oriented protocol with a very transactional aspects to it’s protocol interactions – BGP is not.

3. For the possible methods of BGP extensions for the purpose, there can be other way such as introducing a new AFI/SAFI, etc.
[KT] If at all BGP, then that would perhaps be the way to approach this use-case/functionality.

But we think the BGP-LS extension may be the easiest way. Since BGP-LS can collect info of all kinds of SIDs from the network devices to the controller, it is only to define a TLV/Sub-TLV to indicate the SID allocation from the controller to the network devices. All the existing TLV/Sub-TLV using by BGP-LS will be reused without any change.
[KT] I think this is not just about re-use of BGP-LS TLVs anymore. It is a more fundamental shift in the BGP-LS use-case. The authors of the draft need to cover all possible aspects of this interactions, failures and other scenarios to explain how BGP is going to be used for doing day 0 and day X SR provisioning.

Thanks,
Ketan

If use other ways, there has to define some new TLVs/Sub-TLVs or the transition from the corresponding BGP-LS TLV/Sub-TLVs to the new TLVs/Sub-TLVs. But the option is open. We would like to solicit comments from BGPers.




Best Regards,
Zhenqiang Li
________________________________
[e-mail]<mailto:[e-mail]>

From: Susan Hares<mailto:[e-mail]>
Date: 2019-04-18 22:04
To: [e-mail]<mailto:[e-mail]>
Subject: [Idr] draft-wu-idr-bgp-segment-allocation-ext-02.txt [4/18 - 5/2/2019] - 2 week WG adoption call
This begins a 2 week WG Adoption call for draft-wu-idr-bgp-segment-allocation-ext-02.txt.  You can access the draft at:

https://datatracker.ietf.org/doc/draft-wu-idr-bgp-segment-allocation-ext/

In your comments, consider:


1)      Does this draft mechanisms for  extending BGP-LS to provide IDs for allocation provide a beneficial addition to BGP mechanisms for segment routing?

2)      Is the mechanism well-formed enough to adopted as a WG draft?

3)      Do you see any problems with using these IDs for flow redirection?

4)      Do you support extending BGP-LS?

5)      Should we provide an early allocation for this technology?

6)      Do you know of any early implementations?

By answering these questions during WG Adoption call, you will help John and I determine what issues need to be considered prior to finalizing this WG draft.    Your answer will help us increase the speed of processing BGP-LS drafts.

If enough people indicate that they wish an early allocation upon adoption, I will then send this early allocation to Alvaro.

Sue Hares

PS – I’m trying new methods of WG adoption calls to help speed up the process in IDR WG.   Please send any thoughts on these new methods to me or John.