Re: [lisp] Fwd: #202719 - Re: LISP EID prefix 2001:5:3::/48

"Joel M. Halpern" <jmh@joelhalpern.com> Thu, 01 August 2019 18:41 UTC

Return-Path: <jmh@joelhalpern.com>
X-Original-To: lisp@ietfa.amsl.com
Delivered-To: lisp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 407291200E5 for <lisp@ietfa.amsl.com>; Thu, 1 Aug 2019 11:41:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=joelhalpern.com
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 jBfy4jzUgb37 for <lisp@ietfa.amsl.com>; Thu, 1 Aug 2019 11:41:01 -0700 (PDT)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0BB812013D for <lisp@ietf.org>; Thu, 1 Aug 2019 11:41:00 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 45zzdS6G2tz1V4Vh; Thu, 1 Aug 2019 11:41:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1564684860; bh=mnVb2A6UXJrPnv7wtoaWCKgH5raKBjyj3T4kXBltbgI=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=aTQZW3wbpjsEgE2EZSmGNKX//S6kpybfn+Ujqjdi+2/xEW95WUmdwpBfIdrihuFOx OdNOEpWrcDVHI20q9Y51bPKbyImRy9AaFkMra31SqlUveWyNy+/yChg1jDOjo7EvRj ivy1DnSznh+mABPakf7TUUshsTYGbDmofiydoLYY=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [172.20.7.244] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 45zzdS2MPmz1V4VQ; Thu, 1 Aug 2019 11:41:00 -0700 (PDT)
To: Dino Farinacci <farinacci@gmail.com>
Cc: "lisp@ietf.org list" <lisp@ietf.org>
References: <PMZV6QQO6Q_5d42d66523a09_980c3f7f75ebcf24284095_sprut@zendesk.com> <547CDFBA-E4CB-4422-890C-A8CC895C0F62@gmail.com> <7193daf7-8c2f-31f9-14b5-e8548e9330ec@joelhalpern.com> <CCA2E6B2-141C-49FA-A5E9-482307F0420B@gmail.com> <97c6dce6-ae82-9706-743d-519fcd00c837@joelhalpern.com> <62350D10-4641-4DB9-8FEE-065ACF0A160D@gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <b5d32bdc-e065-ae08-6c1c-c1a94bc0eac0@joelhalpern.com>
Date: Thu, 01 Aug 2019 14:40:56 -0400
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <62350D10-4641-4DB9-8FEE-065ACF0A160D@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/0aL58uAiQFN4ThReL2jtkTNuuXE>
Subject: Re: [lisp] Fwd: #202719 - Re: LISP EID prefix 2001:5:3::/48
X-BeenThere: lisp@ietf.org
X-Mailman-Version: 2.1.29
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: <https://mailarchive.ietf.org/arch/browse/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: Thu, 01 Aug 2019 18:41:03 -0000

We asked for an experiment.  As such, we need to re-evaluate the experiment.
You said "I am using it".   As I said, I presume that is a 
mis-statement.  Who is using EIDs from that block?  What are they being 
used for?  Is having a block actually helpful?

In particular, given that our focus as a working group has moved away 
from Internet-Wide deployments of LISP to more specialized use cases, it 
is not at all clear that the PS-to-be documents warrant the allocation.

Yours,
Joel

On 8/1/2019 2:38 PM, Dino Farinacci wrote:
>> If only one person is using the block after all this time, then yes, we as a working group want RIPE to stop allocating experimental EIDs.
> 
> You are missing the point Joel. There are many sub-blocks allocated from the experimental block from RFC 7955. I am not the only sub-block.
> 
>> If there is significant usage, then we should understand what it is and why.
> 
> What if there is *any* usage for any subblock?
> 
> Dino
> 
>>
>> Yours,
>> Joel
>>
>> On 8/1/2019 2:33 PM, Dino Farinacci wrote:
>>> No, its not about me. RIPE wants to stop allocating experimental EID blocks. Do we, the LISP WG, want that to happen?
>>> Dino
>>>> On Aug 1, 2019, at 10:46 AM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>>>>
>>>> I am presuming your phrasing is slightly misleading.  If you individually are the only user of the block, I do not see how we can justify asking RIPE to continue the assignment.
>>>>
>>>> Yours,
>>>> Joel
>>>>
>>>> On 8/1/2019 1:00 PM, Dino Farinacci wrote:
>>>>> I am still using this block but RIPE wants to remove it per IETF recommendations. Should we update RFC 7955 to indicate the “experiment” is still continuing?
>>>>> Dino
>>>>>> Begin forwarded message:
>>>>>>
>>>>>> *From: *RIPE NCC Support <support@ripe.net <mailto:support@ripe.net>>
>>>>>> *Subject: **#202719 - Re: LISP EID prefix 2001:5:3::/48*
>>>>>> *Date: *August 1, 2019 at 5:09:09 AM PDT
>>>>>> *To: *farinacci <farinacci@gmail.com <mailto:farinacci@gmail.com>>
>>>>>> *Reply-To: *RIPE NCC Support <support@ripe.net <mailto:support@ripe.net>>
>>>>>>
>>>>>> ##- Please type your reply above this line -##
>>>>>>
>>>>>> Ticket (202719) has been updated. To add additional comments, reply to this email.
>>>>>>
>>>>>> *Mike Petrusha*(RIPE NCC Support)
>>>>>>
>>>>>> Aug 1, 14:09 CEST
>>>>>>
>>>>>> Dear Colleagues,
>>>>>>
>>>>>> The RIPE NCC have assigned LISP EID prefix 2001:5:3::/48 tolispers.net <http://lispers.net/>on 2016-11-16.
>>>>>>
>>>>>> The assigned prefix will be removed on 31 August 2019.
>>>>>>
>>>>>> According to RFC 7955,https://tools.ietf.org/html/rfc7955
>>>>>> "According to the 3+3 year experimentation plan, defined in
>>>>>> [RFC 7954  <https://tools.ietf.org/html/rfc7954>], all registrations MUST end by August 2019, unless
>>>>>> the IETF community decides to grant a permanent LISP EID
>>>>>> address block."
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Sincerely,
>>>>>>
>>>>>> Mike Petrusha
>>>>>> RIPE NCC
>>>>>>
>>>>>>
>>>>>> This email is a service from RIPE NCC Support.
>>>>>> [PMZV6Q-QO6Q]
>>>>> _______________________________________________
>>>>> lisp mailing list
>>>>> lisp@ietf.org
>>>>> https://www.ietf.org/mailman/listinfo/lisp
>