IETF Logo Mail Archive

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

Arturo Servin <aservin@lacnic.net> Thu, 15 November 2012 18:14 UTC

Return-Path: <aservin@lacnic.net>
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 11C0921F88A9; Thu, 15 Nov 2012 10:14:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.434
X-Spam-Level:
X-Spam-Status: No, score=-2.434 tagged_above=-999 required=5 tests=[AWL=0.166, BAYES_00=-2.599, NO_RELAYS=-0.001]
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 WY-r4PdfO3ql; Thu, 15 Nov 2012 10:14:06 -0800 (PST)
Received: from mail.lacnic.net.uy (mail.lacnic.net.uy [IPv6:2001:13c7:7001:4000::3]) by ietfa.amsl.com (Postfix) with ESMTP id 6E63821F888E; Thu, 15 Nov 2012 10:14:06 -0800 (PST)
Received: from 85-7-200.lacnic.net.uy (unknown [IPv6:2001:13c7:7001:5128:39f7:daf:f8fc:e39d]) by mail.lacnic.net.uy (Postfix) with ESMTP id 26C5530841C; Thu, 15 Nov 2012 16:14:01 -0200 (UYST)
Message-ID: <50A530E7.8@lacnic.net>
Date: Thu, 15 Nov 2012 16:13:59 -0200
From: Arturo Servin <aservin@lacnic.net>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: lisp@ietf.org
Subject: Re: [lisp] Last Call: <draft-ietf-lisp-eid-block-03.txt> (LISP EID Block) to Informational RFC
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>
In-Reply-To: <87676878-B077-4B4C-96DC-9F755F78018A@gigix.net>
X-Enigmail-Version: 1.4.5
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-LACNIC.uy-MailScanner-Information: Please contact the ISP for more information
X-LACNIC.uy-MailScanner: Found to be clean
X-LACNIC.uy-MailScanner-SpamCheck:
X-LACNIC.uy-MailScanner-From: aservin@lacnic.net
Cc: 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:14:07 -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?

	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?

	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.

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
>

v2.23.0 | Report a Bug | By Email