[lisp] Protocol Action: 'The Locator/ID Separation Protocol (LISP)' to Proposed Standard (draft-ietf-lisp-rfc6830bis-36.txt)

The IESG <iesg-secretary@ietf.org> Thu, 11 February 2021 20:26 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
Cc: lisp-chairs@ietf.org, draft-ietf-lisp-rfc6830bis@ietf.org, db3546@att.com, The IESG <iesg@ietf.org>, Luigi Iannone <ggx@gigix.net>, ggx@gigix.net, rfc-editor@rfc-editor.org, lisp@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <161307516211.1403.1794025281733383001@ietfa.amsl.com>
Date: Thu, 11 Feb 2021 12:26:02 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/1yPXHoccHS4k84VY23BZw95sxX8>
Subject: [lisp] Protocol Action: 'The Locator/ID Separation Protocol (LISP)' to Proposed Standard (draft-ietf-lisp-rfc6830bis-36.txt)

The IESG has approved the following document:
- 'The Locator/ID Separation Protocol (LISP)'
  (draft-ietf-lisp-rfc6830bis-36.txt) as Proposed Standard

This document is the product of the Locator/ID Separation Protocol Working
Group.

The IESG contact persons are Alvaro Retana, Martin Vigoureux and Deborah
Brungard.

A URL of this Internet Draft is:
https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/





Technical Summary

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.

Working Group Summary

 The WG has showed support to the document from its first submission as
individual draft and adopted it right away. On the technical side there was
agreement in the WG and little discussion took place, mainly related on including
some features/improvements not present in RFC 6830. On the organization of the
document, more specifically on what to put in the data-plane document and what to
put in the control-plane document there has been quite some discussion. This
document was previously reviewed by the IESG, due to the technical changes
which have been made, it was Last Called again and re-balloted.

Document Quality

There are several independent implementations of the LISP data-plane.

Personnel

   Who is the Document Shepherd for this document?  Luigi Iannone <ggx@gigix.net>
   Who is the Responsible Area Director? Deborah Brungard <db3546@att.com>

[lisp] Protocol Action: 'The Locator/ID Separatio… The IESG