IETF Logo Mail Archive

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

"jordi.palet@consulintel.es" <jordi.palet@consulintel.es> Mon, 06 November 2023 09:10 UTC

Return-Path: <prvs=16749efe3d=jordi.palet@consulintel.es>
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 6A42FC335B17; Mon, 6 Nov 2023 01:10:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.005
X-Spam-Level:
X-Spam-Status: No, score=-7.005 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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 (1024-bit key) header.d=consulintel.es
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 lpSv5TfqC1yh; Mon, 6 Nov 2023 01:10:34 -0800 (PST)
Received: from mail.consulintel.es (mail.consulintel.es [IPv6:2001:470:1f09:495::5]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3CB23C1FB875; Mon, 6 Nov 2023 01:10:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=consulintel.es; s=MDaemon; t=1699261815; x=1699866615; i=jordi.palet@consulintel.es; q=dns/txt; h=From:Message-Id: Content-Type:Mime-Version:Subject:Date:In-Reply-To:Cc:To: References; bh=7ISllK9O4k1YFMMxOuorKEjhusVrxUTMcldeRTQBWo8=; b=L mUhSHZ9I9//K/aaim/giO8JT2N8vOdqAraUEvT6sJlKdyzb70vmwuqhuDGJeOjpX Orld9/zLUtxizMRhfMsjRORvUWrkEVk8tsgoK/A5A6zRKtdvzDAikhdc4R95H9Wx PvX2oA0HJJHI3iDjISPa3LnRZJsXB1HH35Op6nEkEw=
X-MDAV-Result: clean
X-MDAV-Processed: mail.consulintel.es, Mon, 06 Nov 2023 10:10:15 +0100
X-Spam-Processed: mail.consulintel.es, Mon, 06 Nov 2023 10:10:12 +0100
Received: from smtpclient.apple by mail.consulintel.es (MDaemon PRO v16.5.2) with ESMTPA id md50001289767.msg; Mon, 06 Nov 2023 10:10:10 +0100
X-MDRemoteIP: 2001:67c:1232:144:147f:4b30:2310:b2b2
X-MDHelo: smtpclient.apple
X-MDArrival-Date: Mon, 06 Nov 2023 10:10:10 +0100
X-Authenticated-Sender: jordi.palet@consulintel.es
X-Return-Path: prvs=16749efe3d=jordi.palet@consulintel.es
X-Envelope-From: jordi.palet@consulintel.es
From: "jordi.palet@consulintel.es" <jordi.palet@consulintel.es>
Message-Id: <2E76ED74-0680-4456-B44E-AA2E25E4BAC2@consulintel.es>
Content-Type: multipart/alternative; boundary="Apple-Mail=_151C0FFB-6294-47D3-A7C8-18EFBBBFE69A"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3774.200.91.1.1\))
Date: Mon, 06 Nov 2023 10:09:51 +0100
In-Reply-To: <ZUf8ARPTb2TMXY46@Space.Net>
Cc: Martin Hun??k <martin.hunek@tul.cz>, Xipengxiao <xipengxiao@huawei.com>, "v6ops@ietf.org" <v6ops@ietf.org>, V6Ops Chairs <v6ops-chairs@ietf.org>
To: Gert Doering <gert@space.net>
References: <e078c90495b54390a3fb4c7bae143b05@huawei.com> <2031501.h9gRbJKcGU@asclepius.adm.tul.cz> <5A3E8566-1309-4DBE-B4F7-F5462E697CF7@consulintel.es> <2852055.eeVPZ7aKPO@asclepius.adm.tul.cz> <54DFAB91-0093-42C7-BBD0-22AE3B6274E5@consulintel.es> <ZUfi_ZXN4jxDIWty@Space.Net> <48AD358D-15EE-4728-B5A6-769D35933860@consulintel.es> <ZUf8ARPTb2TMXY46@Space.Net>
X-Mailer: Apple Mail (2.3774.200.91.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/UkNnjRj2jMYEWjc0AQ0nIF4gKEg>
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: Mon, 06 Nov 2023 09:10:45 -0000

Yes, but the assumptions of wasting 50% in my calculations and that we will bury every /48 with each human, and that each human needs a /48, instead of each householder, very well balance that.

Our problem in the next 25-50-100 years will not be IPv6 exhaustion but something else … such as routing table maybe.

Saludos,
Jordi

@jordipalet


> El 5 nov 2023, a las 21:33, Gert Doering <gert@space.net> escribió:
> 
> Hi,
> 
> On Sun, Nov 05, 2023 at 07:57:25PM +0100, jordi.palet@consulintel.es wrote:
>> 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
> 
> Look at the HD-Ratio tables, and understand the reality behind address
> distribution with multilevel aggregation.
> 
> If we could route individual /48s all the way we want, your math would
> have merits.
> 
> Gert Doering
>        -- NetMaster
> -- 
> have you enabled IPv6 on something today...?
> 
> SpaceNet AG                      Vorstand: Sebastian v. Bomhard, Michael Emmer
> Joseph-Dollinger-Bogen 14        Aufsichtsratsvors.: A. Grundner-Culemann
> D-80807 Muenchen                 HRB: 136055 (AG Muenchen)
> Tel: +49 (0)89/32356-444         USt-IdNr.: DE813185279



**********************************************
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.

v2.41.0 | Report a Bug | By Email | System Status