lispers.net LISP NAT-Traversal Implementation Report
draft-farinacci-lisp-lispers-net-nat-12

(Via drafts-eval@iana.org): IESG/Authors/ISE:

The IANA Functions Operator has completed its review of draft-farinacci-lisp-lispers-net-nat-07. If any part of this review is inaccurate, please let us know.

We understand that when this document is sent to us for processing, we will perform the following action:

The following entry will be added to the "LISP Control Plane Header Bits: Map-Request" registry:

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

Spec Name: N
IANA Name: map-request-N
BIT Position: 16
Description: NAT-Traversal Bit
Reference: this document

As this document requests registrations in a Specification Required (see RFC 8126) registry, we have initiated the required Expert Review via a separate request. This review must be completed before the document's IANA state can be changed to "IANA OK."

For definitions of IANA review states, please see:

https://datatracker.ietf.org/help/state/draft/iana-review

Thank you,

Sabrina Tanamal
Lead IANA Services Specialist

draft-farinacci-lisp-lispers-net-nat-06 has been presented to the ISE for
publication as an Informational RFC on the Independent Stream.

==Purpose==

This draft specifies the LISPERS.NET implementation of LISP with NAT
traversal.

== History==

See Section 1 of the memo.  There is a lengthy history of this work
which has been bouncing around since 2014.  It has gone through some
evolution recently to make use of an RLOC-name
[draft-ietf-lisp-name-encoding].  This is intended to address the code
squatting issue we discussed in Prague.

The hope was that draft-ermagen-lisp-nat-traversal would progress, but
thus far it has not done so.  The ISE is aware that NAT traversal is
within the charter of the LISP group, but he is not aware of any
active drafts.

For this draft, if there are IESG concerns about publshing, the ISE
would ask if there are specific textual changes that would ameliorate
those concerns.

==Non-IETF Work==

The LISPERS.NET implementation is non-IETF work.

==Security Considerations==

See Section 11 of the memo.

==IANA==

The document makes no request for IANA action.

==Reviews==

This document was reviewed in detail by Luigi Ianonne and Joel
Halpern.