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 19:27 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 B5B0C21F892B; Thu, 15 Nov 2012 11:27:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.599
X-Spam-Level:
X-Spam-Status: No, score=-3.599 tagged_above=-999 required=5 tests=[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 E5RmVd2Cn-xh; Thu, 15 Nov 2012 11:27:24 -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 1E3A721F8487; Thu, 15 Nov 2012 11:27:24 -0800 (PST)
Received: by mail-pa0-f44.google.com with SMTP id fb11so1316534pad.31 for <multiple recipients>; Thu, 15 Nov 2012 11:27:23 -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=f7gX3VV3hpum0JQntxgjbd/BUjqCnR1htVY0RGxJxgo=; b=HGzbpjWsIQ+NHgNap/EhH5PpMhokdVs2j5ti9ov6/n+aPFDz4bCMLKiZnXaIpaXr3d 1NB/dsGMtz0rfTwL1GVclMDZA1gqr+l3RuB+5G17co6Hog1Kbk8jzsAqXv0RdRX5KX4b ZYkx4B0hAnL0/0+Dl4eZ4aARNUDNLNN4njteuXxwJf6R3SC5x6Uot3U44GfkoV+rsXpp /rsAhiqTrlKGZLc2CGmY59rKY7MmMQ7yqwCrEQwYC9gNNWh5kbL/xlBp5/5jwYlkrpI8 7kBJFbC7duxIrD5z69dKfwpc+Q2ZKg8v40tBy4xpz398xtT5BNe9qJxTQX2x1YrzVpp6 v4Vw==
Received: by 10.66.88.133 with SMTP id bg5mr5830092pab.80.1353007643819; Thu, 15 Nov 2012 11:27:23 -0800 (PST)
Received: from [192.168.1.4] (173-8-188-29-SFBA.hfc.comcastbusiness.net. [173.8.188.29]) by mx.google.com with ESMTPS id ph7sm9937211pbb.9.2012.11.15.11.27.21 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 11:27:23 -0800 (PST)
Content-Type: text/plain; charset="iso-8859-1"
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: <50A538B8.7080709@lacnic.net>
Date: Thu, 15 Nov 2012 11:27:21 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <D1AD4093-C3F7-4A35-8108-3E16639E5991@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> <B8132154-7260-43B4-B10D-E5B95924A15D@gmail.com> <50A538B8.7080709@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 19:27:24 -0000

> Dino,
> 
> 	But who are the registries? The RIRs? Large ISPs? IANA? I think you
> should specify clearly either: what a registry is or that is not defined
> yet.

Yes, nothing has to change in terms of who and how PI addresses are allocated.

> 	Point taken on "This draft is purely a draft to REQUEST space. There
> will need to be a deployment guide on how to allocate EIDs, in general."
> But then it should be written somewhere in the document.

I agree the wording in the abstract and introduction should be a bit stronger and/or more direct.

> 	Although it could be enough only to clearly say that a deployment guide
> would define allocation guides in the future; for the sake of clarity
> and usefulness (now, after the space is allocated by IANA it will be
> there left unused because there is not a clearly indication how is going
> to be used) I would recommend to discuss how the space is going to be
> allocated.

Sure, good comment.

Dino

> 
> Regards
> as
> 
> 	
> On 15/11/2012 16:25, Dino Farinacci wrote:
>>> 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