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

[Jeffrey Haas <[e-mail]>]

[choosing this message for the reply]

On Fri, Feb 07, 2020 at 02:50:06PM -0800, Randy Bush wrote:
> > EBGP using connected-interface address
> > EBGP using loopback address
> > ECMP
> > Validation of allowed peers
> > Liveness detection
> > Supported address family for session setup: IPv4, IPv6
> > Authentication
> > ....
> > 
> > Please share your opinions about this list.
> 
> - signal your ip address (which will tell me v4 or v6) and, as
>   it is the 21st century, assump MPBGP
> - signal your asn.  if it is the same as mine, it's iBGP so
>   no need to think about multi-hop etc
> - signal how many hops i need to get to your listener
> - signal the authentication
> 
> isn't the rest either discoverd/agreed in the OPEN or automagic?

Mostly.  Later in the thread I see the opinion about authentication got more
complicated, which I think is a necessary thing.

One of the ideas I pushed for in the lldp draft, and mentioned similarly in
the Acee IGP RR discovery drafts was the idea of a "role".  It is left
intentionally unspecified in the draft at the moment since policy/config can
help reconcile it, but perhaps as we work on the design having a more formal
definition may be helpful.

A role in a DC fabric context can be what layer of the fabric the router is
operating at.  E.g. in a 3 layer fabric, leaf should interact with
aggregate, aggregate with leaf and spine, etc.  This helps with discovery
and helps avoid misconnectivity.

A role for a standard ISP PE would be "customer", "reflector", etc.

And yes, there's likely overlap with ideas such as ASPA.

---

An interesting question about layering also covers your point above:
Discovery lets you find a thing that speaks BGP and some of the expected
properties.  Some of the things the automation proposals could do could
either live in the discovery mechanism or in the BGP speaker itself.  Role,
for example.  Transport security mechanism likely has to live in the
discovery.

-- Jeff