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

gtsm by default

Browse source
This commit is contained in:
Randy Bush 2022-02-13 17:34:12 -08:00
parent ea02eaee31
commit 762c824df5
1 changed files with 9 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

9
draft-ymbk-idr-l3-discovery.xml
View file

@ -500,6 +500,10 @@ Flags (bit):
TLS/TCP service, and responses MUST be unicast TLS/TCP client TLS/TCP service, and responses MUST be unicast TLS/TCP client
session open requests to it using the same AFI.</t> session open requests to it using the same AFI.</t>
<t>By default, GTSM, <xref target="RFC5082"/>, SHOULD be enabled to
test that a received HELLO MUST be on the local link. It MAY be
disabled by configuration.</t>
<t>If more than one device responds, one adjacency is formed for <t>If more than one device responds, one adjacency is formed for
each unique source IP address. L3ND treats each adjacency as a each unique source IP address. L3ND treats each adjacency as a
separate logical link.</t> separate logical link.</t>
@ -533,6 +537,10 @@ Flags (bit):
would have compatible parameters on all devices, any disagreement would have compatible parameters on all devices, any disagreement
over TLS/TCP or trust anchors MUST be logged.</t> over TLS/TCP or trust anchors MUST be logged.</t>
<t>By default, GTSM, <xref target="RFC5082"/>, SHOULD be enabled to
ensure that a SYN received in response to a HELLO is on the local
link. It MAY be disabled by configuration.</t>
<t>If the receiver of a HELLO agrees with the sender's choice of <t>If the receiver of a HELLO agrees with the sender's choice of
TLS/TCP and authentication, both sides have agreed on an AFI for the TLS/TCP and authentication, both sides have agreed on an AFI for the
transport and on each other's IP address in that AFI. This is transport and on each other's IP address in that AFI. This is
@ -1329,6 +1337,7 @@ Flags (bit):
<?rfc include="reference.RFC.2119.xml"?> <?rfc include="reference.RFC.2119.xml"?>
<?rfc include="reference.RFC.3032.xml"?> <?rfc include="reference.RFC.3032.xml"?>
<?rfc include="reference.RFC.4271.xml"?> <?rfc include="reference.RFC.4271.xml"?>
<?rfc include="reference.RFC.5082.xml"?>
<?rfc include="reference.RFC.5226.xml"?> <?rfc include="reference.RFC.5226.xml"?>
<!--<?rfc include="reference.RFC.5880.xml"?> --> <!--<?rfc include="reference.RFC.5880.xml"?> -->
<!--<?rfc include="reference.RFC.6286.xml"?> --> <!--<?rfc include="reference.RFC.6286.xml"?> -->