IETF Logo Mail Archive

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

Ted Lemon <ted.lemon@nominum.com> Thu, 12 December 2013 14:48 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B4081AE307 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 06:48:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.6
X-Spam-Level:
X-Spam-Status: No, score=-3.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, J_CHICKENPOX_55=0.6, RCVD_IN_DNSWL_MED=-2.3] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id fUlq1DLr9qV4 for <dhcwg@ietfa.amsl.com>; Thu, 12 Dec 2013 06:48:47 -0800 (PST)
Received: from exprod7og120.obsmtp.com (exprod7og120.obsmtp.com [64.18.2.18]) by ietfa.amsl.com (Postfix) with ESMTP id E969E1AE304 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 06:48:46 -0800 (PST)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob120.postini.com ([64.18.6.12]) with SMTP ID DSNKUqnMyXhVJUWWZHNApYVvRETdDbQL2WYc@postini.com; Thu, 12 Dec 2013 06:48:41 PST
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id 922631B82E2 for <dhcwg@ietf.org>; Thu, 12 Dec 2013 06:48:40 -0800 (PST)
Received: from webmail.nominum.com (cas-01.win.nominum.com [64.89.228.131]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTP id 6E406190043; Thu, 12 Dec 2013 06:48:40 -0800 (PST)
Received: from vpna-132.vpn.nominum.com (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 12 Dec 2013 06:48:40 -0800
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com>
Date: Thu, 12 Dec 2013 09:48:35 -0500
Content-Transfer-Encoding: quoted-printable
Message-ID: <0676A81F-E5B1-423C-8233-A5B143908A3A@nominum.com>
References: <489D13FBFA9B3E41812EA89F188F018E1ADA99A8@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1ADD590C@xmb-rcd-x04.cisco.com> <CE4E8958-57AA-4D87-AA80-F2B12FF1A698@gmail.com> <489D13FBFA9B3E41812EA89F188F018E1ADDF49A@xmb-rcd-x04.cisco.com> <F0A0E7AD-387E-4F9C-8200-4297E79BA566@gmail.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, "draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org" <draft-ietf-dhc-dhcpv4-over-dhcpv6@tools.ietf.org>
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dhcpv4-over-dhcpv6-03 - Respond by Dec 9, 2013
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 12 Dec 2013 14:48:48 -0000

On Dec 12, 2013, at 7:39 AM, Qi Sun <sunqi.csnet.thu@gmail.com> 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.

v2.23.0 | Report a Bug | By Email