IETF Logo Mail Archive

Re: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion

Nick Hilliard <nick@foobar.org> Tue, 23 February 2021 13:19 UTC

Return-Path: <nick@foobar.org>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D95CF3A2AB5 for <v6ops@ietfa.amsl.com>; Tue, 23 Feb 2021 05:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 wLUlE4Yx8YfJ for <v6ops@ietfa.amsl.com>; Tue, 23 Feb 2021 05:19:30 -0800 (PST)
Received: from mail.netability.ie (mail.netability.ie [IPv6:2a03:8900:0:100::5]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2A1973A2A4F for <v6ops@ietf.org>; Tue, 23 Feb 2021 05:19:29 -0800 (PST)
X-Envelope-To: v6ops@ietf.org
Received: from crumpet.local (admin.ibn.ie [46.182.8.8]) (authenticated bits=0) by mail.netability.ie (8.16.1/8.16.1) with ESMTPSA id 11NDJDbG050531 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 23 Feb 2021 13:19:14 GMT (envelope-from nick@foobar.org)
X-Authentication-Warning: cheesecake.ibn.ie: Host admin.ibn.ie [46.182.8.8] claimed to be crumpet.local
To: Alexandre Petrescu <alexandre.petrescu@gmail.com>
Cc: Paolo Volpato <paolo.volpato@huawei.com>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <d5835971a5bb429abf8cf740a824e67d@huawei.com> <26f11d42-c35c-bcc6-10a3-99b5b343f70d@gmail.com> <e9846f6259004a5d98a1eac1a61da3a1@huawei.com> <ab16a40c-2618-680f-1943-f3e03faec295@gmail.com>
From: Nick Hilliard <nick@foobar.org>
Message-ID: <02db75ee-0fbf-5aa2-ec95-d37d660658c0@foobar.org>
Date: Tue, 23 Feb 2021 13:19:12 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.16; rv:52.0) Gecko/20100101 PostboxApp/7.0.46
MIME-Version: 1.0
In-Reply-To: <ab16a40c-2618-680f-1943-f3e03faec295@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/v6ops/3P-eNpSFvxxSri9Jrq9GJTzFeLU>
Subject: Re: [v6ops] Update of draft-vf-v6ops-ipv6-deployment and IPv4 exhaustion
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Feb 2021 13:19:33 -0000

Alexandre Petrescu wrote on 23/02/2021 12:19:
> In that sense, maybe there is a rule at RIRs that mandate the ISPs that 
> received IPv4 blocks to actually use them right away?  Or are RIRs 
> allowing ISPs to not use the IP blocks immediately?

bear in mind that RIRs are registries, not behavioral enforcement agencies.

Nick

v2.23.0 | Report a Bug | By Email