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

wording tweaks, lowest IP is server

Browse source
This commit is contained in:
Randy Bush 2022-03-02 14:45:43 -08:00
parent 1772fdca14
commit a3ec5460e2
1 changed files with 17 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -126,10 +126,11 @@
messages.</t>
</list></t>
<t>In this document, the use case for L3ND is for point to point
links in a datacenter Clos (<xref target="Clos"/>) in order to
exchange the data needed for bootstrapping BGP-based peering, EVPNs,
etc. Once IP connectivity has been leveraged to get layer-3
<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
exchange the data needed to bootstrap BGP-based peering, EVPN, etc.;
often in a datacenter Clos <xref target="Clos"/> environment. Once
IP connectivity has been leveraged to discover1 layer-3
addressability and forwarding capabilities, normal IP forwarding and
routing can take over.</t>
@ -478,13 +479,18 @@ Flags (bit):
very large data PDUs while obviating the need to invent complex
transports.</t>
<t>The server, the sender of the HELLO, listens on the advertised
port for the TLS/TCP session open. The receiver of the acceptable
HELLO, the TLS/TCP client, initiates a TLS or raw TCP session with
the sender of the HELLO, the TLS/TCP server, preferably TLS, as
advertised. If TLS, the server has chosen and signaled either a
self-signed certificate or one configured from the operational CA
trusted by both parties, as negotiated in the HELLO exchange.</t>
<t>The L3ND peer with the higher IP address MUST act as the TLS/TCP
client and open the transport session (send SYN) toward the peer
with the lower IP address.</t>
<t>The server, the sender of the HELLO with the lower IP address,
listens on the advertised port for the TLS/TCP session open. The
receiver of the acceptable HELLO, the TLS/TCP client, initiates a
TLS or raw TCP session with the sender of the HELLO, the TLS/TCP
server, preferably TLS, as advertised. If TLS, the server has
chosen and signaled either a self-signed certificate or one
configured from the operational CA trusted by both parties, as
negotiated in the HELLO exchange.</t>
<t>Once the TLS/TCP session is established, if the link is
configured as point to point, the client side SHOULD stop listening