IETF Logo Mail Archive

Re: [dhcwg] Conclusion for draft-ietf-dhc-v4configuration-00

Ted Lemon <Ted.Lemon@nominum.com> Sun, 19 May 2013 16:31 UTC

Return-Path: <Ted.Lemon@nominum.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A933321F87D1 for <dhcwg@ietfa.amsl.com>; Sun, 19 May 2013 09:31:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -106.557
X-Spam-Level:
X-Spam-Status: No, score=-106.557 tagged_above=-999 required=5 tests=[AWL=0.042, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pxePQaLOnSPj for <dhcwg@ietfa.amsl.com>; Sun, 19 May 2013 09:31:29 -0700 (PDT)
Received: from exprod7og110.obsmtp.com (exprod7og110.obsmtp.com [64.18.2.173]) by ietfa.amsl.com (Postfix) with ESMTP id AA8C721F89D5 for <dhcwg@ietf.org>; Sun, 19 May 2013 09:31:27 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob110.postini.com ([64.18.6.12]) with SMTP ID DSNKUZj+X3AsNfMjsBWo0ik9EqUFU60ffclF@postini.com; Sun, 19 May 2013 09:31:27 PDT
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 53BA01B80D6 for <dhcwg@ietf.org>; Sun, 19 May 2013 09:31:27 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id 4CF7D19005D; Sun, 19 May 2013 09:31:27 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Sun, 19 May 2013 09:31:27 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Qi Sun <sunqi.csnet.thu@gmail.com>
Thread-Topic: [dhcwg] Conclusion for draft-ietf-dhc-v4configuration-00
Thread-Index: AQHOUWzOksvS2kVeK0CojhlacokdApkGrpoAgABOfACAANnMAIAACTOAgABadgCABPCfgIAAA/IA
Date: Sun, 19 May 2013 16:31:27 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B6307751A7B75@mbx-01.win.nominum.com>
References: <1775E640-867C-41E3-8EAC-2554D80D4DF6@cisco.com> <CDBA4957.707B7%ian.farrer@telekom.de> <786F13AA11E69F4DB2CCA23F7400C2FB0142D776@S2010EXCH1.ad.local> <8D23D4052ABE7A4490E77B1A012B63077519F6EF@mbx-01.win.nominum.com> <CE0B5816-EDE1-4EAF-9A2F-1B62E55F078B@gmail.com>
In-Reply-To: <CE0B5816-EDE1-4EAF-9A2F-1B62E55F078B@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="us-ascii"
Content-ID: <F998781DF5D72943B4FA18AFED61A9F0@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "dhcwg@ietf.org" <dhcwg@ietf.org>, "volz@cisco.com" <volz@cisco.com>
Subject: Re: [dhcwg] Conclusion for draft-ietf-dhc-v4configuration-00
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.12
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: Sun, 19 May 2013 16:31:35 -0000

On May 19, 2013, at 12:17 PM, Qi Sun <sunqi.csnet.thu@gmail.com> wrote:
> BTW, should we include draft-ietf-dhc-dhcpv6-unknown-msg-00 as a reference in the DHCPv4-over-DHCPv6 draft?

I think that would make sense, yes.

v2.23.0 | Report a Bug | By Email