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

"TS Glassey" <tglassey@earthlink.net> Mon, 26 November 2007 04:06 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 1IwVEx-0005aK-0g; Sun, 25 Nov 2007 23:06:35 -0500
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IwVEt-0005YX-Rf for dhcwg@ietf.org; Sun, 25 Nov 2007 23:06:31 -0500
Received: from elasmtp-curtail.atl.sa.earthlink.net ([209.86.89.64]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IwVEq-0000se-DN for dhcwg@ietf.org; Sun, 25 Nov 2007 23:06:31 -0500
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=sZj8f/NmvbgW85IT4FuC43HTAuBO0vRIriMEpWa60VQnLzzHVfBRx7AcYUCLD7aj; 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 1IwVEp-0006lP-4z; Sun, 25 Nov 2007 23:06:27 -0500
Message-ID: <01b601c82fe1$b77d2c00$6401a8c0@tsg1>
From: TS Glassey <tglassey@earthlink.net>
To: Brian Utterback <Brian.Utterback@Sun.COM>
References: <200711260009.lAQ092va059077@drugs.dv.isc.org> <EF06E977-C3D9-4EDF-A126-6CD888BA8F36@fugue.com> <014d01c82fc6$6b1ecd70$6401a8c0@tsg1> <5C093633-A256-4059-AA10-1800F62F522A@fugue.com> <017901c82fd4$9cad3b70$6401a8c0@tsg1> <474A3297.5040907@sun.com> <018401c82fd7$9f632c50$6401a8c0@tsg1> <474A3C32.1020006@sun.com>
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) OptionsforDHCPv6
Date: Sun, 25 Nov 2007 20:06:22 -0800
MIME-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="iso-8859-1"; reply-type="response"
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: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec795ede2818c4725d1c63d1144f5eb46c13350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 24.23.176.93
X-Spam-Score: 0.0 (/)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc: ntpwg@lists.ntp.org, dhcwg@ietf.org, Ted Lemon <mellon@fugue.com>, "Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
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

BLU
----- Original Message ----- 
From: "Brian Utterback" <Brian.Utterback@Sun.COM>
To: "TS Glassey" <tglassey@earthlink.net>
Cc: "Ted Lemon" <mellon@fugue.com>; <ntpwg@lists.ntp.org>; <dhcwg@ietf.org>; 
"Richard Gayraud (rgayraud)" <rgayraud@cisco.com>
Sent: Sunday, November 25, 2007 7:23 PM
Subject: Re: [ntpwg] [dhcwg] Re: Network Time Protocol (NTP) 
OptionsforDHCPv6


> TS Glassey wrote:
>>
>> I still don't know that the service is needed I have heard a couple of 
>> people mandate that they think this is necessary but in actuality I still 
>> haven't heard anything that makes this mandatory. Especially since 
>> without any pain at all its pretty easy to create a set of known NTP 
>> servers and just use the local DNS service to propagate these. WKS inside 
>> of DNS is a simple method that is time tested.
>>
>> Todd
>
> Okay, so your suggestion is to not have a DHCP NTP field at all, but to 
> have
> the clients use WKS and DNS resolution to find servers. Fair enough.

Yes and no. My suggestion is that the DCHP system could be used if it also 
had some reliable names which were predefined.

My real suggestion is that we need a Time and Trust Service Discovery 
protocol which would work sort of like how DHCP and DNS work but that also 
allows for critical events to be pushed forward as well. This would also 
work for CRL and OCSP type queries to satisfy validity of the underlying 
certificate source.

Todd

>
> blu
> 


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