Re: [Idr] Fw: WG adoption call for draft-xu-idr-neighbor-autodiscovery(Internet mail)

["UTTARO, JAMES" <[e-mail]>]

Zhichun,

                We also are heavily invested in BGP at AT&T Domestic and MOW networks.. help me understand the ask here. Are you saying that you want discovery everywhere in your network? Or is this ask specific to the DC and you will continue  with provisioning in the MAN/WAN space..


Thanks,
                Jim Uttaro

From: Idr [mailto:[e-mail]] On Behalf Of zcjiang(???)
Sent: Monday, July 23, 2018 9:35 AM
To: [e-mail]
Subject: Re: [Idr] Fw: WG adoption call for draft-xu-idr-neighbor-autodiscovery(Internet mail)

Hi , folks

I am a network architect from Tencent, one of the top 3 China's Internet giants and the largest Chinese social-network service operator, running multiple MSDCs across the world.

In our deployment of DC network, BGP is used as IGP to build the underlay of the DC fabric. Since we think BGP is better from perspective of scale and simplicity(think about the flooding of IGP in a DC fabric.....). We are also looking at the BGP based SR in DC yo achieve better traffic engineering and unified MPLS fabric across the DC/MAN and backbone.

The missing piece of BGP comparing to IGP is the neighbor auto-discovery, you still need to configure the peer address , local- remote AS etc, so the effort to add the auto neighbor discovering mechanism to BGP is highly desired.

We as an web operator and I personally as one of the contributor of the draft would like to advocate the mechanism described on this draft for sure.

Thanks

Zhichun Jiang.

------------------------------------------------------------------
From:Susan Hares <[e-mail]<mailto:[e-mail]>>
Send Time:2018年7月20日(星期五) 19:18
To:徐小虎(义先) <[e-mail]<mailto:[e-mail]>>; Idr <[e-mail]<mailto:[e-mail]>>; idr <[e-mail]<mailto:[e-mail]>>
Cc:draft-xu-idr-neighbor-autodiscovery <[e-mail]<mailto:[e-mail]>>
Subject:RE: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery

Xiaohu:

Our next step is to gather requirements for the IDR neighbor discovery from the WG.  We would especially be interested in feedback on requirements from operators of data centers.  If you know of an operators of medium data centers who could send requirements to the IDR chairs or the IDR list, it would be helpful.

Cheerily, Susan Hares

From: Idr [mailto:[e-mail]] On Behalf Of ???(??)
Sent: Friday, July 20, 2018 7:12 AM
To: Idr; idr
Cc: draft-xu-idr-neighbor-autodiscovery
Subject: Re: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery


Hi Sue,

Thanks for launching the WG adoption call for draft-xu-idr-neighbor-autodiscovery.

Hi all,

There has been one implementation developed by a switch vendor. Furthermore at least two additional implementations from other vendors are under construction. If any of you have any concrete and technical concerns on this mechanism, please feel free to tell us and we would like to verify your concerns on the implementation and then give you feedbacks.

Best regards,
Xiaohu
------------------------------------------------------------------
From:Susan Hares <[e-mail]<mailto:[e-mail]>>
Send Time:2018年7月19日(星期四) 17:59
To:idr <[e-mail]<mailto:[e-mail]>>
Cc:draft-xu-idr-neighbor-autodiscovery <[e-mail]<mailto:[e-mail]>>
Subject:Re: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery

This closes the 2 week adoption for draft-xu-idr-neighbor-autodiscovery
(July 2 – July 16).

The WG chairs conclude on my original questions that:

1)  There is WG interest to have an auto-discovery mechanism

that will work for BGP peers in Data Centers


2)  There is some WG  interest having this work

in other deployments.


3)  There is no consensus on the mechanisms

(BGP hellos or other mechanisms)

Or requirements for the mechanisms.


4)  There is WG consensus and AD Consensus that we should

collaborate with LSVR. One mechanism for both would

be good, but it needs to fit the requirements set

by the WG.

There is no consensus on adoption this draft.

During today’s IDR session (18:10-19:10), we will have a
discussion on the requirements for the auto-discovery mechanisms.
We will start by reviewing the LSVR requirement set.

If our discussions today do not come to a clear conclusion,
the chairs are willing to sponsor an interim on the topic.

Susan Hares and John Scudder.

From: Idr [mailto:[e-mail]] On Behalf Of Susan Hares
Sent: Monday, July 2, 2018 1:09 PM
To: [e-mail]<mailto:[e-mail]>
Cc: [e-mail]<mailto:[e-mail]>
Subject: [Idr] WG adoption call for draft-xu-idr-neighbor-autodiscovery

Greetings:

This begins a 2 week WG adoption call for draft-xu-idr-neighbor-autodiscovery (July 2 – July 16).

https://datatracker.ietf.org/doc/draft-xu-idr-neighbor-autodiscovery/<https://urldefense.proofpoint.com/v2/url?u=https-3A__datatracker.ietf.org_doc_draft-2Dxu-2Didr-2Dneighbor-2Dautodiscovery_&d=DwMGaQ&c=LFYZ-o9_HUMeMTSQicvjIg&r=s7ZzB4JbPv3nYuoSx5Gy8Q&m=MU6Gnn4Pl1H3kbngfFfnwWWrIF4eDWqmnSrxG03TYQ8&s=JWVZk-QAfbuLnv3IJNkfcyJDYO-4MUCpjoEGA_s7plY&e=>

The authors of this draft should send their IPR statements in response to this email.  I hope the authors will ihelp their vacationing co-authors to respond by July 7th.

The WG should consider the following:

1)      Does BGP need to have an autodiscovery mechanism for peers within Data Centers?

2)      Does this mechanism work for other deployments?


3)      If so, should be passed in BGP Hello message?

Or should it be a part of another protocol (e.g. LLDP, BFD, etc).


4)      Does this interact with any of the LSVR work?

I want to thank the authors for their patience while we sorted through some of the WG LC for other drafts.  We decided to wait until some of those discussion were cleared up prior to starting a new WG Adoption call.


Susan Hares