[dhcwg] AD Review: draft-ietf-dhc-dhcpv6-opt-timeconfig-02.txt

Margaret Wasserman <mrw@windriver.com> Sat, 13 September 2003 23:51 UTC

Received: from optimus.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01675 for <dhcwg-archive@odin.ietf.org>; Sat, 13 Sep 2003 19:51:35 -0400 (EDT)
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19yKAY-0003va-2I for dhcwg-archive@odin.ietf.org; Sat, 13 Sep 2003 19:51:11 -0400
Received: (from exim@localhost) by www1.ietf.org (8.12.8/8.12.8/Submit) id h8DNpA28015094 for dhcwg-archive@odin.ietf.org; Sat, 13 Sep 2003 19:51:10 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19yKAX-0003vN-RR for dhcwg-web-archive@optimus.ietf.org; Sat, 13 Sep 2003 19:51:09 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id TAA01612 for <dhcwg-web-archive@ietf.org>; Sat, 13 Sep 2003 19:51:02 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19yKAV-00006U-00 for dhcwg-web-archive@ietf.org; Sat, 13 Sep 2003 19:51:07 -0400
Received: from ietf.org ([132.151.1.19] helo=optimus.ietf.org) by ietf-mx with esmtp (Exim 4.12) id 19yKAU-00006O-00 for dhcwg-web-archive@ietf.org; Sat, 13 Sep 2003 19:51:06 -0400
Received: from localhost.localdomain ([127.0.0.1] helo=www1.ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19yKAP-0003sf-Pe; Sat, 13 Sep 2003 19:51:01 -0400
Received: from odin.ietf.org ([132.151.1.176] helo=ietf.org) by optimus.ietf.org with esmtp (Exim 4.20) id 19xpz3-00044p-0D for dhcwg@optimus.ietf.org; Fri, 12 Sep 2003 11:37:17 -0400
Received: from ietf-mx (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA28717 for <dhcwg@ietf.org>; Fri, 12 Sep 2003 11:37:08 -0400 (EDT)
Received: from ietf-mx ([132.151.6.1]) by ietf-mx with esmtp (Exim 4.12) id 19xpz1-0000TM-00 for dhcwg@ietf.org; Fri, 12 Sep 2003 11:37:15 -0400
Received: from unknown-1-11.windriver.com ([147.11.1.11] helo=mail.wrs.com) by ietf-mx with esmtp (Exim 4.12) id 19xpz1-0000T4-00 for dhcwg@ietf.org; Fri, 12 Sep 2003 11:37:15 -0400
Received: from ala-mrwtemp.windriver.com ([147.11.233.18]) by mail.wrs.com (8.9.3/8.9.1) with ESMTP id IAA06887; Fri, 12 Sep 2003 08:36:37 -0700 (PDT)
Message-Id: <5.1.0.14.2.20030911172439.03646108@mail.windriver.com>
X-Sender: mrw@mail.windriver.com
X-Mailer: QUALCOMM Windows Eudora Version 5.1
Date: Thu, 11 Sep 2003 17:34:55 -0400
To: dhcwg@ietf.org
From: Margaret Wasserman <mrw@windriver.com>
Cc: Thomas Narten <narten@us.ibm.com>
Mime-Version: 1.0
Content-Type: multipart/mixed; boundary="=====================_68575466==_"
Subject: [dhcwg] AD Review: draft-ietf-dhc-dhcpv6-opt-timeconfig-02.txt
Sender: dhcwg-admin@ietf.org
Errors-To: dhcwg-admin@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Id: <dhcwg.ietf.org>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>

Hi All,

I've reviewed draft-ietf-dhc-dhcpv6-opt-timeconfig-02.txt, and I
have several comments on the document which are attached below.

Some of these comments are editorial, but I also have a few
fundamental questions that should be addressed by the WG before
we send this document to the full IESG:

    1) Given that we are in the process of deprecating the
       option codes for the equivalent IPv4 options, do we
       have a strong reason to believe that these options
       are needed for IPv6?  Why?  Has anyone implemented
       them?

    2) The applications area has not yet specified how NTP
       would run over IPv6.  Does that make it premature
       to define a DHCPv6 option to configure NTP server
       addresses?

    3) Why is it necessary or desirable to specify a
       format for timezone naming that is specific to
       this document, instead of relying completely
       on an existing standard?

I am not sure that it makes sense to address any of my other
comments, unless we can come up with a satisfactory answer
to my first question, above.

Margaret