IETF Logo Mail Archive

Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options forDHCPv6

"TS Glassey" <tglassey@earthlink.net> Thu, 22 November 2007 00:22 UTC

Return-path: <dhcwg-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuzqD-0000li-PF; Wed, 21 Nov 2007 19:22:49 -0500
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IuzqC-0000ld-MC for dhcwg@ietf.org; Wed, 21 Nov 2007 19:22:48 -0500
Received: from elasmtp-curtail.atl.sa.earthlink.net ([209.86.89.64]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IuzqC-0002EE-AI for dhcwg@ietf.org; Wed, 21 Nov 2007 19:22:48 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=jLEoyltlf2OdLo+XW+R1IhSPFGzw4ukNE4Jps3zHGvHudARD2jrgkq27E8NPWE9X; h=Received:Message-ID:From:To:Cc:References:Subject:Date:MIME-Version:Content-Type:Content-Transfer-Encoding:X-Priority:X-MSMail-Priority:X-Mailer:X-MimeOLE:X-ELNK-Trace:X-Originating-IP;
Received: from [24.23.176.93] (helo=tsg1) by elasmtp-curtail.atl.sa.earthlink.net with asmtp (Exim 4.34) id 1IuzqA-0002IT-0p; Wed, 21 Nov 2007 19:22:46 -0500
Message-ID: <001801c82c9d$ce250780$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Ted Lemon <mellon@fugue.com>, Harlan Stenn <stenn@ntp.org>
References: <20071121052610.DD3EF39E3F@mail1.ntp.org>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options forDHCPv6
Date: Wed, 21 Nov 2007 16:05:14 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="original"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.3138
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3138
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79b3ccb8fab3432bb809c7ae5479e6de74350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 39bd8f8cbb76cae18b7e23f7cf6b2b9f
Cc: ntpwg@lists.ntp.org, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>, dhcwg@ietf.org
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: dhcwg.ietf.org
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
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>
Errors-To: dhcwg-bounces@ietf.org

----- Original Message ----- 
From: "Harlan Stenn" <stenn@ntp.org>
To: "Ted Lemon" <mellon@fugue.com>
Cc: <ntpwg@lists.ntp.org>; "Danny Mayer" <mayer@ntp.org>; "Richard Gayraud 
(rgayraud)" <rgayraud@cisco.com>; <dhcwg@ietf.org>
Sent: Tuesday, November 20, 2007 9:24 PM
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) Options 
forDHCPv6


> Guys,
>
> Is this about mechanism or policy?

Both

>
> I would suspect (and hope) it is about mechanism.
>
> In that case one must be able to "offer" either a name or an IPv4
> address or an IPv6 address.
>
> If one *also* wishes to address policy issues, that's OK (IMO).
>
> But (again IMO) the underlying mechanism needs to support names and/or
> addresses.

true.

>
> H
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> https://lists.ntp.org/mailman/listinfo/ntpwg 


_______________________________________________
dhcwg mailing list
dhcwg@ietf.org
https://www1.ietf.org/mailman/listinfo/dhcwg

v2.23.0 | Report a Bug | By Email