Re: [dhcwg] recommendation on DHCP6 source port numbers

[David Farmer <[e-mail]>]

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=
[e-mail]> 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
> [e-mail]
> https://www.ietf.org/mailman/listinfo/dhcwg
>


-- 
===============================================
David Farmer               Email:[e-mail]
Networking & Telecommunication Services
Office of Information Technology
University of Minnesota
2218 University Ave SE        Phone: [phone]
Minneapolis, MN 55414-3029   Cell: 612-812-9952
===============================================