randy/draft-bgp-discovery-layers
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

refs finally available

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

12
draft-ymbk-bgp-discovery-layers.xml
View file

@ -321,7 +321,7 @@
<t>
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
discovered peer. Details such as loopback peering are handled
by attributes in the L3DL protocol itself.
@ -342,13 +342,13 @@
<t>
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>
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.
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
week's work could customize the design for the IDR Design Team's
needs. But ...
@ -457,9 +457,9 @@
<?rfc include="reference.RFC.6830"?>
<?rfc include="reference.I-D.acee-idr-lldp-peer-discovery"?>
<?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-signing"?>
<?rfc include="reference.I-D.ymbk-lsvr-lsoe"?>
<?rfc include="reference.I-D.ietf-lsvr-l3dl-ulpc"?>
<?rfc include="reference.I-D.ietf-lsvr-l3dl-signing"?>
<?rfc include="reference.I-D.ietf-lsvr-lsoe"?>
</references>
<!--