[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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.

- Ralph


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

> Some clarification of port number usage, please:
> 
>  
> 
> Section 5.2 seems to make it simple.  Clients use 546, Servers and
> Relays use 547.  However, section 21.1 (when talking about Selectors for
> IPSec tunnels between Relays and Servers) talks about both port 546 and
> 547.  If relays are to only use 547, why mention 546 in 21.1?
> 
>  
> 
> So the question is, what's the correct port usage for Relays?  Is it
> supposed to listen on only port 547 for all of its DHCPv6 traffic?  Or
> is it supposed to listen on port 547 for Client -> Relay traffic, and
> port 546 for Server/Relay -> Relay traffic (as the Relay is effectively
> playing DHCPv6 client to the server/relay)?
> 
>  
> 
> Also note, 3315 doesn't specify source port numbers.  Is it supposed to
> be defined that servers & relays send from 547 (potentially Relays from
> 546 and 547, depending on whether it's sending to a Server/Relay or a
> Client), and clients send from 546, or are ephermal source port numbers
> "OK"?
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg at ietf.org
> https://www1.ietf.org/mailman/listinfo/dhcwg

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