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

"Bernie Volz (volz)" <> Thu, 12 December 2013 17:01 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 1FD5A1ADFFD for <>; Thu, 12 Dec 2013 09:01:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -8.302
X-Spam-Status: No, score=-8.302 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, J_CHICKENPOX_55=0.6, J_CHICKENPOX_57=0.6, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 1201UZ8cFT1i for <>; Thu, 12 Dec 2013 09:01:15 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 9D7AA1ADF92 for <>; Thu, 12 Dec 2013 09:01:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;;; l=1836; q=dns/txt; s=iport; t=1386867669; x=1388077269; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=W9V93glHf+TAdzA/fG8UljpbWWzzHNB36et2XA1JfhA=; b=g/CTnbRL0PZB75eCfCqQ7yoZFrqjCrYJugzha49pqifABuP0gnHkRMnT vfUGPwIFDA7XAd6FxgOXcsQ5rZ5yPbxeyty/qAJ+dLOXqeDg4qLBemyTx swfQR+/YEcY27ctkaXEXqZtn7A5RV9U7r8ioEHqjPsa5QogvFO+S0RFIo Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos;i="4.93,879,1378857600"; d="scan'208";a="6336819"
Received: from ([]) by with ESMTP; 12 Dec 2013 17:01:08 +0000
Received: from ( []) by (8.14.5/8.14.5) with ESMTP id rBCH18Y7027033 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 12 Dec 2013 17:01:08 GMT
Received: from ([]) by ([]) with mapi id 14.03.0123.003; Thu, 12 Dec 2013 11:01:08 -0600
From: "Bernie Volz (volz)" <>
To: Ted Lemon <>, Qi Sun <>
Thread-Topic: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
Thread-Index: AQHO90lArmKZq0TABkWmduI/5klrZppQxvXA
Date: Thu, 12 Dec 2013 17:01:07 +0000
Message-ID: <>
References: <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "" <>, "" <>
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: Thu, 12 Dec 2013 17:01:17 -0000

I wonder whether DHCPV4REQUEST and DHCPV4REPLY (perhaps with a hyphen) may actually be better choices for the V6 messages. While the underlying protocol is BOOTP, that name is somewhat misleading and most everything now uses DHCP[v4] -- yes, I know that I was likely the source of those original message names.

I'm not sure using QUERY/RESPONSE adds much value.

But again, I really have no good answer here and was not trying to promote one name over the other - I was just asking the WG the question as to whether these are good message names or whether we wanted to change them now, before we are stuck with them 'forever'.

It is a minor issue (as what goes over the wire is really a message type code), but it does make a difference in tools (i.e., packet decoders), logs, and in source code.

- Bernie

-----Original Message-----
From: Ted Lemon [] 
Sent: Thursday, December 12, 2013 9:49 AM
To: Qi Sun
Cc: Bernie Volz (volz);;
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013

On Dec 12, 2013, at 7:39 AM, Qi Sun <> wrote:
> I'm OK with your suggestion (using the  BOOTPREQUESTV6 and BOOTPREPLYV6).

The only reason to use BOOTREQUESTv6 and BOOTREPLYv6 is the similarity between that name and the name of the BOOTP packet that DHCPv4 rides in.   If you are going to change the name, you might as well call it DHCPv4QUERY and DHCPv4RESPONSE or something.   Using the BOOTP name allows you to avoid confusion between DHCPREQUEST/DHCPREPLY and DHCPv4REQUEST/DHCPv4REPLY, but you could use QUERY/RESPONSE to avoid that just as well.

Anyway, I don't think BOOTPREQUESTv6 makes a whole lot of sense.