--- 1/draft-ietf-lisp-rfc8113bis-00.txt	2018-11-04 23:13:08.147927962 -0800
+++ 2/draft-ietf-lisp-rfc8113bis-01.txt	2018-11-04 23:13:08.163928350 -0800
@@ -1,21 +1,21 @@
 
 LISP                                                        M. Boucadair
 Internet-Draft                                              C. Jacquenet
 Obsoletes: 8113 (if approved)                                     Orange
-Updates: rfc6833bis (if approved)                     September 27, 2018
+Updates: rfc6833bis (if approved)                       November 5, 2018
 Intended status: Standards Track
-Expires: March 31, 2019
+Expires: May 9, 2019
 
  Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA
                   Registry for Packet Type Allocations
-                     draft-ietf-lisp-rfc8113bis-00
+                     draft-ietf-lisp-rfc8113bis-01
 
 Abstract
 
    This document specifies a Locator/ID Separation Protocol (LISP)
    shared message type for defining future extensions and conducting
    experiments without consuming a LISP packet type codepoint for each
    extension.
 
    This document obsoletes RFC 8113.
 
@@ -29,21 +29,21 @@
    Internet-Drafts are working documents of the Internet Engineering
    Task Force (IETF).  Note that other groups may also distribute
    working documents as Internet-Drafts.  The list of current Internet-
    Drafts is at https://datatracker.ietf.org/drafts/current/.
 
    Internet-Drafts are draft documents valid for a maximum of six months
    and may be updated, replaced, or obsoleted by other documents at any
    time.  It is inappropriate to use Internet-Drafts as reference
    material or to cite them other than as "work in progress."
 
-   This Internet-Draft will expire on March 31, 2019.
+   This Internet-Draft will expire on May 9, 2019.
 
 Copyright Notice
 
    Copyright (c) 2018 IETF Trust and the persons identified as the
    document authors.  All rights reserved.
 
    This document is subject to BCP 78 and the IETF Trust's Legal
    Provisions Relating to IETF Documents
    (https://trustee.ietf.org/license-info) in effect on the date of
    publication of this document.  Please review these documents
@@ -55,22 +55,23 @@
 
 Table of Contents
 
    1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
    2.  Requirements Language . . . . . . . . . . . . . . . . . . . .   2
    3.  LISP Shared Extension Message Type  . . . . . . . . . . . . .   3
    4.  Security Considerations . . . . . . . . . . . . . . . . . . .   3
    5.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   3
      5.1.  LISP Packet Types . . . . . . . . . . . . . . . . . . . .   3
      5.2.  Sub-Types . . . . . . . . . . . . . . . . . . . . . . . .   4
-   6.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   4
-   7.  Normative References  . . . . . . . . . . . . . . . . . . . .   4
+   6.  Changes from RFC 8113 . . . . . . . . . . . . . . . . . . . .   4
+   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   5
+   8.  Normative References  . . . . . . . . . . . . . . . . . . . .   5
    Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5
 
 1.  Introduction
 
    The Locator/ID Separation Protocol (LISP) base specification,
    [I-D.ietf-lisp-rfc6833bis], defines a set of primitives that are
    identified with a packet type code.  Several extensions have been
    proposed to add more LISP functionalities.  It is expected that
    additional LISP extensions will be proposed in the future.
 
@@ -160,37 +161,55 @@
    The values in the range 0-1023 are assigned via Standards Action.
    This range is provisioned to anticipate, in particular, the
    exhaustion of the LISP Packet types.
 
    The values in the range 1024-4095 are assigned on a First Come, First
    Served (FCFS) basis.  The registration procedure should provide IANA
    with the desired codepoint and a point of contact; providing a short
    description (together with an acronym, if relevant) of the foreseen
    usage of the extension message is also encouraged.
 
-6.  Acknowledgments
+6.  Changes from RFC 8113
+
+   The following changes were made from RFC 8113:
+
+   o  Change the status from Experimental to Standard track.
+
+   o  Indicate explicitly that the shared extension is used for two
+      purposes: extend the type space and conduct experiments to assess
+      new LISP extensions.  Therefore, this document updates
+      [I-D.ietf-lisp-rfc6833bis].
+
+   o  Delete pointers to some examples illustrating how the shared
+      extension message is used to extend the LISP protocol.
+
+   o  Request IANA to update the "IANA LISP Packet Types" and ""LISP
+      Shared Extension Message Type Sub-types" registries to point to
+      this document instead of RFC8113.
+
+7.  Acknowledgments
 
    This work is partly funded by ANR LISP-Lab project #ANR-13-INFR-
    009-X.
 
    Many thanks to Luigi Iannone, Dino Farinacci, and Alvaro Retana for
    the review.
 
    Thanks to Geoff Huston for the RtgDir directorate review.
 
-7.  Normative References
+8.  Normative References
 
    [I-D.ietf-lisp-rfc6833bis]
               Fuller, V., Farinacci, D., and A. Cabellos-Aparicio,
               "Locator/ID Separation Protocol (LISP) Control-Plane",
-              draft-ietf-lisp-rfc6833bis-15 (work in progress),
-              September 2018.
+              draft-ietf-lisp-rfc6833bis-19 (work in progress), October
+              2018.
 
    [RFC2119]  Bradner, S., "Key words for use in RFCs to Indicate
               Requirement Levels", BCP 14, RFC 2119,
               DOI 10.17487/RFC2119, March 1997,
               <https://www.rfc-editor.org/info/rfc2119>.
 
    [RFC8126]  Cotton, M., Leiba, B., and T. Narten, "Guidelines for
               Writing an IANA Considerations Section in RFCs", BCP 26,
               RFC 8126, DOI 10.17487/RFC8126, June 2017,
               <https://www.rfc-editor.org/info/rfc8126>.