Subject: [Bgp-autoconf] Summarized requirements

From: "Dongjie (Jimmy)" <[email-masked]>
Date: Mon, 2 Mar 2020 16:02:56 +0000

Hi all,

First of all, thanks again to the draft authors who send the summarized requirements from their drafts. I made a list based on the collected requirements, and tried to classify them into "common requirements", "union of other functional requirements" and "requirements about design principle":

1.       Common requirements

l  Support IPv4 and IPv6 address family

l  Support using interface or loopback address for BGP session

l  Support to discover the peering IP address

l  Support to discover the peering ASN

l  Support authentication of control message

l  Enable Layer 3 link liveness detection, such as BFD

2.       Union of other functional requirements (could be considered optional)

l  Discover mutually supported encapsulation

l  Provide Layer 2 keep-alive messages for session continuity

l  Discover the role of the connected nodes

l  Automatic setup of reachability to peer's loopback over one or more connected links

l  Provide resolution for the BGP next-hop address (i.e. the loopback address) for the BGP routes exchanged over these sessions between the loopback addresses.

l  Enable exchange of IP addresses and link attributes between the directly connected BGP routers. should be extensible to include other information in future.

l  Discover neighbor's BGP ID for consistency check or avoid connection collision

l  Discovery parameters relating to the BGP peer session (e.g., the local address)

l  Mechanism should be limited to link scope for security and use link-local addressing only

l  Support optional validation of parameters to detect misconfiguration (e.g. link address subnet mismatch, peering between incorrect AS, etc.) in an extensible manner

3.       Requirements about design principle:

l  Independent from BGP session establishment

l  Widely applicable to a range of routing and similar protocols which need layer 3 discovery and characterization

l  Not affect or change BGP session establishment and routing exchange, other than the interactions for triggering the setup/removal of peer session that is based on discovery mechanism

l  Generic for any link-layer protocol

l  Make use of a currently implemented and deployed DC switch protocol to reduce the cost and complexity

l  Make use of existing BGP protocol for automating the BGP session bring-up

Firstly please check if there is any requirement I missed. Then I'd need your opinions on whether some requirement should be moved from the "other functional requirements" to the "common requirements" category, or vise versa. One example is "discover the role of the connected nodes" which seems was widely accepted on our conference call.

After the functional requirement lists are determined, we could move forward to have some further discussion about the design principle.

Thoughts?

Best regards,
Jie