refs finally available

This commit is contained in:
Randy Bush 2020-05-27 14:52:23 -07:00
parent 05c31f000b
commit a75e2c9146
2 changed files with 26 additions and 26 deletions

View file

@ -4,9 +4,9 @@
Network Working Group R. Bush Network Working Group R. Bush
Internet-Draft Arrcus, Inc. & Internet Initiative Japan Internet-Draft Arrcus, Inc. & Internet Initiative Japan
Updates: 6811 (if approved) May 25, 2020 Updates: 6811 (if approved) May 27, 2020
Intended status: Informational Intended status: Informational
Expires: November 26, 2020 Expires: November 28, 2020
Trade-offs in BGP Peer Discovery Trade-offs in BGP Peer Discovery
@ -36,7 +36,7 @@ Status of This Memo
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on November 26, 2020. This Internet-Draft will expire on November 28, 2020.
Copyright Notice Copyright Notice
@ -53,7 +53,7 @@ Copyright Notice
Bush Expires November 26, 2020 [Page 1] Bush Expires November 28, 2020 [Page 1]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -109,7 +109,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Bush Expires November 26, 2020 [Page 2] Bush Expires November 28, 2020 [Page 2]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -165,7 +165,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Bush Expires November 26, 2020 [Page 3] Bush Expires November 28, 2020 [Page 3]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -214,14 +214,14 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
abilities, and link liveness which may then be disseminated using abilities, and link liveness which may then be disseminated using
BGP-SPF and similar protocols. BGP-SPF and similar protocols.
L3DL Upper Layer Protocol Configuration, [I-D.ymbk-lsvr-l3dl-ulpc], L3DL Upper Layer Protocol Configuration, [I-D.ietf-lsvr-l3dl-ulpc],
details signaling the minimal set of parameters needed to start a BGP details signaling the minimal set of parameters needed to start a BGP
session with a discovered peer. Details such as loopback peering are session with a discovered peer. Details such as loopback peering are
handled by attributes in the L3DL protocol itself. handled by attributes in the L3DL protocol itself.
Bush Expires November 26, 2020 [Page 4] Bush Expires November 28, 2020 [Page 4]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -231,11 +231,11 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
o BGP Authentication. o BGP Authentication.
L3DL and L3DL-ULPC have well-specified security mechanisms, see L3DL and L3DL-ULPC have well-specified security mechanisms, see
[I-D.ymbk-lsvr-l3dl-signing]. [I-D.ietf-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.ietf-lsvr-lsoe], was simpler and might
be a better candidate for adaptation. A week's work could customize be a better candidate for adaptation. A week's work could customize
the design for the IDR Design Team's needs. But ... the design for the IDR Design Team's needs. But ...
@ -277,7 +277,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
Bush Expires November 26, 2020 [Page 5] Bush Expires November 28, 2020 [Page 5]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -313,27 +313,27 @@ 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] [I-D.ietf-lsvr-l3dl-signing]
Bush, R. and R. Austein, "Layer 3 Discovery and Liveness Bush, R. and R. Austein, "Layer 3 Discovery and Liveness
Signing", draft-ymbk-lsvr-l3dl-signing-01 (work in Signing", draft-ietf-lsvr-l3dl-signing-00 (work in
progress), May 2020. progress), May 2020.
[I-D.ymbk-lsvr-l3dl-ulpc] [I-D.ietf-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-ietf-lsvr-l3dl-ulpc-00 (work in
progress), May 2020. progress), May 2020.
[I-D.ymbk-lsvr-lsoe] [I-D.ietf-lsvr-lsoe]
Bush, R., Austein, R., and K. Patel, "Link State Over Bush, R., Austein, R., and K. Patel, "Link State Over
Ethernet", draft-ymbk-lsvr-lsoe-03 (work in progress), Ethernet", draft-ietf-lsvr-lsoe-01 (work in progress),
November 2018. February 2019.
Bush Expires November 26, 2020 [Page 6] Bush Expires November 28, 2020 [Page 6]
Internet-Draft Trade-offs in BGP Peer Discovery May 2020 Internet-Draft Trade-offs in BGP Peer Discovery May 2020
@ -389,4 +389,4 @@ Author's Address
Bush Expires November 26, 2020 [Page 7] Bush Expires November 28, 2020 [Page 7]

View file

@ -321,7 +321,7 @@
<t> <t>
L3DL Upper Layer Protocol Configuration, <xref L3DL Upper Layer Protocol Configuration, <xref
target="I-D.ymbk-lsvr-l3dl-ulpc"/>, details signaling the target="I-D.ietf-lsvr-l3dl-ulpc"/>, details signaling the
minimal set of parameters needed to start a BGP session with a minimal set of parameters needed to start a BGP session with a
discovered peer. Details such as loopback peering are handled discovered peer. Details such as loopback peering are handled
by attributes in the L3DL protocol itself. by attributes in the L3DL protocol itself.
@ -342,13 +342,13 @@
<t> <t>
L3DL and L3DL-ULPC have well-specified security mechanisms, see L3DL and L3DL-ULPC have well-specified security mechanisms, see
<xref target="I-D.ymbk-lsvr-l3dl-signing"/>. <xref target="I-D.ietf-lsvr-l3dl-signing"/>.
</t> </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.
L3DL's predecessor, LSOE, <xref target="I-D.ymbk-lsvr-lsoe"/>, L3DL's predecessor, LSOE, <xref target="I-D.ietf-lsvr-lsoe"/>,
was simpler and might be a better candidate for adaptation. A was simpler and might be a better candidate for adaptation. A
week's work could customize the design for the IDR Design Team's week's work could customize the design for the IDR Design Team's
needs. But ... needs. But ...
@ -457,9 +457,9 @@
<?rfc include="reference.RFC.6830"?> <?rfc include="reference.RFC.6830"?>
<?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.ietf-lsvr-l3dl-ulpc"?>
<?rfc include="reference.I-D.ymbk-lsvr-l3dl-signing"?> <?rfc include="reference.I-D.ietf-lsvr-l3dl-signing"?>
<?rfc include="reference.I-D.ymbk-lsvr-lsoe"?> <?rfc include="reference.I-D.ietf-lsvr-lsoe"?>
</references> </references>
<!-- <!--