IETF Logo Mail Archive

Re: [dhcwg] recommendation on DHCP6 source port numbers

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 01 March 2024 00:51 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 F3993C14F602 for <dhcwg@ietfa.amsl.com>; Thu, 29 Feb 2024 16:51:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.407
X-Spam-Level:
X-Spam-Status: No, score=-4.407 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_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, 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=ham 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 jRkREgVNyOBz for <dhcwg@ietfa.amsl.com>; Thu, 29 Feb 2024 16:51:17 -0800 (PST)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [209.87.249.19]) (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 DBE86C14F5FF for <dhcwg@ietf.org>; Thu, 29 Feb 2024 16:51:17 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id AFCD83898E for <dhcwg@ietf.org>; Thu, 29 Feb 2024 19:51:16 -0500 (EST)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id WoMKb0mX2SXv for <dhcwg@ietf.org>; Thu, 29 Feb 2024 19:51:15 -0500 (EST)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id AC1383898D for <dhcwg@ietf.org>; Thu, 29 Feb 2024 19:51:15 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sandelman.ca; s=mail; t=1709254275; bh=Zt6VtcRuZeXtMazfUA73qYrenVTwO0x1LHNbJtpOt3U=; h=From:To:Subject:In-Reply-To:References:Date:From; b=FUVbmRVaS1wbWQDe6+oRBF+bNxF1i4nkTmTiHnttF2jvG0TW32ZwODS9Bk5ePoXTq x9SuGWBvtLAndcu7JkJq8nXeY7pwdH1cuQJLfkqRbe6WMUl1Xy5fR0vWrZbyqQsBRo 4Lo/Lc+FW1pNSgL7WYOH36EN1y47MQc4kdLZ5P9r0t0Kllx9SJt8w9w4P1q/FlEJuN CheMcgJPurOwuu+6/gQJQG56ESDa0MK0odMVrBiHNVJ+SqYsCv7kFFXSsYyZDFjuII nmGWzT7P79nwELPijjrGyitappF728lpudRQ/OuBnzCO/O/ri3NJPPvTFc0HrJFpTL /6YtjREtNsQjQ==
Received: from obiwan.sandelman.ca (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id A4C67873 for <dhcwg@ietf.org>; Thu, 29 Feb 2024 19:51:15 -0500 (EST)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: dhcwg <dhcwg@ietf.org>
In-Reply-To: <CAN-Dau3m2_L7J9T9VBk7oyHTK0EeMeuiv+jNpuMGE3m1T623=A@mail.gmail.com>
References: <44363ABD-3FF1-4EA6-9E4D-85152467F24D@employees.org> <BAB1070B-E2B3-4430-B355-871B8AE1AEDF@gmail.com> <7031AD5E-97AB-42FF-99B5-DFD32F8FD665@employees.org> <CAN-Dau14nHcuN6HBQsLBNcYkCK1seE4r5iLcg+3d=8WBMK0eJg@mail.gmail.com> <CAN-Dau3m2_L7J9T9VBk7oyHTK0EeMeuiv+jNpuMGE3m1T623=A@mail.gmail.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, 29 Feb 2024 19:51:15 -0500
Message-ID: <9830.1709254275@obiwan.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/_tcyY0lu3HiX4Q4UX3L_QzRCojE>
Subject: Re: [dhcwg] recommendation on DHCP6 source port numbers
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: Fri, 01 Mar 2024 00:51:22 -0000

David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote:
    > Clients, servers, and relay agents MAY send DHCP messages from any UDP
    > (source) port they are allowed to use, including their designated
    > destination ports. Nevertheless, regardless of the source port used,
    > DHCP messages MUST be sent to their designated destination ports.

I guess I would just add:
    DHCP replies are never returned to the source port present in the packet.

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

v2.23.0 | Report a Bug | By Email