From 2fb5ac051b1c352b69173494a3718ebeabfb0822 Mon Sep 17 00:00:00 2001 From: Randy Bush Date: Wed, 29 Jul 2020 12:20:10 -0700 Subject: [PATCH] spell --- draft-ietf-lsvr-l3dl.xml | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-) diff --git a/draft-ietf-lsvr-l3dl.xml b/draft-ietf-lsvr-l3dl.xml index 2cc5d65..82361e2 100644 --- a/draft-ietf-lsvr-l3dl.xml +++ b/draft-ietf-lsvr-l3dl.xml @@ -224,7 +224,7 @@ Encapsulation data are exchanged and IP-Level Liveness checks enabled A BGP-like upper layer protocol is assumed to use the - identiiers and encapsulation data to discover and build a topology + identifiers and encapsulation data to discover and build a topology database @@ -409,6 +409,10 @@ There are no intermediate devices capable of further fragmentation or reassembly. + As fragments are not ACK paced (as PDUs are), a PDU might need a + large number of frames to be sent. To avoid overwhelming bursts, + the sender should pace them ***********. + L3DL is carrying relatively small amounts of data on relatively high bandwidth links, and at a time when the link is not active with other data as it does not yet have layer three connectivity. So @@ -844,7 +848,9 @@ q--> Although delay and jitter in responding with an OPEN were specified above, beware of load created by long strings of - authentication failures and retries. + authentication failures and retries. A confugurable failure count + limit (default 8) SHOULD result in giving up on the connection + attempt. The Serial Number is that of the last received and processed PDU. This allows a receiver sending an OPEN to tell the sender that the