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

spell check <blush>

Browse source
This commit is contained in:
Randy Bush 2020-05-25 20:28:13 -07:00
parent f79d3cc9cb
commit b5120766b2
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -73,7 +73,7 @@
<section anchor="underlay" title="BGP is the Underlay"> <section anchor="underlay" title="BGP is the Underlay">
<t> <t>
The assumedenvironment has BGP used as the underlay routing The assumed environment has BGP used as the underlay routing
protocol in data center. protocol in data center.
</t> </t>
@ -100,7 +100,7 @@
its loopback addresses for the BGP session endpoint. its loopback addresses for the BGP session endpoint.
</t> </t>
<t> <t>
Support discoverery of the peers' ASs. Support discovery of the peers' ASs.
</t> </t>
<t> <t>
Agree on any BGP session authentication and parameters. Agree on any BGP session authentication and parameters.
@ -178,7 +178,7 @@
<t> <t>
Each one's attributes, a deployment defined set, e.g.: leaf, Each one's attributes, a deployment defined set, e.g.: leaf,
spine, ice cream flavor, ... These attributes are arbitrary spine, ice cream flavor, ... These attributes are arbitrary
and operator dependednt. No assumptions should be made, code and operator dependent. No assumptions should be made, code
points assigned,, etc. points assigned,, etc.
</t> </t>
@ -345,7 +345,7 @@
<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 reedecesor, LSOE, <xref target="I-D.ymbk-lsvr-lsoe"/>, L3DL's predecessor, LSOE, <xref target="I-D.ymbk-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 ...
@ -373,7 +373,7 @@
The principal problem would appear to be discovery at Layer-3, The principal problem would appear to be discovery at Layer-3,
because one neither knows whether to use IPv4 or IPv6. This is because one neither knows whether to use IPv4 or IPv6. This is
exacerbated by the possibility of a potential peer not being on exacerbated by the possibility of a potential peer not being on
the local subnet, and hence broadcast and simiar techniques may the local subnet, and hence broadcast and similar techniques may
not be applicable. not be applicable.
</t> </t>
@ -398,7 +398,7 @@
<section anchor="layer7" title="Discovery at Layer Seven"> <section anchor="layer7" title="Discovery at Layer Seven">
<t> <t>
Peer discovery at Layer-7 requires application layer rendezcous Peer discovery at Layer-7 requires application layer rendezvous
mechanisms analogous to those used by LISP, <xref mechanisms analogous to those used by LISP, <xref
target="RFC6830"/> or the Bitcoin Protocol. target="RFC6830"/> or the Bitcoin Protocol.
</t> </t>