From ea02eaee318694488329d1a3f80a39939c677d2e Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Sun, 13 Feb 2022 14:23:27 -0800 Subject: [PATCH] some things from keyur review --- draft-ymbk-idr-l3-discovery.xml | 153 ++++++++++++++++++-------------- 1 file changed, 84 insertions(+), 69 deletions(-) diff --git a/draft-ymbk-idr-l3-discovery.xml b/draft-ymbk-idr-l3-discovery.xml index db3267b..14fe364 100644 --- a/draft-ymbk-idr-l3-discovery.xml +++ b/draft-ymbk-idr-l3-discovery.xml @@ -31,21 +31,6 @@ - - Hickory Hill Consulting -
- - 7453 Hickory Hill - Saline - MI - 48176 - USA - - +1-734-604-0332 - shares@ndzh.com -
-
- Vigil Security, LLC
@@ -67,6 +52,21 @@
+ + Hickory Hill Consulting +
+ + 7453 Hickory Hill + Saline + MI + 48176 + USA + + +1-734-604-0332 + shares@ndzh.com +
+
+ Arrcus
@@ -456,14 +456,16 @@ Flags (bit): + The Payload Length is 24 to cover the Flags and Port fields. + The Port is the TCP Port Number (TBD3) on which the HELLO sender MUST have a waiting TLS/TCP (as specified in Flags) server listening. Though the IANA assigned well-known port SHOULD be used, this field allows configuration of alternate ports. The HELLO PDU is unique in that it is encapsulated in a multicast - UDP packet. It solicits TLS/TCP connections from other peers on a - link. See for why multicast is used. + UDP packet. It offers TLS/TCP service to peers on a link. See + for why multicast is used. The HELLO PDU is an IPv4 or IPv6 UDP PDU sent to a link-local multicast address. It solicits a unicast TLS/TCP open request(s) of @@ -477,7 +479,8 @@ Flags (bit): peer's destination IP address is known after the HELLO. When an interface is turned up on a device, it SHOULD issue a - HELLO if it is to participate in L3ND sessions. + HELLO if it is to participate in L3ND sessions and repeat HELLOs at + a configured interval, with a default of 60 seconds. An implementation SHOULD provide the ability to distribute one or more loopback addresses or interfaces into L3ND on an external L3ND speaking interface.