IETF Logo Mail Archive

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

Dino Farinacci <farinacci@gmail.com> Thu, 01 August 2019 18:38 UTC

Return-Path: <farinacci@gmail.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 842371201E3 for <lisp@ietfa.amsl.com>; Thu, 1 Aug 2019 11:38:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level:
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HbdYEHh9va8S for <lisp@ietfa.amsl.com>; Thu, 1 Aug 2019 11:38:49 -0700 (PDT)
Received: from mail-pg1-x531.google.com (mail-pg1-x531.google.com [IPv6:2607:f8b0:4864:20::531]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C06C01201CC for <lisp@ietf.org>; Thu, 1 Aug 2019 11:38:41 -0700 (PDT)
Received: by mail-pg1-x531.google.com with SMTP id u17so34684026pgi.6 for <lisp@ietf.org>; Thu, 01 Aug 2019 11:38:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xU5FG5BIdj9nvYdX4yCr+QDa95z6PjjQC3dmRumT5dI=; b=X6T3giXVLa7u4Ix5AUdSRQKKQaWS5e457y2NYzonpxOwFYID55LaWpAu92gqOVdfNv 0QLBgaZddeaiX/7dZVX+3HwRnwIL/qWM3Jt5cESNY7LGkjmoQEElllG8Mu0cfwSmupD/ d8tUs8eBWZBLUKQAszEAXTif6Yl9/HJRHV8UhkGZeu6oQUrSUremeNOGx0cgUk/8pwc9 AsNU5sJYtqJzD+GjLb/aDI6LuHlDgOTurqhkrjfcZhjTJLECwxEhEgSKY4D5zwjBg99T Gn8uo/W6h+bDsfJnMT1t9fqxzXLjHt31Uhvibrt7Q3JhvcxzViVW/tMQbVLcODFb71ae E15w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=xU5FG5BIdj9nvYdX4yCr+QDa95z6PjjQC3dmRumT5dI=; b=gv2oKGujvlorPXmlsMhTjp7Dbv+vwH2Jp4/RyeLvt7FIfaQok5QhUpU9kgjgCO/Avp +iwoPCRTsaee5L7v0f8py441L6NgolmKpLl13nCaZDKVLuKBoNIjAc/n/Hkw4BpCrfjZ UKQ0IpWcjcRewhuNjalivT5NNm+36F3HrZsqQSE897eeaVyciTbfGZ+ePD8C8rJ6d1x4 +lizMahMZo9EiSRUgzB9M6HszPbgdDo4qmikJyziq2cTffMZ4FwZBi4aJp7npbpXpBbs w9elwwXL0d/SVFnROgf9RSytcL+gp9kW4i08ddhmkGkO2DzlJDyIVbiz4v+WyuttlKFo bIDQ==
X-Gm-Message-State: APjAAAVROxGvZqIydtcx3n2Ut+1hD5EjEzRdeTeNSkSpnM61R0yoCU5U K3KpkywzfYiwpi8Ss+0s0s8=
X-Google-Smtp-Source: APXvYqym4q/dnzArd08cXolrulMBceejwPcqZ8M7NpOS3OheL9Phif2yophr3/XaR0szd2avKO74cg==
X-Received: by 2002:a62:1c5:: with SMTP id 188mr52944695pfb.26.1564684721243; Thu, 01 Aug 2019 11:38:41 -0700 (PDT)
Received: from [10.97.50.122] ([96.72.181.209]) by smtp.gmail.com with ESMTPSA id n98sm5441679pjc.26.2019.08.01.11.38.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Aug 2019 11:38:38 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
From: Dino Farinacci <farinacci@gmail.com>
In-Reply-To: <97c6dce6-ae82-9706-743d-519fcd00c837@joelhalpern.com>
Date: Thu, 01 Aug 2019 11:38:38 -0700
Cc: "lisp@ietf.org list" <lisp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <62350D10-4641-4DB9-8FEE-065ACF0A160D@gmail.com>
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>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.9.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/lisp/_LXEx2MuszuAFJyVGhFnMFZS1EA>
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:38:53 -0000

> 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

v2.23.0 | Report a Bug | By Email