IETF Logo Mail Archive

Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC

Dino Farinacci <farinacci@gmail.com> Thu, 15 November 2012 18:26 UTC

Return-Path: <farinacci@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 76A3421F8467; Thu, 15 Nov 2012 10:26:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.449
X-Spam-Level:
X-Spam-Status: No, score=-3.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A01A0wl7kCYF; Thu, 15 Nov 2012 10:26:04 -0800 (PST)
Received: from mail-pa0-f44.google.com (mail-pa0-f44.google.com [209.85.220.44]) by ietfa.amsl.com (Postfix) with ESMTP id 3E9A721F8428; Thu, 15 Nov 2012 10:26:04 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1278033pad.31 for <multiple recipients>; Thu, 15 Nov 2012 10:25:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; bh=rf0IPjmMHLRM/S6zNnDAfmV7Ac+E30fN0kMcL0M4x5Q=; b=OWnr3Q2V7EdpVXUmtmM/7OmssLBUdqLOFPYpPaLvOzdoJusvN9fB6VJ/9keyjNomCU FNlzbLb4GL02afObRaVnSgooNH/X0z4P6xuTNbU19KyMO+t50wAtd2cyFJXHpA2NzpbD jTTGOrKNFHPIzp6jcHKB6WxaltgwrnkXHsB5mgRZQ1JobI4WoGKDY0pY5ViYa2ursCWI +JMoe+/GduNyGoFaZC8nUMQq1WTHZQN8AoN1A/oeRsGP/j4YNV0uGwaA1Lrh6+bOGCy4 i1gwn+I/yXqPymc21iPvQDzCbBocxC7Z5R9I+DgtXjDyfp9cxvw42Lm/Le+XG7/ji6OO /TQg==
Received: by 10.66.73.102 with SMTP id k6mr5610000pav.22.1353003959927; Thu, 15 Nov 2012 10:25:59 -0800 (PST)
Received: from sjc-vpn5-1054.cisco.com (128-107-239-233.cisco.com. [128.107.239.233]) by mx.google.com with ESMTPS id g10sm10091212pav.9.2012.11.15.10.25.56 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 10:25:58 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <50A530E7.8@lacnic.net>
Date: Thu, 15 Nov 2012 10:25:56 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com>
References: <20121113144545.12836.71935.idtracker@ietfa.amsl.com> <CAKFn1SFy2+hXJLVtEpkdXfNuXA31ybmYnBFFPXj-73kb3tD+yw@mail.gmail.com> <5FCB8A98-4984-427C-9468-1DFDEBD206FD@steffann.nl> <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net> <50A530E7.8@lacnic.net>
To: Arturo Servin <aservin@lacnic.net>
X-Mailer: Apple Mail (2.1499)
X-Mailman-Approved-At: Fri, 16 Nov 2012 08:43:07 -0800
Cc: lisp@ietf.org, ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 18:26:06 -0000

> Luigi,
> 
> On 15/11/2012 12:33, Luigi Iannone wrote:
>> 
>> On 15 Nov. 2012, at 10:43 , Sander Steffann <sander@steffann.nl> wrote:
>> 
>>> Hi,
>>> 
>>>> I have to ask, who can request an netblock from this address space and
>>>> from where?
>>>> I might be blind but I couldn't find it mentioned anywhere.
>>> 
>>> Good question. Will there be a central registry, or will parts of the space be delegated to i.e. LISP based ISPs?
>>> 
>> 
>> Hi Sander,
>> 
>> no central registry has been ever discussed, was more about delegated the space to LISP ISPs.
> 
> 
> 	How are you going to allocate space to ISPs?

This is PI space. The registries will take portions of this space to allocate to end devices.  This is endpoint ID space. ISPs will continue to allocate addresses for LISP RLOCs. And they will have to allocate orders of magnitude less address space now.

> 	Who is going to track the allocations made to ISPs, how are they going
> to be published, what are the requirements to ask for space, what data
> needs to be registered, where I can see allocations data?

Registries will track allocations to end sites.

> 	You asked George why the document is not ready to be published. Well,
> the undocumented rules on how the space is going to be managed is one
> important reason IMHO.

This draft is purely a draft to REQUEST space. There will need to be a deployment guide on how to allocate EIDs, in general.

Dino

> 
> Regards,
> as
> 	
> 
>> 
>> Luigi
>> 
>> 
>>> - Sander
>>> 
>>> _______________________________________________
>>> lisp mailing list
>>> lisp@ietf.org
>>> https://www.ietf.org/mailman/listinfo/lisp
>> 
>> _______________________________________________
>> lisp mailing list
>> lisp@ietf.org
>> https://www.ietf.org/mailman/listinfo/lisp
>> 
> _______________________________________________
> lisp mailing list
> lisp@ietf.org
> https://www.ietf.org/mailman/listinfo/lisp

v2.23.0 | Report a Bug | By Email