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

[Robert Raszuk <[e-mail]>]

Hi Randy & Dongjie,

Before we dive into bits and pieces is the assumption that auto
discovered stuff is ephemeral and disappears upon reboot or is to stay for
a while in the box ?

How about marking peers as upstream vs downstream? See we may wan to apply
different peer templates up vs down say different prefix limits as example
- example to compute vs spine from a given TOR.

>  - signal your ip address (which will tell me v4 or v6) and, as
>   it is the 21st century, assump MPBGP

Do you want to try all possible AFI/SAFIs in capabilities ?

> - signal your asn.  if it is the same as mine, it's iBGP so
>   no need to think about multi-hop etc

if it is not the same then you guess if this is multihop, disable
connected-check or p2p ?

> - signal how many hops i need to get to your listener

How would I ever know that apriori ? BTSH in autodiscovery case is a little
bit tricky :).

> - signal the authentication

You mean type ? Well I would put those into pre-cfg template instead.

> EBGP using connected-interface address
> > EBGP using loopback address
> > ECMP
>

ECMP is not property of the session. It is internal thing to given end. I
don't think we need to autodiscover it.


> > Validation of allowed peers
>

Sure but again this is local policy.


> > Liveness detection
>

You mean BFD on/off + BFD flavor ? Or something else ?


> > Supported address family for session setup: IPv4, IPv6
>

+1


> > Authentication
>

as commented above

Thx,
r.

PS. I really do not know how far we want to go here but there is few things
which ORF can help us with too.