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:41 -07:00
parent b5120766b2
commit 3ef2eab7d5
1 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

10
draft-ymbk-bgp-discovery-layers.txt
View file

@ -90,7 +90,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
endpoints. endpoints.
o Support using either a device's external interface or one of its o Support using either a device's external interface or one of its
loopback addresses for the BGP session endpoint. loopback addresses for the BGP session endpoint.
o Support discoverery of the peers' ASs. o Support discovery of the peers' ASs.
o Agree on any BGP session authentication and parameters. o Agree on any BGP session authentication and parameters.
o Enable Layer 3 link liveness detection, such as BFD. o Enable Layer 3 link liveness detection, such as BFD.
@ -138,7 +138,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
IP addresses. IP addresses.
o Each one's attributes, a deployment defined set, e.g.: leaf, o Each one's attributes, a deployment defined set, e.g.: leaf,
spine, ice cream flavor, ... These attributes are arbitrary and spine, ice cream flavor, ... These attributes are arbitrary and
operator dependednt. No assumptions should be made, code points operator dependent. No assumptions should be made, code points
assigned,, etc. assigned,, etc.
o Each one's layer three peering address(es), and o Each one's layer three peering address(es), and
o Other attributes required for BGP OPEN to succeed, e.g. o Other attributes required for BGP OPEN to succeed, e.g.
@ -232,7 +232,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
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, [I-D.ymbk-lsvr-lsoe], was simpler and might L3DL's predecessor, LSOE, [I-D.ymbk-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 ...
@ -248,7 +248,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
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 the exacerbated by the possibility of a potential peer not being on the
local subnet, and hence broadcast and simiar techniques may not be local subnet, and hence broadcast and similar techniques may not be
applicable. applicable.
If one can assume point-to-point links , then discovery might try If one can assume point-to-point links , then discovery might try
@ -263,7 +263,7 @@ Internet-Draft Trade-offs in BGP Peer Discovery May 2020
9. Discovery at Layer Seven 9. Discovery at Layer Seven
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, [RFC6830] or the Bitcoin mechanisms analogous to those used by LISP, [RFC6830] or the Bitcoin
Protocol. Protocol.