checksum error cause ACK with Checksum Error code

draft-ietf-lsvr-l3dl.xml

@@ -11,7 +11,7 @@
 <?rfc tocindent="yes"?>
 <?rfc tocompact="yes"?>
 
-<rfc category="std" docName="draft-ietf-lsvr-l3dl-02" ipr="trust200902">
+<rfc category="std" docName="draft-ietf-lsvr-l3dl-03" ipr="trust200902">
 
 <front>
 
@@ -71,7 +71,7 @@
     <t>The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
     "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
     "OPTIONAL" in this  document are to be interpreted as described in
-    BCP&nbsp;14 <xref target="RFC2119"/> <xref target="RFC8174"/> when,
+    BCP 14 <xref target="RFC2119"/> <xref target="RFC8174"/> when,
     and only when, they appear in all capitals, as shown here.</t>
 
     </note>
@@ -141,7 +141,7 @@
       <t hangText="Encapsulation:">Address Family Indicator and
       Subsequent Address Family Indicator (AFI/SAFI).  I.e. classes of
       layer 2.5 and 3 addresses such as IPv4, IPv6, MPLS, etc.</t>
-      <t hangText="Frame:">A Layer 2 packet.</t>
+      <t hangText="Frame:">A Layer 2 Ethernet packet.</t>
       <t hangText="Link or Logical Link:">A logical connection between
       two logical ports on two devices.  E.g. two VLANs between the same
       two ports are two links.</t>
@@ -210,8 +210,8 @@
     <t><list style="symbols">
       <t>Devices discover each other on logical links</t>
       <t>Logical Link Endpoint Identifiers are exchanged</t>
-      <t>Layer 2 Liveness Checks may be started</t>
+      <t>Layer 2 Liveness checks may be started</t>
-      <t>Encapsulation data are exchanged and IP-Level Liveness Checks
+      <t>Encapsulation data are exchanged and IP-Level Liveness checks
       enabled</t>
       <t>A BGP-like upper layer protocol is assumed to use these data to
       discover and build a topology database</t>
@@ -379,14 +379,15 @@
   <section anchor="transport" title="Transport Layer">
 
     <t>L3DL PDUs are carried by a simple transport layer which allows
-    PDUs to occupy many Ethernet frames.  An L3DL Ethernet frame is
+    PDUs to occupy many Ethernet frames.  The L3DL content of an
-    referred to as a Datagram.</t>
+    Ethernet frame, exclusive of Ethernet framing data, is referred to
+    as a Datagram.</t>
 
     <t>The L3DL Transport Layer encapsulates each Datagram using a
     common transport header.</t>
 
     <t>If a PDU does not fit in a single datagram, it is broken into
-    multiple datagrams and reassembled by the receiver a la <xref
+    multiple Datagrams and reassembled by the receiver a la <xref
     target="RFC0791"/> Section 2.3 Fragmentation.</t>
 
 <!--
@@ -429,7 +430,10 @@
       a datagram to 2^16 octets.</t>
 
       <t hangText="Checksum:">A 32 bit hash over the Datagram to detect
-      bit flips, see <xref target="checksum"/>.</t>
+      bit flips, see <xref target="checksum"/>.  If a Datagram fails a
+      checksum verification, the entire PDU is invalid and an ACK PDU
+      with Error Code "Checksum Error" is sent; see <xref
+      target="iana-error"/>.</t>
 
       <t hangText="Payload:">The PDU being transported or a fragment
       thereof.</t>
@@ -1581,10 +1585,11 @@ q-->
           Code    Error Name
           ----    -------------------
             0     No Error
-            1     Logical Link Addressing Conflict
+            1     Checksum Error
-            2     Authorization Failure in OPEN
+	    2	  Logical Link Addressing Conflict
-            3     Signature Failure in PDU
+            3     Authorization Failure in OPEN
-            4     Announce/Withdraw Error
+            4     Signature Failure in PDU
+            5     Announce/Withdraw Error
              </artwork>
            </figure>