Locator/ID Separation Protocol (LISP): Shared Extension Message and IANA Registry for Packet Type Allocations
draft-ietf-lisp-rfc8113bis-03

[Ballot comment]
* Section 5.1.  LISP Packet Types

"The values in the ranges 5-7 and 9-14 can be assigned via Standards Action [RFC8126]."

Since LISP-DDT already used up packet type 6 this text probably needs to get updated.

(Via drafts-lastcall@iana.org): IESG/Authors/WG Chairs:

The IANA Functions Operator has completed its review of draft-ietf-lisp-rfc8113bis-01. If any part of this review is inaccurate, please let us know.

The IANA Functions Operator understands that, upon approval of this document, there are three actions which we must complete.

First, in the LISP Packet Types registry on the Locator/ID Separation Protocol (LISP) Parameters registry page located at:

https://www.iana.org/assignments/lisp-parameters/

The registration procedure will be changed so that the values in the ranges 5-7 and 9-14 can be assigned via Standards Action as defined in RFC 8126. In addition, the reference for the registry is to be changed from RFC 8113 to [ RFC-to-be ].

Second, also in the LISP Packet Types registry on the Locator/ID Separation Protocol (LISP) Parameters registry page located at:

https://www.iana.org/assignments/lisp-parameters/

the registration for code 15 is to have its reference changed from RFC 8113 to [ RFC-to-be ].

Third, in the LISP Shared Extension Message Type Sub-types registry on the Locator/ID Separation Protocol (LISP) Parameters registry page located at:

https://www.iana.org/assignments/lisp-parameters/

the reference for the registry is to be changed from RFC 8113 to [ RFC-to-be ].

The IANA Functions Operator understands that these are the only actions required to be completed upon approval of this document.

Note:  The actions requested in this document will not be completed until the document has been approved for publication as an RFC. This message is meant only to confirm the list of actions that will be performed.

Thank you,

Sabrina Tanamal
Senior IANA Services Specialist

The following Last Call announcement was sent out (ends 2018-12-27):

From: The IESG
To: IETF-Announce
CC: lisp-chairs@ietf.org, lisp@ietf.org, db3546@att.com, Joel Halpern , draft-ietf-lisp-rfc8113bis@ietf.org, jmh@joelhalpern.com
Reply-To: ietf@ietf.org
Sender:
Subject: Last Call:  (Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations) to Proposed Standard


The IESG has received a request from the Locator/ID Separation Protocol WG
(lisp) to consider the following document: - 'Locator/ID Separation Protocol
(LISP): Shared Extension Message & IANA
  Registry for Packet Type Allocations'
  as Proposed Standard

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
ietf@ietf.org mailing lists by 2018-12-27. Exceptionally, comments may be
sent to iesg@ietf.org instead. In either case, please retain the beginning of
the Subject line to allow automated sorting.

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.

  This document updates I-D.ietf-lisp-rfc6833bis.




The file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc8113bis/

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc8113bis/ballot/


No IPR declarations have been submitted directly on this I-D.

Locator/ID Separation Protocol (LISP): Shared Extension Message & IANA Registry for Packet Type Allocations (https://tools.ietf.org/html/draft-ietf-lisp-rfc8113bis-01) updates RFC 8113 which specifies and extension mechanism for LISP Packet Types and Defines the Registry for those Packet Types.

The Document Shepherd is Joel Halpern, one of the WG co-chairs.  The responsible Area Director is Deborah Brungard.  This writeup is in support of publishing this document as a Proposed Standard RFC

The primary reason for producing this document is that this is a standards track registry so as to avoid the need for downrefs in all documents that reference the registry.  There are some minor additional cleanups noted in the document.

This document was produced at the request of the LISP WG chairs.  It was reviewed and accepted by the working group both as a call for adoption and as a working group last call.  There was support for the document, and no dissent.

The document shepherd has confirmed that the authors have disclosed all known relevant IPR (there are no IPR disclosures against this document.)