[lisp] Last Call: <draft-ietf-lisp-rfc6830bis-14.txt> (The Locator/ID Separation Protocol (LISP)) to Proposed Standard

The IESG <iesg-secretary@ietf.org> Wed, 15 August 2018 17:29 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, Luigi Iannone <ggx@gigix.net>, ggx@gigix.net, lisp@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: <153435419816.14388.8449951694289375416.idtracker@ietfa.amsl.com>
Date: Wed, 15 Aug 2018 10:29:58 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/3qmLMDe40RW7tE9-Av9AXvHNum0>
Subject: [lisp] Last Call: <draft-ietf-lisp-rfc6830bis-14.txt> (The Locator/ID Separation Protocol (LISP)) to Proposed Standard

The IESG has received a request from the Locator/ID Separation Protocol WG
(lisp) to consider the following document: - 'The Locator/ID Separation
Protocol (LISP)'
<draft-ietf-lisp-rfc6830bis-14.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-29. 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 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.

LISP requires no change to either host protocol stacks or to underlay
routers and offers Traffic Engineering, multihoming and mobility,
among other features.

This document obsoletes RFC 6830.

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

IESG discussion can be tracked via
https://datatracker.ietf.org/doc/draft-ietf-lisp-rfc6830bis/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-rfc6830bis-14.… The IESG