IETF Logo Mail Archive

Re: [dhcwg] recommendation on DHCP6 source port numbers

Robert Nagy <rob@deepdivenetworking.com> Thu, 29 February 2024 16:32 UTC

Return-Path: <rob@deepdivenetworking.com>
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 F4156C1C4DA5 for <dhcwg@ietfa.amsl.com>; Thu, 29 Feb 2024 08:32:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.012
X-Spam-Level:
X-Spam-Status: No, score=-6.012 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.1, MIME_HTML_ONLY_MULTI=0.001, MPART_ALT_DIFF=0.79, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] 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 vv6HTTWDlYsC for <dhcwg@ietfa.amsl.com>; Thu, 29 Feb 2024 08:32:28 -0800 (PST)
Received: from sender4-op-o10.zoho.com (sender4-op-o10.zoho.com [136.143.188.10]) (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 A95AFC19ECBA for <dhcwg@ietf.org>; Thu, 29 Feb 2024 08:32:28 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1709224345; cv=none; d=zohomail.com; s=zohoarc; b=dAcZVF07LPgjWg7ty54Dafp7zbnjB53dMLTMCqb9KShgZYi3B1ZL01olYWf/+sEMi5Gof/FwHr9J2r/wvFz/qAMPTNTpMq2z08v6amnQH578cgipvZ1508LqF/+Bh712pFWw94U58UJ4xwbpmOB836tSU3n7u9stiFKMr6JtHsA=
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=zohomail.com; s=zohoarc; t=1709224345; h=Content-Type:Content-Transfer-Encoding:Cc:Cc:Date:Date:From:From:In-Reply-To:MIME-Version:Message-ID:References:Subject:Subject:To:To:Message-Id:Reply-To; bh=EiFGq+bL1uWGkFp+ibjgz1ZWuwkWIGanSBtiWdn31D8=; b=MxvhJX9I+P1ZWXy+IjwCENZKeW6sEIOvRZP0x1TC5BHaZgr+GLOyZu260S4K8iqFR8S52BMYND2zSYbGmKtKsNTcVDzQj6rK2QYkSaFy5g82eE/91XeroOLpDQTdtwvOXvCExBWje/sy/NK3wHfIiBYPAFffYZaTEZzMpNvu9Ws=
ARC-Authentication-Results: i=1; mx.zohomail.com; spf=pass smtp.mailfrom=rob@deepdivenetworking.com; dmarc=pass header.from=<rob@deepdivenetworking.com>
Received: from mail.zoho.com by mx.zohomail.com with SMTP id 1709224343901472.76160753884074; Thu, 29 Feb 2024 08:32:23 -0800 (PST)
Content-Type: multipart/alternative; boundary="Apple-Mail-CEB1EF3D-804A-45D9-AD99-8AF8BCA774AF"
Content-Transfer-Encoding: 7bit
From: Robert Nagy <rob@deepdivenetworking.com>
Mime-Version: 1.0
Date: Thu, 29 Feb 2024 08:32:13 -0800
Message-Id: <F31CE6B2-ADDD-4DF5-B729-77DFC0A7B118@deepdivenetworking.com>
References: <CAN-Dau14nHcuN6HBQsLBNcYkCK1seE4r5iLcg+3d=8WBMK0eJg@mail.gmail.com>
Cc: Ole Troan <otroan=40employees.org@dmarc.ietf.org>, dhcwg <dhcwg@ietf.org>
In-Reply-To: <CAN-Dau14nHcuN6HBQsLBNcYkCK1seE4r5iLcg+3d=8WBMK0eJg@mail.gmail.com>
To: David Farmer <farmer=40umn.edu@dmarc.ietf.org>
User-Agent: Zoho Mail
X-Mailer: Zoho Mail
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/VAjkpC60e0fjCsvFfNnW0UuGx0c>
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: Thu, 29 Feb 2024 16:32:33 -0000

+1 to David’s suggestion. I as well have never found this ambiguous but I do see why people might. IMNHO we dictate the service ports things are sent to (hence listen on) whereas what clients and servers use for source ports is open to implementation  

Rob

Robert Nagy
CEO/ Senior Dive Master
DeepDive Networking, Inc
C: 408.480.5133


Sent from my iPhone

On Feb 29, 2024, at 8:24 AM, David Farmer <farmer=40umn.edu@dmarc.ietf.org> wrote:


Would this text clarify things?

Clients receive DHCP messages on UDP (destination) port 546.  Servers and relay agents receive DHCP messages on UDP (destination) port 547.

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 the client uses, the server or relay agent MUST send traffic to the designated destination port of the client. And vice versa, regardless of the source port used by the server or relay agent, the client MUST send traffic to the designated destination port of the server or relay agent.

Thanks

On Thu, Feb 29, 2024 at 10:03 AM Ole Troan <otroan=40employees.org@dmarc.ietf.org> wrote:
Bernie,

> DHCPv6 has been successfully deployed and this is the first I recall of this kind of discussion/issue.
> You would likely also invalidate a lot of implementations with such a change, which is not really in line with advancing this to Full Standard.

It’s a lot more important to have the specification clear and unambiguous. I think it has been shown that it isn’t.
Happy with whatever solution there is consensus for, but the ambiguity has to be resolved I think.

O.
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg" rel="noreferrer nofollow" target="_blank">https://www.ietf.org/mailman/listinfo/dhcwg


--
===============================================
David Farmer               Email:farmer@umn.edu
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota  
2218 University Ave SE        Phone: 612-626-0815
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================
_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email