Re: [Bgp-autoconf] Discussion about BGP autoconf requirements in DC

[Randy Bush <[e-mail]>]

mornin' robert

> So as proven in working implementations (see Cumulus) bare min you
> need to automagically operate is a peer's address. They take it from
> link local and are done. SAFI is always 1. AFI depends on the IP as
> you suggested. eBGP AS is learned from OPEN.
> 
> So their basic interface level bgp cfg is this:
> 
> - add bgp autonomous-system 65000
>    - add bgp neighbor swp51 interface remote-as external
>    - add bgp neighbor swp52 interface remote-as external
> 
> Anything else seems topping on the cake.
> 
> There is also an interesting case Cumulus did for unnumbered loopback
> peering ... well it is actually IPv4 loopback to lPv4 loopback but
> using IPv6 link local as next hops. Works on p2p breaks few hops away.

being a simple guy, i like simple!

> I am not stating that we should or should not but do we have full
> agreement that DC case must cover any other BGP peering except p2p and
> lo2lo over p2p ? Is there a real requirement to discover your peers
> few IP hops away ?

how do we socialize this question?  maybe we, as the dt, put out a short
goals statement on idr and see if it flies?

> As far as md5, A0, XYZ to validate if you are legitimate peer this
> really is not an autodiscovery part. IMO it should be part of
> preconfigured template.

having a bit of infosec blood, i am a bit more concerned.  but you are
right, it's tough; either a leap of faith or a bleedin' infrastructure;
see draft-ymbk-lsvr-l3dl-signing.

randy