[dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs / server ID
David 'equinox' Lamparter <equinox@diac24.net> Thu, 25 July 2024 16:54 UTC
Return-Path: <equinox@diac24.net>
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 BB243C16942B; Thu, 25 Jul 2024 09:54:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.908
X-Spam-Level:
X-Spam-Status: No, score=-1.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
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 B2sa6KyOiq98; Thu, 25 Jul 2024 09:53:58 -0700 (PDT)
Received: from eidolon.nox.tf (eidolon.nox.tf [IPv6:2a07:2ec0:2185::]) (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 E19C0C1930B6; Thu, 25 Jul 2024 09:53:44 -0700 (PDT)
Received: from equinox by eidolon.nox.tf with local (Exim 4.97.1) (envelope-from <equinox@diac24.net>) id 1sX1im-00000007y0V-184s; Thu, 25 Jul 2024 18:53:40 +0200
Date: Thu, 25 Jul 2024 18:53:40 +0200
From: David 'equinox' Lamparter <equinox@diac24.net>
To: Bernie Volz <bevolz@gmail.com>
Message-ID: <ZqKDFGqqjEVS5vAU@eidolon.nox.tf>
References: <ZqGViiJ8jEPaD5hB@eidolon.nox.tf> <65241FCE-649D-4734-BD91-032AE2B79CF6@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <65241FCE-649D-4734-BD91-032AE2B79CF6@gmail.com>
Message-ID-Hash: ILTRQ3UBGDSAZSHX5N3AOZ6XYLMZZVGP
X-Message-ID-Hash: ILTRQ3UBGDSAZSHX5N3AOZ6XYLMZZVGP
X-MailFrom: equinox@diac24.net
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
CC: draft-porfiri-dhc-dhcpv4-over-dhcpv6-ra@ietf.org, dhcwg@ietf.org
X-Mailman-Version: 3.3.9rc4
Precedence: list
Subject: [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs / server ID
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Mjkj_Y6JQhToDa-s0Y0s9ssJT6I>
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>
On Thu, Jul 25, 2024 at 07:50:09AM -0400, Bernie Volz wrote: > router (likely also relay) would need an IPv4 address anyway. The draft suggests implementing 4o6RA on an L2 switch. With option 82, that switch was previously inserting it on passing through an IPv4 packet - it didn't need an IPv4 address itself, and it likely doesn't have one, at least in the "user" network. (It might have one in an isolated management network, but that might be IPv6, so the switch has no IPv4 at all.) Now the L2 switch translates incoming IPv6 4o6 replies into IPv4 for the legacy client. The 4o6 packet has no IPv4 source address; the L2 switch needs to come up with one. Is that going to be 0.0.0.0? > And, we have existing mechanisms such as server-id override (added to > v4 dhcp request in option 82) that could be used should the clients > not be able to directly communicate with the dhcp server itself. The draft might want to include a recommendation to use 5107; if I understand correctly it'd mean the DHCP server doesn't need an IPv4 address at all? (Even if it still has one, the client bypassing the relay and RENEWing with the server is probably not desirable, considering this draft is all about topology information.) (Also the multiplication of above 2 things clashes again, how do you do 5107 with an L2 switch that has no IPv4 address itself?) Cheers, equi (David)
- [dhcwg] dhcpv4-over-dhcpv6-ra: source addrs / ser… David 'equinox' Lamparter
- [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs /… Bernie Volz
- [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs /… David 'equinox' Lamparter
- [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs /… David 'equinox' Lamparter
- [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs /… Bernie Volz
- [dhcwg] Re: dhcpv4-over-dhcpv6-ra: source addrs /… David 'equinox' Lamparter