Re: [lisp] I-D Action: draft-ietf-lisp-eid-block-mgmnt-01.txt

Geoff Huston <gih@apnic.net> Fri, 21 February 2014 09:29 UTC

Return-Path: <gih@apnic.net>
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 694C31A003B for <lisp@ietfa.amsl.com>; Fri, 21 Feb 2014 01:29:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.339
X-Spam-Level:
X-Spam-Status: No, score=-102.339 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.548, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, 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 C0y4X4fhQXsN for <lisp@ietfa.amsl.com>; Fri, 21 Feb 2014 01:29:40 -0800 (PST)
Received: from so-mailgw.apnic.net (so-mailgw.apnic.net [IPv6:2001:dd8:a:3::230]) by ietfa.amsl.com (Postfix) with SMTP id A11621A0502 for <lisp@ietf.org>; Fri, 21 Feb 2014 01:29:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apnic.net; s=c3po; h=received:received:content-type:mime-version:subject:from:in-reply-to:date:cc: content-transfer-encoding:message-id:references:to:x-mailer:return-path; bh=Si2FJcaVpUQnY2sGKPrYy5+v8HNoQO8K8f7LEh4hiU8=; b=tz6r1Q2s46bp0sQd9Hdpsd2bZTSr6l75Un6PfEMogEshLFUpiyTJYW7lATWmUG/sOoTRiKeMIHfY6 n2Mph88AGiqDIKHLR/dCjNo+qHcNfmG7iwiywd1FZE8LsFitvSRxW19+/3JoWmoMxvNeu+UQuClPLf mx7E7aw5NrPSn8zM=
Received: from NXMDA1.org.apnic.net (unknown [203.119.93.247]) by so-mailgw.apnic.net (Halon Mail Gateway) with ESMTP; Fri, 21 Feb 2014 19:29:19 +1000 (EST)
Received: from [10.100.59.173] (203.119.101.249) by NXMDA1.org.apnic.net (203.119.107.11) with Microsoft SMTP Server (TLS) id 14.1.218.12; Fri, 21 Feb 2014 19:29:31 +1000
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Geoff Huston <gih@apnic.net>
In-Reply-To: <20140214163439.8133.81625.idtracker@ietfa.amsl.com>
Date: Fri, 21 Feb 2014 20:29:25 +1100
Content-Transfer-Encoding: quoted-printable
Message-ID: <78447E2F-11A0-4123-85FB-E6801F000D64@apnic.net>
References: <20140214163439.8133.81625.idtracker@ietfa.amsl.com>
To: luigi.iannone@telecom-paristech.fr
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/lisp/D-YsNbNnjh0eL5foQq7J6BrIVEM
Cc: LISP mailing list list <lisp@ietf.org>
Subject: Re: [lisp] I-D Action: draft-ietf-lisp-eid-block-mgmnt-01.txt
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
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: <http://www.ietf.org/mail-archive/web/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: Fri, 21 Feb 2014 09:29:42 -0000

On 15 Feb 2014, at 3:34 am, internet-drafts@ietf.org wrote:

> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Locator/ID Separation Protocol Working Group of the IETF.
> 
>       Title           : LISP EID Block Management Guidelines
>       Authors         : Luigi Iannone
>                         Roger Jorgensen
>                         David Conrad
> 	Filename        : draft-ietf-lisp-eid-block-mgmnt-01.txt
> 	Pages           : 13
> 	Date            : 2014-02-14



section4, bullet 5 states:
      All allocations (renewed or not,
      including delegations and sub-allocations) MUST be returned by 31
      December 2020, in accordance to the 3+3 years plan outlined in
      [I-D.ietf-lisp-eid-block].


but the text at the end of the section reads:

  If/When the EID block experiment changes status (e.g., to not being
  "experimental"), and following the policies outlined in [RFC5226],
  the EID block will change status as well and will be converted to a
  permanent allocation. 


Bullet 5 states "MUST be returned" and the later text states "will be converted to a permanent allocation"

This seems to be a contradiction. What's the intended plan? 

If the permanent plan is that LISP runs from corralled space, then I am seriously concerned that this is an admission of failure of LISP from the outset. I though the object of the exercise was to offer LISP as a routing protocol with superior scaling properties to what we have now. But if this entails renumbering the Internet to achieve it, then just renumbering the Internet so that the address structure aligns with the topology of the network would allow the existing protocols to also scale - so where is the "win" in LISP?

At the very least it would be good for the draft to clarify the directives of must be returned and the conversion to a permanent allocation.

But I would also like to understand the longer term issues at play here - is the longer term plan for LISP to route the Internet's unicast address space as deployed, or are we truly contemplating a lengthy transition into an essentially renumbered space?

Geoff