<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.xu-idr-neighbor-autodiscovery" target="https://datatracker.ietf.org/doc/html/draft-xu-idr-neighbor-autodiscovery-11">
   <front>
      <title>BGP Neighbor Discovery</title>
      <author initials="X." surname="Xu" fullname="Xiaohu Xu">
         <organization>Alibaba Inc</organization>
      </author>
      <author initials="K." surname="Talaulikar" fullname="Ketan Talaulikar">
         <organization>Cisco Systems</organization>
      </author>
      <author initials="K." surname="Bi" fullname="Kunyang Bi">
         <organization>Huawei</organization>
      </author>
      <author initials="J." surname="Tantsura" fullname="Jeff Tantsura">
         <organization>Apstra</organization>
      </author>
      <author initials="N." surname="Triantafillis" fullname="Nikos Triantafillis">
         <organization>Apstra</organization>
      </author>
      <date month="April" day="16" year="2019" />
      <abstract>
	 <t>   BGP is being used as the underlay routing protocol in some large-
   scaled data centers (DCs).  Most popular design followed is to do
   hop-by-hop external BGP (EBGP) session configurations between
   neighboring routers on a per link basis.  The provisioning of BGP
   neighbors in routers across such a DC brings its own operational
   complexity.

   This document introduces a BGP neighbor discovery mechanism that
   greatly simplifies BGP operations in such DC and other networks by
   automatic setup of BGP sessions between neighbor routers using this
   mechanism.


	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-xu-idr-neighbor-autodiscovery-11" />
   
</reference>
