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

make nonce explicitly be session

Browse source
This commit is contained in:
Randy Bush 2022-03-19 14:14:59 -07:00
parent d7694de555
commit 1fcda8adf5
1 changed files with 11 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

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

@ -130,7 +130,7 @@
<?rfc subcompact="yes"?> <?rfc subcompact="yes"?>
<t>Discover each other's IP Addresses,</t> <t>Discover each other's IP Addresses,</t>
<t>Discover mutually supported layer-3 encapsulations, e.g. <t>Discover mutually supported layer-3 encapsulations, e.g.
IP/MPLS,</t> IPv4/IPv6//MPLS,</t>
<t>Discover Layer-3 IP and/or MPLS addressing of interfaces of the <t>Discover Layer-3 IP and/or MPLS addressing of interfaces of the
encapsulations,</t> encapsulations,</t>
<t>Provide authenticity, integrity, and verification of protocol <t>Provide authenticity, integrity, and verification of protocol
@ -139,16 +139,16 @@
<?rfc subcompact="no"?> <?rfc subcompact="no"?>
</list></t> </list></t>
<t>L3DN is intended for use within single IP subnets (IP over <t>L3ND is intended for use within single IP subnets (IP over
Ethernet or other point-to-point or multi-point IP link) in order to 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.; exchange the data needed to bootstrap BGP-based peering, EVPN, etc.;
especially in a datacenter Clos <xref target="Clos"/> environment. especially in a datacenter Clos <xref target="Clos"/> environment.
Once IP connectivity has been leveraged to discover1 layer-3 Once IP connectivity has been leveraged to discover layer-3
addressability and forwarding capabilities, normal IP forwarding and addressability and forwarding capabilities, normal IP forwarding and
routing can take over.</t> routing can take over.</t>
<t>L3ND might be found to be widely applicable to a range of routing <t>L3ND might be more widely applicable to a range of routing and
and similar protocols which need Layer-3 neighbor discovery.</t> similar protocols which need Layer-3 neighbor discovery.</t>
</section> </section>
@ -178,8 +178,7 @@
of the largest packet that can be sent on a medium, see <xref of the largest packet that can be sent on a medium, see <xref
target="RFC1122"/> 1.3.3.</t> target="RFC1122"/> 1.3.3.</t>
<t hangText="PDU:">Protocol Data Unit, an L3ND application layer <t hangText="PDU:">Protocol Data Unit, an L3ND application layer
message. A PDU's content may need to be broken into multiple message.</t>
Datagrams to make it through MTU or other restrictions.</t>
<!-- <t hangText="RouterID:">An 32-bit identifier unique in the <!-- <t hangText="RouterID:">An 32-bit identifier unique in the
current routing domain, see <xref target="RFC6286"/>.</t> --> current routing domain, see <xref target="RFC6286"/>.</t> -->
<t hangText="Session:">An established, via exchange of OPEN PDUs, <t hangText="Session:">An established, via exchange of OPEN PDUs,
@ -567,11 +566,11 @@ Flags (bit):
<t>The four octet Payload Length is the number of octets in all <t>The four octet Payload Length is the number of octets in all
fields of the PDU from the Nonce through the Serial Number.</t> fields of the PDU from the Nonce through the Serial Number.</t>
<t>The four octet Nonce enables detection of a duplicate OPEN PDU. <t>The four octet Nonce identifies a session. It enables detection
It SHOULD be either a random number or a high resolution timestamp. of a duplicate OPEN PDU. It SHOULD be either a random number or a
It is needed to prevent session closure due to a repeated OPEN high resolution timestamp. It is needed to prevent session closure
caused by a race or a dropped or delayed ACK. It can be used to due to a repeated OPEN caused by a race or a dropped or delayed ACK.
resume a dropped logical session.</t> It can be used to resume a dropped logical session.</t>
<t>The one octet AttrCount is the number of attributes in the <t>The one octet AttrCount is the number of attributes in the
Attribute List. A node may send zero or more attributes.</t> Attribute List. A node may send zero or more attributes.</t>