add l3dl signing

This commit is contained in:
Randy Bush 2020-05-25 20:39:28 -07:00
parent 04f7097506
commit 05c31f000b
2 changed files with 28 additions and 22 deletions

View file

@ -206,7 +206,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Which of these are really necessary could be discussed. Which of these are really necessary could be discussed.
7.2. Layer-3 Discovery Protocol (L3dl) 7.2. Layer-3 Discovery Protocol (L3DL)
L3DL [I-D.ietf-lsvr-l3dl] is an ongoing development in the IETF LSVR L3DL [I-D.ietf-lsvr-l3dl] is an ongoing development in the IETF LSVR
Working Group with the goals of discovering IP Layer-3 attributes of Working Group with the goals of discovering IP Layer-3 attributes of
@ -230,6 +230,9 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
o IP address, IPv4 or IPv6, and o IP address, IPv4 or IPv6, and
o BGP Authentication. o BGP Authentication.
L3DL and L3DL-ULPC have well-specified security mechanisms, see
[I-D.ymbk-lsvr-l3dl-signing].
This is similar but not quite the sane as the needs of this IDR This is similar but not quite the sane as the needs of this IDR
Design Team. E.g., L3DL is designed to meet more complex needs. Design Team. E.g., L3DL is designed to meet more complex needs.
L3DL's predecessor, LSOE, [I-D.ymbk-lsvr-lsoe], was simpler and might L3DL's predecessor, LSOE, [I-D.ymbk-lsvr-lsoe], was simpler and might
@ -272,9 +275,6 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
reach the rendezvous. In a BGP centric deployment this could pose a reach the rendezvous. In a BGP centric deployment this could pose a
chicken and egg problem. chicken and egg problem.
Rendezvous approaches may appeal to deployments which favor a central
control framework.
Bush Expires November 26, 2020 [Page 5] Bush Expires November 26, 2020 [Page 5]
@ -282,6 +282,9 @@ Bush Expires November 26, 2020 [Page 5]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Rendezvous approaches may appeal to deployments which favor a central
control framework.
On the other hand, those who favor distributed protocols will have On the other hand, those who favor distributed protocols will have
the classic worries about fragility, redundancy, reliability, etc. the classic worries about fragility, redundancy, reliability, etc.
@ -310,6 +313,11 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
and Liveness", draft-ietf-lsvr-l3dl-04 (work in progress), and Liveness", draft-ietf-lsvr-l3dl-04 (work in progress),
May 2020. May 2020.
[I-D.ymbk-lsvr-l3dl-signing]
Bush, R. and R. Austein, "Layer 3 Discovery and Liveness
Signing", draft-ymbk-lsvr-l3dl-signing-01 (work in
progress), May 2020.
[I-D.ymbk-lsvr-l3dl-ulpc] [I-D.ymbk-lsvr-l3dl-ulpc]
Bush, R. and K. Patel, "L3DL Upper Layer Protocol Bush, R. and K. Patel, "L3DL Upper Layer Protocol
Configuration", draft-ymbk-lsvr-l3dl-ulpc-03 (work in Configuration", draft-ymbk-lsvr-l3dl-ulpc-03 (work in
@ -320,14 +328,6 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Ethernet", draft-ymbk-lsvr-lsoe-03 (work in progress), Ethernet", draft-ymbk-lsvr-lsoe-03 (work in progress),
November 2018. November 2018.
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830,
DOI 10.17487/RFC6830, January 2013,
<https://www.rfc-editor.org/info/rfc6830>.
Appendix A. Acknowledgements
The authors wish to thank .
@ -338,6 +338,15 @@ Bush Expires November 26, 2020 [Page 6]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
[RFC6830] Farinacci, D., Fuller, V., Meyer, D., and D. Lewis, "The
Locator/ID Separation Protocol (LISP)", RFC 6830,
DOI 10.17487/RFC6830, January 2013,
<https://www.rfc-editor.org/info/rfc6830>.
Appendix A. Acknowledgements
The authors wish to thank .
Author's Address Author's Address
Randy Bush Randy Bush
@ -370,15 +379,6 @@ Author's Address

View file

@ -308,7 +308,7 @@
</section> </section>
<section anchor="l3dl" title="Layer-3 Discovery Protocol (L3dl)"> <section anchor="l3dl" title="Layer-3 Discovery Protocol (L3DL)">
<t> <t>
L3DL <xref target="I-D.ietf-lsvr-l3dl"/> is an ongoing L3DL <xref target="I-D.ietf-lsvr-l3dl"/> is an ongoing
@ -340,6 +340,11 @@
</list> </list>
</t> </t>
<t>
L3DL and L3DL-ULPC have well-specified security mechanisms, see
<xref target="I-D.ymbk-lsvr-l3dl-signing"/>.
</t>
<t> <t>
This is similar but not quite the sane as the needs of this IDR This is similar but not quite the sane as the needs of this IDR
Design Team. E.g., L3DL is designed to meet more complex needs. Design Team. E.g., L3DL is designed to meet more complex needs.
@ -453,6 +458,7 @@
<?rfc include="reference.I-D.acee-idr-lldp-peer-discovery"?> <?rfc include="reference.I-D.acee-idr-lldp-peer-discovery"?>
<?rfc include="reference.I-D.ietf-lsvr-l3dl"?> <?rfc include="reference.I-D.ietf-lsvr-l3dl"?>
<?rfc include="reference.I-D.ymbk-lsvr-l3dl-ulpc"?> <?rfc include="reference.I-D.ymbk-lsvr-l3dl-ulpc"?>
<?rfc include="reference.I-D.ymbk-lsvr-l3dl-signing"?>
<?rfc include="reference.I-D.ymbk-lsvr-lsoe"?> <?rfc include="reference.I-D.ymbk-lsvr-lsoe"?>
</references> </references>