randy/draft-l3nd
1
0
Fork 0
Code Issues 3 Pull requests Projects Releases Packages Wiki Activity Actions

-01 with lowest ip server, and some bumph

Browse source
This commit is contained in:
Randy Bush 2022-03-03 14:19:28 -08:00
parent a3ec5460e2
commit 7e172c8236
1 changed files with 18 additions and 5 deletions
Download patch file Download diff file Expand all files Collapse all files

23
draft-ymbk-idr-l3nd.xml
View file

@ -11,7 +11,7 @@
<?rfc tocindent="yes"?> <?rfc tocindent="yes"?>
<?rfc tocompact="yes"?> <?rfc tocompact="yes"?>
<rfc consensus="yes" category="std" submissionType="IETF" docName="draft-ymbk-idr-l3nd-00" ipr="trust200902"> <rfc consensus="yes" category="std" submissionType="IETF" docName="draft-ymbk-idr-l3nd-01" ipr="trust200902">
<front> <front>
@ -115,22 +115,35 @@
provides a similar solution at Layer-3, attempting to be as similar provides a similar solution at Layer-3, attempting to be as similar
as reasonable to L3DL.</t> as reasonable to L3DL.</t>
<t>Some guiding principles when dealing with datacenters with tens
of thousands of devices are <list style="symbols">
<?rfc subcompact="yes"?>
<t>Predictable Reliability,</t>
<t>Security: Authorization and Integrity more than
Confidentiality, and</t>
<t>Massive Scalability</t>
<?rfc subcompact="no"?>
</list></t>
<t>Layer-3 Neighbor Discovery (L3ND) provides brutally simple <t>Layer-3 Neighbor Discovery (L3ND) provides brutally simple
mechanisms for neighboring devices to <list style="symbols"> mechanisms for neighboring devices to <list style="symbols">
<?rfc subcompact="yes"?>
<t>Discover each other's IP Addresses,</t> <t>Discover each other's IP Addresses,</t>
<t>Discover mutually supported layer-3 encapsulations, e.g. <t>Discover mutually supported layer-3 encapsulations, e.g.
IP/MPLS,</t> IP/MPLS,</t>
<t>Discover Layer-3 IP and/or MPLS addressing of interfaces of the <t>Discover Layer-3 IP and/or MPLS addressing of interfaces of the
encapsulations,</t> encapsulations,</t>
<t>Provide for authenticity and verification of protocol <t>Provide authenticity, integrity, and verification of protocol
messages.</t> messages, and</t>
<t>Accommodate scaling needed for EVPN etc.
<?rfc subcompact="no"?>
</list></t> </list></t>
<t>L3DN is intended for use within single IP subnets (IP over <t>L3DN is intended for use within single IP subnets (IP over
Ethernet or other point-to-point or multi-point IP link) in order to Ethernet or other point-to-point or multi-point IP link) in order to
exchange the data needed to bootstrap BGP-based peering, EVPN, etc.; exchange the data needed to bootstrap BGP-based peering, EVPN, etc.;
often in a datacenter Clos <xref target="Clos"/> environment. Once especially in a datacenter Clos <xref target="Clos"/> environment.
IP connectivity has been leveraged to discover1 layer-3 Once IP connectivity has been leveraged to discover1 layer-3
addressability and forwarding capabilities, normal IP forwarding and addressability and forwarding capabilities, normal IP forwarding and
routing can take over.</t> routing can take over.</t>