--- 1/draft-ietf-lisp-rfc6830bis-31.txt	2020-03-05 06:13:34.272343609 -0800
+++ 2/draft-ietf-lisp-rfc6830bis-32.txt	2020-03-05 06:13:34.444347986 -0800
@@ -5,21 +5,21 @@
 Intended status: Standards Track             vaf.net Internet Consulting
 Expires: September 6, 2020                                      D. Meyer
                                                                1-4-5.net
                                                                 D. Lewis
                                                            Cisco Systems
                                                        A. Cabellos (Ed.)
                                                        UPC/BarcelonaTech
                                                            March 5, 2020
 
                The Locator/ID Separation Protocol (LISP)
-                     draft-ietf-lisp-rfc6830bis-31
+                     draft-ietf-lisp-rfc6830bis-32
 
 Abstract
 
    This document describes the Data-Plane protocol for the Locator/ID
    Separation Protocol (LISP).  LISP defines two namespaces, End-point
    Identifiers (EIDs) that identify end-hosts and Routing Locators
    (RLOCs) that identify network attachment points.  With this, LISP
    effectively separates control from data, and allows routers to create
    overlay networks.  LISP-capable routers exchange encapsulated packets
    according to EID-to-RLOC mappings stored in a local Map-Cache.
@@ -855,21 +855,21 @@
    misconfiguration.
 
    Some xTRs and PxTRs performs re-encapsulation operations and need to
    treat the 'Explicit Congestion Notification' (ECN) in a special way.
    Because the re-encapsulation operation is a sequence of two
    operations, namely a decapsulation followed by an encapsulation, the
    ECN bits MUST be treated as described above for these two operations.
 
    The LISP dataplane protocol is not backwards compatible with
    [RFC6830] and does not have explicit support for introducing future
-   protocol changes (e.g. an explicit version field), However, the LISP
+   protocol changes (e.g. an explicit version field).  However, the LISP
    control plane [I-D.ietf-lisp-rfc6833bis] allows an ETR to register
    dataplane capabilities by means of new LCAF types [RFC8060].  In this
    way an ITR can be made aware of the dataplane capabilities of an ETR,
    and encapsulate accordingly.  The specification of the new LCAF
    types, new LCAF mechanisms, and their use, is out of the scope of
    this document.
 
 6.  LISP EID-to-RLOC Map-Cache
 
    ITRs and PITRs maintain an on-demand cache, referred as LISP EID-to-