Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 2023
Ole Troan <otroan@employees.org> Thu, 14 September 2023 10:47 UTC
Return-Path: <otroan@employees.org>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AAC6C14CE52 for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 03:47:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 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_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=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=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 R04hC6Ozycku for <dhcwg@ietfa.amsl.com>; Thu, 14 Sep 2023 03:47:32 -0700 (PDT)
Received: from proxmox01.kjsl.com (proxmox01.kjsl.com [IPv6:2607:7c80:54:6::6]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C3EACC14CE45 for <dhcwg@ietf.org>; Thu, 14 Sep 2023 03:47:32 -0700 (PDT)
Received: from proxmox01.kjsl.com (localhost.localdomain [127.0.0.1]) by proxmox01.kjsl.com (Proxmox) with ESMTP id 8E3CCE5A96; Thu, 14 Sep 2023 10:47:32 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=employees.org; h=cc:cc:content-transfer-encoding:content-type:content-type :date:from:from:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to; s=prox2023; bh=5x6rAQi6d5iSMnP6 +hphpJhtpZ8/r9cLon40+GDHV5U=; b=fBOUC8wAJewfrGKA8sHsAgq2PsyeE1c0 reGcz3R+c+rw0xxdU+fwgyPQaNN6V4W/O5Tuy/mE70+swYCWqVU20Fh9RZIRwban h0R6iSp2+6Wo92mKu3qAC4ea8cULpBMI/C/x655LU/a9q3SBL53tR+D184GxUed9 86l/Th5Mt6nc4l4BMr5+Zk2JwcTpiFanOH5PRLpgu4mFTp7d9raNWrJ8wV00xNu3 LHFTdPOZaDRI3Corj36n7cex7MdiyqbsuF+BLt9U+f1CZ88kzgNif5+FIPC/ErUe 6RVcj1tj9fRUInNbU9kdPNPmfZhlQaRDmAlQl8yhevpotb8S7ScQmg==
Received: from clarinet.employees.org (clarinet.employees.org [IPv6:2607:7c80:54:3::74]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) by proxmox01.kjsl.com (Proxmox) with ESMTPS id 705C5E5A39; Thu, 14 Sep 2023 10:47:32 +0000 (UTC)
Received: from smtpclient.apple (77.16.214.56.tmi.telenormobil.no [77.16.214.56]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by clarinet.employees.org (Postfix) with ESMTPSA id 9AA454E11AF6; Thu, 14 Sep 2023 10:47:31 +0000 (UTC)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.700.6\))
From: Ole Troan <otroan@employees.org>
In-Reply-To: <CAFU7BAQu+eFunTPE7DFi=sMEbbEd7_D2+YV9HFHYzkAgZYfqcg@mail.gmail.com>
Date: Thu, 14 Sep 2023 12:47:19 +0200
Cc: Lorenzo Colitti <lorenzo@google.com>, dhcwg <dhcwg@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7137E787-AA97-43F8-B35E-9F098C79D935@employees.org>
References: <CAKD1Yr3AEOa_7dKM15g+z6ZPDApZz08vgCS4kn9Uvi=+B9Dthg@mail.gmail.com> <3F659608-5298-42B3-9403-2C2A170DFCB3@employees.org> <CAKD1Yr3no4WQ6-dsTYVNswfdT85zmg4fHXvLJPMa--ZT9=h6Og@mail.gmail.com> <A675F57A-7FDA-4011-A100-AA3CDA52A323@employees.org> <A87EAA8A-0A80-4FCF-BEB9-6C19022751E2@employees.org> <CAKD1Yr1qs_+Y+Eb+oSjYQ6-033anRkn3d_fcWXcZ6s5mCA-_aA@mail.gmail.com> <4705B18E-E96E-4EED-8CDC-70431600F59F@employees.org> <CAKD1Yr0BGoZNKgaO5wRVg9V2Cs6swj+POnVj+7hoPixkdByxug@mail.gmail.com> <98972EEB-EB29-4DDD-AF07-B4848D406C96@employees.org> <CAFU7BATFx-yW9p88BLOMCarps92ejj4zYkvJB=BBtPqOy9QD3A@mail.gmail.com> <DA08259F-B3AF-43CD-858C-5EBC399D20A7@employees.org> <CAFU7BASuLfBB0TswJdza2xtwhXqiZ=HHt-EvsofAK9zSp5G9TA@mail.gmail.com> <16472FC6-4253-4117-986A-2FE24B1ACDE8@employees.org> <CAFU7BAQu+eFunTPE7DFi=sMEbbEd7_D2+YV9HFHYzkAgZYfqcg@mail.gmail.com>
To: Jen Linkova <furry13@gmail.com>
X-Mailer: Apple Mail (2.3731.700.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/uxFhP58Yo77pNYExgOTgMAcva2k>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notification - Respond by September 13, 2023
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Sep 2023 10:47:37 -0000
Jen, >>> This is becoming more like a topic for v6ops, but...My point is that >>> even if all enterprise devices support DHCPv6 IA_NA (let's say there >>> are no Android devices on the network), that it's not possible to >>> build an DHCPv6-only enterprise network. SLAAC is required and will be >>> required at least for some time. So it's not a matter of supporting >>> DHCPv6 IA_NA or not. >> >> I don’t think that statement is correct in the general case. >> For your statement to be true, you would have to assume IPv6 only on the link and you would have to assume 464XLAT. >> >> 464XLAT isn’t the only way to bring IPv4 connectivity to IPv4 only applications. >> I would imagine you could also build a 464CLAT that can share address with the host address. > > I'd expect such approach to have some performance implications, so I'd > consider it undesirable. > Anyway it's not how modern OSes do it. > >> You could even give out two addresses in DHCP IA_NA if that was required. > > In theory yes, in practice I doubt it would be possible any time soon. > >> I think you can run a network with DHCPv6 only. >> In face I’m sitting on such a network right now. Albeit with IPv4 also enabled. > > As I said in another email on this thread: do we really want to assume > that IPv4 is always around as a safety net for cases when IPv6 is > broken? > Is it a desirable deployment scenario? (spoilers: I strongly believe it isn't). > IMHO when we develop something for IPv6, we shall make sure it works > w/o any IPv4 on the link. > > So yes, when I'm saying "it's not possible to build a DHCPv6-only > enterprise network" I do assume it's IPv6-only. Currently it also > implies 464xlat. Going by that logic. I think you could simplify your statement to: It’s not possible to build an IPv6 only enterprise network. Period. Not all hosts support 464XLAT. Nor any other IPv4 transition mechanism. Not all networks support the mechanisms for NAT64 discovery. In the long and arduous path towards that, if it ever happens. I am not at all convinced that the current protocol under discussion, the DHCPv6 address notification protocol is helping rather than harming. O.
- [dhcwg] WGLC for draft-ietf-dhc-addr-notification… Timothy Winters
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Erik Kline
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Sheng Jiang
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Michael Richardson
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… David Farmer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Lorenzo Colitti
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Jen Linkova
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ted Lemon
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… David Farmer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Bernie Volz
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Nick Buraglio
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Timothy Winters
- [dhcwg] Fwd: WGLC for draft-ietf-dhc-addr-notific… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Trøan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Li HUANG
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Timothy Winters
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Mark Smith
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… David Farmer
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Ole Troan
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Alan DeKok
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… rob@deepdivenetworklng.com
- Re: [dhcwg] WGLC for draft-ietf-dhc-addr-notifica… Nick Buraglio