make nonce explicitly be session
This commit is contained in:
parent
d7694de555
commit
1fcda8adf5
1 changed files with 11 additions and 12 deletions
|
|
@ -130,7 +130,7 @@
|
|||
<?rfc subcompact="yes"?>
|
||||
<t>Discover each other's IP Addresses,</t>
|
||||
<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
|
||||
encapsulations,</t>
|
||||
<t>Provide authenticity, integrity, and verification of protocol
|
||||
|
|
@ -139,16 +139,16 @@
|
|||
<?rfc subcompact="no"?>
|
||||
</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
|
||||
exchange the data needed to bootstrap BGP-based peering, EVPN, etc.;
|
||||
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
|
||||
routing can take over.</t>
|
||||
|
||||
<t>L3ND might be found to be widely applicable to a range of routing
|
||||
and similar protocols which need Layer-3 neighbor discovery.</t>
|
||||
<t>L3ND might be more widely applicable to a range of routing and
|
||||
similar protocols which need Layer-3 neighbor discovery.</t>
|
||||
|
||||
</section>
|
||||
|
||||
|
|
@ -178,8 +178,7 @@
|
|||
of the largest packet that can be sent on a medium, see <xref
|
||||
target="RFC1122"/> 1.3.3.</t>
|
||||
<t hangText="PDU:">Protocol Data Unit, an L3ND application layer
|
||||
message. A PDU's content may need to be broken into multiple
|
||||
Datagrams to make it through MTU or other restrictions.</t>
|
||||
message.</t>
|
||||
<!-- <t hangText="RouterID:">An 32-bit identifier unique in the
|
||||
current routing domain, see <xref target="RFC6286"/>.</t> -->
|
||||
<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
|
||||
fields of the PDU from the Nonce through the Serial Number.</t>
|
||||
|
||||
<t>The four octet Nonce enables detection of a duplicate OPEN PDU.
|
||||
It SHOULD be either a random number or a high resolution timestamp.
|
||||
It is needed to prevent session closure due to a repeated OPEN
|
||||
caused by a race or a dropped or delayed ACK. It can be used to
|
||||
resume a dropped logical session.</t>
|
||||
<t>The four octet Nonce identifies a session. It enables detection
|
||||
of a duplicate OPEN PDU. It SHOULD be either a random number or a
|
||||
high resolution timestamp. It is needed to prevent session closure
|
||||
due to a repeated OPEN caused by a race or a dropped or delayed ACK.
|
||||
It can be used to resume a dropped logical session.</t>
|
||||
|
||||
<t>The one octet AttrCount is the number of attributes in the
|
||||
Attribute List. A node may send zero or more attributes.</t>
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue