Re: [dhcwg] Ports clarification on DHCPv6

[Ralph Droms <rdroms at cisco.com>]

Working entirely from memory, the specification for the source port in
DHCPv4 is strictly based on the wording of RFC 2131, which, in turn, may be
a carryover from BOOTP.  I don't believe that there is any functional reason
why the source port needs to be constrained in DHCPv4.

We realized that the source port plays no real function in DHCP and we
explicitly did not specify source port behavior in RFC 3315.  Therefore,
there shouldn't be any implementation requirements that a DHCPv6 component
MUST use any particular source port.

- Ralph


On 12/7/06 2:23 PM, "Andre Kostur" <akostur at incognito.com> wrote:

> OK... but I guess an early warning on the source port issue:  Note that
> for DHCPv4 we (the WG) seem to be recommending that relays MUST use 67
> as their source port number (draft-ietf-dhc-implementation-02, section
> 4.7.2).  Looking forward, are we not going to be running into exactly
> the same issues in the DHCPv6 world?
> 
> -----Original Message-----
> From: Ralph Droms [mailto:rdroms at cisco.com]
> Sent: Thursday, December 07, 2006 10:36 AM
> To: Andre Kostur; dhcwg at ietf.org
> Subject: Re: [dhcwg] Ports clarification on DHCPv6
> 
> Andre - here is a quick response; I need to reread 21.1 (later today,
> after
> more teleconf hell) to give a complete response.
> 
> From RFC 3315:
> 
> 5.2. UDP Ports
> 
>    Clients listen for DHCP messages on UDP port 546.  Servers and relay
>    agents listen for DHCP messages on UDP port 547.
> 
> Relays listen for all traffic, whether from a client or the server, on
> port
> 547.  Source addresses are not specified by RFC 3315; any port (not
> restricted to just 546 and 547) can be used as a source port.  The
> message
> recipient ignores the source port.

_______________________________________________
dhcwg mailing list
dhcwg at ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg