[lisp] Last Call: <draft-ietf-lisp-impact-04.txt> (LISP Impact) to Informational RFC
The IESG <iesg-secretary@ietf.org> Mon, 05 October 2015 20:23 UTC
Return-Path: <iesg-secretary@ietf.org>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 091B91B4FB8; Mon, 5 Oct 2015 13:23:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.9
X-Spam-Level:
X-Spam-Status: No, score=-101.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dgjMsmAH59UJ; Mon, 5 Oct 2015 13:23:10 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id B701E1B4FAF; Mon, 5 Oct 2015 13:23:10 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
X-Test-IDTracker: no
X-IETF-IDTracker: 6.4.1
Auto-Submitted: auto-generated
Precedence: bulk
Sender: iesg-secretary@ietf.org
Message-ID: <20151005202310.30395.33813.idtracker@ietfa.amsl.com>
Date: Mon, 05 Oct 2015 13:23:10 -0700
Archived-At: <http://mailarchive.ietf.org/arch/msg/lisp/pMpxJHt-VUjLoLmG_tNrJrc9SE4>
Cc: lisp@ietf.org
Subject: [lisp] Last Call: <draft-ietf-lisp-impact-04.txt> (LISP Impact) to Informational RFC
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: List for the discussion of the Locator/ID Separation Protocol <lisp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lisp>, <mailto:lisp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/lisp/>
List-Post: <mailto:lisp@ietf.org>
List-Help: <mailto:lisp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lisp>, <mailto:lisp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 05 Oct 2015 20:23:12 -0000
The IESG has received a request from the Locator/ID Separation Protocol WG (lisp) to consider the following document: - 'LISP Impact' <draft-ietf-lisp-impact-04.txt> as Informational RFC 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 2015-10-19. 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 The Locator/Identifier Separation Protocol (LISP) aims at improving the Internet routing scalability properties by leveraging on three principles: address role separation, encapsulation, and mapping. In this document, based on implementation work, deployment experiences, and theoretical studies, we discuss the impact that the deployment of LISP can have on both the routing infrastructure and the end-user. The file can be obtained via https://datatracker.ietf.org/doc/draft-ietf-lisp-impact/ IESG discussion can be tracked via https://datatracker.ietf.org/doc/draft-ietf-lisp-impact/ballot/ No IPR declarations have been submitted directly on this I-D.