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

The IESG <iesg-secretary@ietf.org> Fri, 17 August 2018 15:17 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, lisp@ietf.org, db3546@att.com, Luigi Iannone <ggx@gigix.net>, ggx@gigix.net, draft-ietf-lisp-rfc6833bis@ietf.org
Reply-To: ietf@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Reply-To: ietf@ietf.org
Message-ID: <153451906473.18078.3298934607001431350.idtracker@ietfa.amsl.com>
Date: Fri, 17 Aug 2018 08:17:44 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/U1c5DfzRK0GSh8Gn5C1KOHivmic>
Subject: [lisp] Last Call: <draft-ietf-lisp-rfc6833bis-12.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-12.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
ietf@ietf.org mailing lists by 2018-08-31. 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 describes the Control-Plane and Mapping Service for the
   Locator/ID Separation Protocol (LISP), implemented by two new 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, connect directly to LISP-capable
   Internet end sites, and comprising the bulk of LISP-speaking devices,
   reducing their implementation and operational complexity should also
   reduce the overall cost and effort of deploying LISP.

   This document obsoletes RFC 6833.




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

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


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-12.… The IESG