IETF Logo Mail Archive

[dhcwg] Re: Adoption of draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra?

Michael Richardson <mcr+ietf@sandelman.ca> Thu, 18 July 2024 17:13 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 2A46DC151078 for <dhcwg@ietfa.amsl.com>; Thu, 18 Jul 2024 10:13:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.108
X-Spam-Level:
X-Spam-Status: No, score=-2.108 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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=sandelman.ca
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 yEV8R3kDpdaQ for <dhcwg@ietfa.amsl.com>; Thu, 18 Jul 2024 10:13:33 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0DB00C15109C for <dhcwg@ietf.org>; Thu, 18 Jul 2024 10:13:32 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 396E03898C; Thu, 18 Jul 2024 13:13:31 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavis, port 10024) with LMTP id ICoJnzhVvQEc; Thu, 18 Jul 2024 13:13:30 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [209.87.249.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 7B8AF38988; Thu, 18 Jul 2024 13:13:30 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1721322810; bh=8pPow7Ca2aa9UaWttLwciWhKBPeHze4/og0oqmBA2Qs=; h=From:To:Subject:In-Reply-To:References:Date:From; b=SLyZo7MNz64LWSMA4W4DQZmY96j9DCDAquFiNMsBgIrewEcoGBfvMKTJuWtuPMitm /dIYSZds046xLqLu5e1pbBFCAANKp3Kpm3NGj04uqu/1THSJEhr5ZetnpinxnXUKjD 5Qr+WaPujqW5KNXvIm6p2WcyRgn50bi+e2eoZgaFK7qpu1fyX9Z4YM26fGWJWegDtq VuXnVDBYdjI+KT6/zhODz4xHl63GFsOczJWNsTwBFVpWpDnkYdkvSffPfEpF+sdcGz QYIngQJWeeoHvRBVb1i+RncdqdlQfcRnd2Jm6E0NxCIaLSxP6eRhw7dhEFEjWtbjdr jD9uJhxRQ949g==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id 769C5504; Thu, 18 Jul 2024 13:13:30 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: "Eric Vyncke (evyncke)" <evyncke=40cisco.com@dmarc.ietf.org>, Jari Arkko <jari.arkko@piuha.net>, dhcwg <dhcwg@ietf.org>
In-Reply-To: <PH0PR11MB4966A63F8CC3C5874B0D5D51A9AC2@PH0PR11MB4966.namprd11.prod.outlook.com>
References: <FFF4CE58-6B7A-4222-975E-73F879FEE417@piuha.net> <974.1721243571@obiwan.sandelman.ca> <PH0PR11MB4966A63F8CC3C5874B0D5D51A9AC2@PH0PR11MB4966.namprd11.prod.outlook.com>
X-Mailer: MH-E 8.6+git; nmh 1.8+dev; GNU Emacs 28.2
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0;<'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Thu, 18 Jul 2024 13:13:30 -0400
Message-ID: <24283.1721322810@obiwan.sandelman.ca>
Message-ID-Hash: LLU6OI3VOZS6AI5KTDIBAYFC2W2HXXZT
X-Message-ID-Hash: LLU6OI3VOZS6AI5KTDIBAYFC2W2HXXZT
X-MailFrom: mcr+ietf@sandelman.ca
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dhcwg.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [dhcwg] Re: Adoption of draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra?
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/vrd1uBoKRB5wWAzgwF5rF6wP-T8>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Owner: <mailto:dhcwg-owner@ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Subscribe: <mailto:dhcwg-join@ietf.org>
List-Unsubscribe: <mailto:dhcwg-leave@ietf.org>

Eric Vyncke \(evyncke\) <evyncke=40cisco.com@dmarc.ietf.org> wrote:
    > [and without any hat] I also think that this document would benefit if
    > the RAN use case was removed. I.e., plain DHCPv4 relay over DHCPv6 is
    > interesting enough and more generic.

I don't know if it needs to go away; it might really be their primary use
case, but I think it needs a bit more detail.

I would generally err on the side of more use cases before adoption.


--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide

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