-10 submitted

This commit is contained in:
Randy Bush 2023-07-25 14:29:15 -07:00
parent 0fd99db20e
commit ba7a23440d

View file

@ -11,7 +11,7 @@
<?rfc tocindent="yes"?> <?rfc tocindent="yes"?>
<?rfc tocompact="yes"?> <?rfc tocompact="yes"?>
<rfc consensus="yes" submissionType="IETF" category="std" docName="draft-ietf-lsvr-l3dl-09" ipr="trust200902"> <rfc consensus="yes" submissionType="IETF" category="std" docName="draft-ietf-lsvr-l3dl-10" ipr="trust200902" version="2">
<front> <front>
@ -85,12 +85,18 @@
<t>The Massive Data Center (MDC) environment presents unusual <t>The Massive Data Center (MDC) environment presents unusual
problems of scale, e.g. O(10,000) forwarding devices, while its problems of scale, e.g. O(10,000) forwarding devices, while its
homogeneity presents opportunities for simple approaches. homogeneity presents opportunities for simple approaches.
Approaches such as Jupiter Rising <xref target="JUPITER"/> use a Approaches such as <eref target="https://xml2rfc.tools.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/2975159.xml?anchor=JUPITER">&quot;Jupiter Rising: A study of non-blocking switching networks&quot; [PAYWALLED]</eref>
<!-- <xref target="JUPITER"/>
--> use a
central controller to deal with scaling, while BGP-SPF <xref central controller to deal with scaling, while BGP-SPF <xref
target="I-D.ietf-lsvr-bgp-spf"/> provides massive scale-out without target="I-D.ietf-lsvr-bgp-spf"/> provides massive scale-out without
centralization using a tried and tested scalable distributed control centralization using a tried and tested scalable distributed control
plane, offering a scalable routing solution in Clos <xref plane, offering a scalable routing solution in
target="Clos0"/><xref target="Clos1"/> and similar environments. <!-- <xref target="Clos0"/> -->
<eref target="https://en.wikipedia.org/wiki/Clos_network/">&quot;Clos Networks&quot;</eref>
<!--<xref target="Clos1"/>
-->
and similar environments.
But BGP-SPF and similar higher level device-spanning protocols, But BGP-SPF and similar higher level device-spanning protocols,
e.g. <xref target="I-D.malhotra-bess-evpn-lsoe"/>, need logical link e.g. <xref target="I-D.malhotra-bess-evpn-lsoe"/>, need logical link
state and addressing data from the network to build the routing state and addressing data from the network to build the routing
@ -1773,6 +1779,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
<?rfc include="reference.RFC.1122.xml"?> <?rfc include="reference.RFC.1122.xml"?>
<?rfc include="reference.RFC.1982.xml"?> <?rfc include="reference.RFC.1982.xml"?>
<?rfc include="reference.I-D.malhotra-bess-evpn-lsoe.xml"?> <?rfc include="reference.I-D.malhotra-bess-evpn-lsoe.xml"?>
<!--
<?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/2975159.xml?anchor=JUPITER"?> <?rfc include="https://xml2rfc.tools.ietf.org/public/rfc/bibxml-doi/reference.DOI.10.1145/2975159.xml?anchor=JUPITER"?>
<reference anchor="Clos0" > <reference anchor="Clos0" >
<front> <front>
@ -1791,6 +1798,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
<date/> <date/>
</front> </front>
</reference> </reference>
-->
</references> </references>
</back> </back>