[Bgp-autoconf] Issues not mentioned in yesterday's revision

[Susan Hares <[e-mail]>]

Jeff and Warren: 

 

Thank you for the first draft.  

 

Here's a list of requirements that I do not see mentioned: 

 

1.  security requirements -  

 

Is it a requirement to secure data sent in a L3 multicast BGP
auto-configuration packet?

Is there a requirement that people could send a secure portion of the packet
if they desired? 

 

It all gets down to trust vs. complexity

 

2.  validation of Data sent 

 

Will the bgp-autoconf  check syntax of data sent? 

Will it validate the content of the data set? 

 

3.  Will it carry link level information? 

If so, what security issues will that cause. 

If you trust everyone, what about errors in the fabric. 

 

4.  Will it have a link to BFD? 

 

5.  What requirements are there on top of the IP Multicast - 

 Is the IP multicast a "spray and pray" multicast without   or is it "blast
and echo check"?

 

Mechanisms that I personally hoped would work: 

a) layer 3 multicast with "blast and echo" with ability to go through 2+
switches on way to remote end

b) optional securing of the data sent on BGP auto-configuration  

c) Fast failure - via BFD or some "x" mechanism 

d) optional bootstrap from IGPs or LLDP

Mechanism that I personally hoped a BGP-5 might revise its FSM. 

 

Sue