Re: [v6ops] Revised Internet Drafts for allocation of IPv6 space for LISP EIDs

"Joel M. Halpern" <jmh@joelhalpern.com> Fri, 25 October 2013 14:02 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 946D111E8316 for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2013 07:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.356
X-Spam-Level:
X-Spam-Status: No, score=-102.356 tagged_above=-999 required=5 tests=[AWL=-0.357, BAYES_00=-2.599, J_CHICKENPOX_13=0.6, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RzuziL8Kk8gC for <v6ops@ietfa.amsl.com>; Fri, 25 Oct 2013 07:02:40 -0700 (PDT)
Received: from mailc2.tigertech.net (mailc2.tigertech.net [208.80.4.156]) by ietfa.amsl.com (Postfix) with ESMTP id 1705611E83DB for <v6ops@ietf.org>; Fri, 25 Oct 2013 07:02:38 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mailc2.tigertech.net (Postfix) with ESMTP id F20287C; Fri, 25 Oct 2013 07:02:37 -0700 (PDT)
X-Virus-Scanned: Debian amavisd-new at c2.tigertech.net
Received: from Joels-MacBook-Pro.local (c213-89-137-101.bredband.comhem.se [213.89.137.101]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mailc2.tigertech.net (Postfix) with ESMTPSA id 130797B; Fri, 25 Oct 2013 07:02:36 -0700 (PDT)
Message-ID: <526A79FB.8010101@joelhalpern.com>
Date: Fri, 25 Oct 2013 10:02:35 -0400
From: "Joel M. Halpern" <jmh@joelhalpern.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: Lorenzo Colitti <lorenzo@google.com>
References: <28CFF7E5-E98E-4D97-B7F4-3A18C255253C@gigix.net> <D62C71FC-306F-4F91-97E2-84D6F64A58A3@istaff.org> <5267E96B.1000802@innovationslab.net> <20131023152549.GN50205@Space.Net> <5267EB60.7080105@innovationslab.net> <CAKD1Yr1SpS0e3qDkZyRsiSB-a_oXCi7nWKe2szxW34mJfhJnxw@mail.gmail.com> <5267ED12.4090602@innovationslab.net> <CAKD1Yr0CixObNWW=CuZgXfF4WUXKK0u+8jw8DdF4M9n6s6ZRcQ@mail.gmail.com>
In-Reply-To: <CAKD1Yr0CixObNWW=CuZgXfF4WUXKK0u+8jw8DdF4M9n6s6ZRcQ@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: "v6ops@ietf.org WG" <v6ops@ietf.org>
Subject: Re: [v6ops] Revised Internet Drafts for allocation of IPv6 space for LISP EIDs
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/v6ops>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 Oct 2013 14:02:44 -0000

Arguably, LISP creates a separate (overlayed) connectivity infrastructure.
It should not come as a great surprise that such an infrastructure uses 
(one way or another) an effectively separate address registry for its 
separate operation.

Having said that, leaks and how they relate to the allocation is one of 
the questions I asked the WG to clarify about this document.  It is 
currently unclear on the point, and that is not going to work for any of us.

Yours,
Joel

On 10/23/13 12:11 PM, Lorenzo Colitti wrote:
> On Thu, Oct 24, 2013 at 12:36 AM, Brian Haberman
> <brian@innovationslab.net <mailto:brian@innovationslab.net>> wrote:
>
>     Keep in mind that the referenced draft went through IETF Last
>     Call and was subsequently sent back to the WG due to the concerns
>     raised about routing and potentially creating a parallel address
>     registry
>     outside of the RIRs.
>
>
> Which it's still doing, right? The block-mgmnt draft is all about
> creating a parallel address registry.
>
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>