Re: [v6ops] Chair decision on WGLC for draft-ietf-v6ops-dhcp-pd-per-device-04

Martin Huněk <martin.hunek@tul.cz> Sun, 05 November 2023 23:27 UTC

Return-Path: <martin.hunek@tul.cz>
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 79047C17C539; Sun, 5 Nov 2023 15:27:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.107
X-Spam-Level:
X-Spam-Status: No, score=-2.107 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tul.cz
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m0Ne_W1HBwnP; Sun, 5 Nov 2023 15:27:38 -0800 (PST)
Received: from bubo.tul.cz (bubo.tul.cz [147.230.16.1]) (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 634CDC17C531; Sun, 5 Nov 2023 15:27:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at tul.cz
Received: from asclepius.adm.tul.cz (unknown [147.230.238.39]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by bubo.tul.cz (Postfix) with ESMTPSA id 0C36C18050A13; Mon, 6 Nov 2023 00:27:29 +0100 (CET)
DKIM-Filter: OpenDKIM Filter v2.11.0 bubo.tul.cz 0C36C18050A13
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tul.cz; s=tul2021; t=1699226850; bh=V+6ON7t/Hu44MX6sEvzUEkw+foEzQofTT5zgFZRH9I8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ytX744hcffPV01roaUjMh0vIHY/4W98EnoP57SCBlSuTYKHzGgNNHY8nWPofxhqLe zHImSDXR2ycTpWmw34waArjZQPMMswjYRo+cdc+qlE55OjVZ+lfHGJ+ZjTjmJPzOkE BsPKuAYHcw4AbIL0OyufLTRLpkGMdm2wTqnt0xZoVg2oKJrYGN7I5ZQNc3qjUpr92b g7ieEDbrNdoqT9hX/A6EVOVBRUyTbSnJUQAt6uAtIrWxERayIVyKrIQBG5k1xtHWwz 76T1CxwpCgrXVpBuC04WVpDcoHHXocNnakgulVmSzdmIBabCfBIi9r0lYX2tojLn11 Z+EQjI9pY6aMQ==
From: Martin Huněk <martin.hunek@tul.cz>
To: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Cc: v6ops@ietf.org, V6Ops Chairs <v6ops-chairs@ietf.org>
Date: Mon, 06 Nov 2023 00:27:23 +0100
Message-ID: <3862530.yeFs27NDWt@asclepius.adm.tul.cz>
Organization: Technická univerzita v Liberci
In-Reply-To: <48AD358D-15EE-4728-B5A6-769D35933860@consulintel.es>
References: <e078c90495b54390a3fb4c7bae143b05@huawei.com> <ZUfi_ZXN4jxDIWty@Space.Net> <48AD358D-15EE-4728-B5A6-769D35933860@consulintel.es>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart21969509.huCnfhLgOn"; micalg="sha384"; protocol="application/pkcs7-signature"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/XTF-rFw9lC6VqKVb1Bo5u80dY78>
Subject: Re: [v6ops] Chair decision on WGLC for draft-ietf-v6ops-dhcp-pd-per-device-04
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Sun, 05 Nov 2023 23:27:45 -0000

Jordi,

Please tell me where I can get my ~8000 /48s for the non-LIR University I'm working for. So far, I have 1 /48. And because we started our address plan in around 2007, it does not take into consideration every single host having /64.

Also, as we are surrounded by other networks, I cannot expect to get my assignment extended, not by a single bit, even when the RIPE NCC would allow it (it currently does not). That would mean renumbering the whole network, which is not something I'm keen to do.

Theoretically, It is possible by current RIPE policy to extend one's assignment/allocation. However, this is pure fiction in practice. I've tried that in the case of my second employer (LIR ISP) to get my /29 extended to /28, but no luck, even when meeting the criteria.

Saying that we can give every human /48 could work if we would route IPs to people in global routing tables. Fortunately, we want to aggregate ...

Regards,
Martin

Dne neděle 5. listopadu 2023 19:57:25 CET jste napsal(a):
> In a /3 there are 35.184.372.088.832 /48s
> 
> if we underestimate the utilization to the 50%, that get’s us to half: 17.592.186.044.416 /48s
> 
> If the population gets to 34.359.738.368 people (not sure if that will fit in the earth), and we estimate that every human will live 100 years, and after that we don’t recover every /48, then with a single IPv6 /3, we will have a total IPv6 life-span of 51.200 years.
> 
> If we use the rest of the /3s, then we get up to 409.600 years.
> 
> And to be honest, I don’t think it makes sense to bury each /48 when a human pass away, same I don’t think that we should calculate it per human instead of householder, but I prefer to be pessimistic in terms of lifetime.
> 
> Regards,
> Jordi
> 
> @jordipalet
> 
> 
> > El 5 nov 2023, a las 19:46, Gert Doering <gert@space.net> escribió:
> > 
> > Hi
> > 
> > On Sun, Nov 05, 2023 at 07:42:03PM +0100, jordi.palet@consulintel.es wrote:
> >> It is pure maths.
> > 
> > Geoff's maths disagree with yours.  I prefer to err on the side of caution.
> > 
> > Gert Doering
> >        -- NetMaster
> 
> 
> **********************************************
> IPv4 is over
> Are you ready for the new Internet ?
> http://www.theipv6company.com
> The IPv6 Company
> 
> This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.
> 
> 
> 
>