[lisp] Last Call: <draft-ietf-lisp-rfc6833bis-27.txt> (Locator/ID Separation Protocol (LISP) Control-Plane) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Thu, 04 June 2020 20:34 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: db3546@att.com, lisp-chairs@ietf.org, Luigi Iannone <ggx@gigix.net>, draft-ietf-lisp-rfc6833bis@ietf.org, lisp@ietf.org, ggx@gigix.net
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <159130284379.4585.8783946586699870805@ietfa.amsl.com>
Date: Thu, 04 Jun 2020 13:34:04 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/Cd9SHcpC0Xk_O1NGHkOVzUZXgKU>
Subject: [lisp] Last Call: <draft-ietf-lisp-rfc6833bis-27.txt> (Locator/ID Separation Protocol (LISP) Control-Plane) 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) Control-Plane'
<draft-ietf-lisp-rfc6833bis-27.txt> 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
last-call@ietf.org mailing lists by 2020-06-18. 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. Note, this is a 2nd IETF Last
Call due to technical changes during IESG review.

Abstract

This document describes the Control-Plane and Mapping Service for the
Locator/ID Separation Protocol (LISP), implemented by two types of
LISP-speaking devices -- the LISP Map-Resolver and LISP Map-Server --
that provides a simplified "front end" for one or more Endpoint ID to
Routing Locator mapping databases.

By using this Control-Plane service interface and communicating with
Map-Resolvers and Map-Servers, LISP Ingress Tunnel Routers (ITRs) and
Egress Tunnel Routers (ETRs) are not dependent on the details of
mapping database systems, which facilitates modularity with different
database designs. Since these devices implement the "edge" of the
LISP Control-Plane infrastructure, connecting EID addressable nodes
of a LISP site, their implementation and operational complexity
reduces the overall cost and effort of deploying LISP.

This document obsoletes RFC 6830 and RFC 6833.

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

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

The document contains these normative downward references.
See RFC 3967 for additional information:
draft-ietf-lisp-6834bis: Locator/ID Separation Protocol (LISP) Map-Versioning (None - IETF stream)

[lisp] Last Call: <draft-ietf-lisp-rfc6833bis-27.… The IESG