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

some typos

Browse source
This commit is contained in:
Randy Bush 2024-01-30 13:12:52 -08:00
parent f5eb7c24b0
commit ff8e7f4a4b
1 changed files with 3 additions and 3 deletions
Download patch file Download diff file Expand all files Collapse all files

6
draft-ietf-lsvr-l3dl.xml
View file

@ -1458,7 +1458,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
sub-TLV-->.</t> sub-TLV-->.</t>
<t>If there are one or more open BGP sessions, <!-- absent a BGP <t>If there are one or more open BGP sessions, <!-- absent a BGP
Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD not Restart sub-TLV, --> receipt of a new BGP ULPC PDU SHOULD NOT
affect these sessions. The received data are stored for a future affect these sessions. The received data are stored for a future
session restart.</t> session restart.</t>
@ -1469,7 +1469,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
<t>For each BGP peering on a link here MUST be one agreed <t>For each BGP peering on a link here MUST be one agreed
encapsulation, and the addresses used MUST be in the corresponding encapsulation, and the addresses used MUST be in the corresponding
L3DP IPv4/IPv6 Announcement PDUs. If the choice is ambiguous, an L3DL IPv4/IPv6 Announcement PDUs. If the choice is ambiguous, an
Attribute may be used to signal preferences.</t> Attribute may be used to signal preferences.</t>
<t>If a peering address has been announced as a loopback, <t>If a peering address has been announced as a loopback,
@ -1590,7 +1590,7 @@ uint32_t sbox_checksum_32(const uint8_t *b, const size_t n)
configuration of the environment, it might be a simple MD5 key configuration of the environment, it might be a simple MD5 key
(see <xref target="RFC2385"/>), the name of a key chain in a (see <xref target="RFC2385"/>), the name of a key chain in a
KARP database (see <xref target="RFC7210"/>), or one of multiple KARP database (see <xref target="RFC7210"/>), or one of multiple
Authentication sub-TLVs to support hop<xref Authentication sub-TLVs to support <xref
target="RFC4808"/>.</t> target="RFC4808"/>.</t>
<!-- <!--