Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

Simon Perreault <> Wed, 27 November 2013 18:09 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id E941D1AD694 for <>; Wed, 27 Nov 2013 10:09:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id z_G7nDxkkbSR for <>; Wed, 27 Nov 2013 10:09:50 -0800 (PST)
Received: from ( [IPv6:2620:0:230:8000::2]) by (Postfix) with ESMTP id 995E51ADF0E for <>; Wed, 27 Nov 2013 10:09:50 -0800 (PST)
Received: from (unknown [IPv6:2620:0:230:c000:dd97:4873:5d32:1565]) by (Postfix) with ESMTPSA id 97409403BB; Wed, 27 Nov 2013 13:09:49 -0500 (EST)
Message-ID: <>
Date: Wed, 27 Nov 2013 13:09:49 -0500
From: Simon Perreault <>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.0
MIME-Version: 1.0
To: Qi Sun <>
References: <> <> <> <>
In-Reply-To: <>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 27 Nov 2013 18:09:53 -0000

Le 2013-11-27 11:18, Qi Sun a écrit :
>> - The client MUST always include both OPTION_DHCP4_O_DHCP6_ENABLE and
> [Qi] RFC3315 says that the client SHOULD use unicast if instructed by
> the server. In this document, if the client doesn't include this option,
> it can still work (using multicast). So I think it's SHOULD for the

Let me repeat: You don't want to have a server sending an option that 
was not requested by the client. Stay with the usual ORO model.

Please explain why deviating from the usual ORO model is warranted.

>> - The server responds with zero (if DHCPv4-over-DHCPv6 is not
>> available) or one of two options. Never both.
>>    - OPTION_DHCP4_O_DHCP6_ENABLE means "multicast".
>>    - OPTION_DHCP4_O_DHCP6_SERVER means "unicast".
>> If this makes sense, then I would rename the options:
>> s/ENABLE/MULTICAST/ and s/SERVER/UNICAST/. And maybe go further and
>> kill OPTION_DHCP4_O_DHCP6_ENABLE, and just put the multicast address
>> in the payload of OPTION_DHCP4_O_DHCP6_SERVER.
> [Qi] The multicast address is a well-known address in RFC3315. The
> client knows it even you don't tell the client. I don't think it
> necessary to put the multicast address into the option.

I did not argue that it was necessary to tell the multicast address to 
the client. I did argue that it was simpler to have only one option.

>> By the way, a suggestion for the document: replace all instances of
>> "4o6 Server Address option" with the full option name,
>> "OPTION_DHCP4_O_DHCP6_SERVER". Always using the same terminology makes
>> it much easier to grep the document.
> [Qi] Thanks for the suggestion! IMHO, the "4o6 Server Address option" is
> the name of the option, while the OPTION_DHCP4_O_DHCP6_SERVER is the
> option code to be assigned by the IANA. What I get from RFC3315 is that
> when you refer to an option, use the name; if you want to mention the
> code, then use the uppercase phrase.

Sure, it is common practice, but it still makes the document harder to 
grep. But this is just an editorial suggestion, I don't care much. Feel 
free to ignore it.

DTN made easy, lean, and smart -->
NAT64/DNS64 open-source        -->
STUN/TURN server               -->