IDR is in the process of adopting BGP auto-configuration drafts.
We will adopt 1-4 of the BGP-auto-configuration proposals
that support BGP auto-configuration for data centers.

Please consider sending your comments to the IDR list.
The mail thread is at:

https://mailarchive.ietf.org/arch/msg/idr/ZuPiqp4YzZ3LVrfQPmAIsut6s9A/

Thank you,
Sue , Jeff, and Keyur
(IDR chairs)

=======================================================


IDR Working Group,



BGP auto-configuration has four proposals for consideration for adoption by

the IDR Working Group:



- draft-acee-idr-lldp-peer-discovery

https://datatracker.ietf.org/doc/draft-acee-idr-lldp-peer-discovery/



- draft-ietf-lsvr-l3dl + draft-ietf-lsvr-l3dl-ulpc

https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl/

https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl-ulpc/

https://datatracker.ietf.org/doc/draft-ietf-lsvr-l3dl-signing/



- draft-minto-idr-bgp-auto-discovery

https://datatracker.ietf.org/doc/draft-minto-idr-bgp-autodiscovery/



- draft-ymbk-idr-l3dn + draft-ymbk-idr-l3dn-ulpc

https://datatracker.ietf.org/doc/draft-ymbk-idr-l3nd/

https://datatracker.ietf.org/doc/draft-ymbk-idr-l3nd-ulpc/





These proposals address the core issue of BGP auto-configuration in

different ways:

- What security model should we require?

- What OSI layer? (Layer 2, Layer 3)

- Does it provide a session layer?



A brief summary of these properties for each proposal under consideration

for adoption:



draft-acee-idr-lldp-peer-discovery:

- Operates at Layer 2 as an extension to the LLDP protocol.

- Security optional, provided by MACSEC.

- Does not provide (or require) a session layer.



draft-ietf-lsvr-l3dl + draft-ietf-lsvr-l3dl-ulpc:

- Operates at Layer 2.

- Security varies from optional to certificate based.

- Provides its own session layer as part of the protocol.



draft-minto-idr-bgp-auto-discovery

- Operates at Layer 3 link-local multicast.

- Shared key authentication.

- Does not provide (or require) a session layer.



draft-ymbk-idr-l3dn + draft-ymbk-idr-l3dn-ulpc

- Operates at Layer 3 with a link-local multicast component, and a unicast

 component.

- Security varies from optional to using certificate based with TLS.

- Uses TCP for session layer for its unicast component.



What protocol or protocols should be adopted by the Working Group for

BGP auto-configuration?



-----

FYI - Jeff Tantsura will be judging the consensus for this adoption call.


_______________________________________________
rtgwg mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/rtgwg

Reply via email to