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

["Susan Hares" <[e-mail]>]

Zhengquiang: 

 

<wg-chair hat on> 

This is a good question to raise during the adoption of an IDR draft.   

 

I hope that the authors of the draft and others will indicate why they desire the BGP-LS method of allocating the SIDs.  As you are aware, the NETCONF based mechanism utilize a secure transport during the allocation.  BGP SHOULD run over an authenticated transport (MD5 or better yet TLS), but all BGP peers within a network may not run over the secure transport. 

<wg-chair hat off> 

 

<wg-member hat on>

As a WG member, I realize that each network makes choices on allocating SIDs and their control path.   Some of the reasons may not be able to be disclosed on a public mailing list.  However, it would be good for the authors to provide some reasons “Why BGP-LS” for allocation. 

<wg-member hat off> 

 

Sue Hares 

 

 

From: Idr [mailto:[e-mail]] On Behalf Of li zhenqiang
Sent: Wednesday, April 24, 2019 3:51 AM
To: Susan Hares; [e-mail]
Cc: draft-ietf-teas-enhanced-vpn; draft-dong-lsr-sr-enhanced-vpn
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.

 

Best Regards,

Zhenqiang Li

  _____  

[e-mail]

 

From: Susan Hares <mailto:[e-mail]> 

Date: 2019-04-18 22:04

To: [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.