IETF Logo Mail Archive

Re: [v6ops] Fwd: New Version Notification for draft-collink-v6ops-ent64pd-01.txt

Ole Troan <otroan@employees.org> Thu, 15 December 2022 20:47 UTC

Return-Path: <otroan@employees.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 BE213C152702; Thu, 15 Dec 2022 12:47:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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=employees.org
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 dtX2-68e3ir1; Thu, 15 Dec 2022 12:47:52 -0800 (PST)
Received: from vesa02.kjsl.com (vesa02.kjsl.com [IPv6:2620:13b:0:1000::10]) (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 03990C1526F8; Thu, 15 Dec 2022 12:47:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=employees.org; i=@employees.org; q=dns/txt; s=vesa202009; t=1671137273; x=1702673273; h=content-transfer-encoding:from:mime-version:subject:date: message-id:references:cc:in-reply-to:to; bh=sl1Tvqa4YoPRkHbwUF1ZJaC0OMk25e9AQkyP96clPkw=; b=fzXztfojr73E043qjf8He7ljC+TpMppJZeLoXBMrRwghlb/yBoGXml9E pgf3Qcf/LIjPpKMFxqqt7aBpaUF7kllx9PscZy1HIeI9Hxtmn4cXDrtfB X8dlmBd/RZ3sCJ2A5HEyo97FOmgUj//g2mn25gzj8tODdv/5d5pOwp+I8 fgeFS5og+OkJg8ypsbGYvU4ASlazq5v9lCnpGjNqZtnYNIwIpwmZj1QO1 GPNGJNr038JOv5h5GRf7lPZsAfCrg/nH4oJaKSp8H4MFQqNcFkwe5/jEr o7HUUTmXbQXNxeYG66BdioFfbEQ8wpjaCMGb1VQV9XeFZ1PjaMOPPBBzd Q==;
Received: from clarinet.employees.org ([198.137.202.74]) by vesa02.kjsl.com with ESMTP; 15 Dec 2022 20:47:52 +0000
Received: from smtpclient.apple (ti0389q160-5811.bb.online.no [95.34.2.246]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 6F2504E11B80; Thu, 15 Dec 2022 20:47:50 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Ole Troan <otroan@employees.org>
Mime-Version: 1.0 (1.0)
Date: Thu, 15 Dec 2022 21:47:38 +0100
Message-Id: <E1CAD2C9-755C-4BEF-97B4-4A23849A04FB@employees.org>
References: <Y5sy2ikgQEWSnCsM@Space.Net>
Cc: Jen Linkova <furry13@gmail.com>, V6 Ops List <v6ops@ietf.org>, draft-collink-v6ops-ent64pd@ietf.org, xiaom@google.com
In-Reply-To: <Y5sy2ikgQEWSnCsM@Space.Net>
To: Gert Doering <gert@space.net>
X-Mailer: iPhone Mail (20B110)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0hDhof77Z8jlNC9uYtzb4SsLKjY>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-collink-v6ops-ent64pd-01.txt
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: Thu, 15 Dec 2022 20:47:55 -0000

And DHCP PD can of course also assign a /128 prefix to the host if that’s desired. :-)

O. 

> On 15 Dec 2022, at 15:45, Gert Doering <gert@space.net> wrote:
> 
> Hi,
> 
>> On Thu, Dec 15, 2022 at 02:59:33PM +1100, Jen Linkova wrote:
>> We've just submitted -01 version of draft-collink-v6ops-ent64pd, which
>> proposes using DHCPv6-PD to delete /64 per host (the draft was very
>> briefly presented at the last IETF).
> 
> I do not think that a /64 per host is reasonable address usage.
> 
> To implement this, network admins need not only to add v6 subnets
> to broadcast segments but also add pools of sizeable size, which does
> create pressure in the /48.../64 range of the addresses they have
> ("one /48 per site").
> 
> Something like a /96 per host - so "limitless amounts of host would
> fit into a single /64" would avoid that, and still fulfill the 
> stated necessity of having many many many addresses per hosts.
> 
> 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
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops

v2.23.0 | Report a Bug | By Email