
From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 16:32:04 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 475431AE2A2 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 16:32:04 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 rVv27gBH0Qvg for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 16:32:02 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 6F3B71AE299 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 16:31:59 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id AEA2686DAD9 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 00:31:57 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 03E0886D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 00:31:42 +0000 (UTC)
Received: from pool-173-76-224-232.bstnma.fios.verizon.net ([173.76.224.232] helo=[192.168.1.3]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnHQJ-0004FJ-DI; Mon, 02 Dec 2013 00:31:40 +0000
Message-ID: <529BD4CF.6000408@ntp.org>
Date: Sun, 01 Dec 2013 19:31:11 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Ted Lemon <ted.lemon@nominum.com>, Olafur Gudmundsson <ogud@ogud.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com>
In-Reply-To: <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 173.76.224.232
X-SA-Exim-Rcpt-To: ted.lemon@nominum.com, ogud@ogud.com, dhcwg@ietf.org, ntpwg@lists.ntp.org, volz@cisco.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 12/1/2013 5:29 PM, Ted Lemon wrote:
> On Dec 1, 2013, at 5:05 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
>> The "threat" the document is trying to address, device wants to
DNSSEC or CERT validation but clock is far off thus VALID credentials
fail validation.
> =

> Ah, thanks for explaining. This is what I was missing=97you're not
> doing
this to avoid a threat at all, but rather to simply make DNSSEC work in
a possibly non-secure mode until such time as you can bootstrap better
time information.
> =

> This would be worth mentioning in the introduction and/or the
> security
considerations section. You allude to it in the security considerations,
but it's pretty oblique.
> =

> It is worth pointing out that NTP doesn't actually need DNS to
work=97DHCP can deliver NTP server addresses as IP addresses. That said,
this option seems to add value, since there is no guarantee that devices
that implement the existing DHCP NTP will not send FQDNs rather than IP
addresses.

I had a long discussion with Bernie over the issue of delivering NTP IP
addresses via DHCP. We understand the issues you raised concerning
DNSSEC and have no disagreement about that. The problem is that for NTP
DNS names are preferred over IP addresses because that allows a server
maintainer to retire an NTP server. With an IP address there is no
chance that your local instance will know about this and continue to
bombard the old address. Moreover the newer pool option cannot be used
to any advantage.

When was the last time you looked at your NTP configuration and verified
that all of the servers listed are still valid? How often will DHCP
servers do this as a matter of course before providing such
provisioning? We have systems that are being bombarded by requests even
though no NTP server is responding to queries. We have plenty of
evidence of this. Even worse we have seen home routers which have
hard-coded IP addresses for NTP servers embedded. How long are those
going to be in operation?

I think we need to figure out how to get around the Catch-22 situation
of DNSSEC requiring relatively good time and NTP wanting to be able to
use DNS to find valid NTP servers.

We need a joint agreement on how to deal with this between DHCP and NTP
Working Groups assuming that is a viable option in the first place.
RFC5908 was not a good indication of this.

Danny

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 18:37:19 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE241AE06E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 18:37:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 PeClrj1etp3B for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 18:37:18 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 02D741AE2EB for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 18:37:18 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1720386D761 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 02:37:15 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 20B8086D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 02:37:04 +0000 (UTC)
Received: from exprod7og107.obsmtp.com ([64.18.2.167]) by mail1.ntp.org with smtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ted.Lemon@nominum.com>) id 1VnJNf-0004qO-3G for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 02:37:04 +0000
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob107.postini.com ([64.18.6.12]) with SMTP ID DSNKUpvyTgwqxvKP1RiyfjSgXzLi2akBRs5z@postini.com; Sun, 01 Dec 2013 18:37:03 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 51A061B82E2 for <ntpwg@lists.ntp.org>; Sun,  1 Dec 2013 18:37:02 -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 40901190043; Sun,  1 Dec 2013 18:37:02 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 18:37:02 -0800
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <529BD4CF.6000408@ntp.org>
Date: Sun, 1 Dec 2013 21:36:59 -0500
Message-ID: <A775B456-E8F6-4111-AFB3-B51BB92ABFC7@nominum.com>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
To: <mayer@ntp.org>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-SA-Exim-Connect-IP: 64.18.2.167
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 1, 2013, at 7:31 PM, Danny Mayer <mayer@ntp.org> wrote:
> We need a joint agreement on how to deal with this between DHCP and NTP
> Working Groups assuming that is a viable option in the first place.
> RFC5908 was not a good indication of this.

RFC 5908 got approved pretty much accidentally, without finishing the review process in the DHC working group.   It was a major screwup, and I don't precisely know how it happened.   It doesn't really do what you wanted, and it certainly doesn't do what we wanted.   I agree that this needs to be resolved, but the resolution has to be based on reasoning, not an instinctive reaction to past pain.

I'm not even convinced that DHCP is the right way to distribute NTP server information.   I suspect Olafur may be thinking about the case that's more common at present, which is that an FQDN is hard-coded into the O.S. distribution, and resolved at startup time.   In that case, DHCP's ability to deliver NTP server IP addresses doesn't help.

As for the home router use model, it may be that what you really want is for the home router to query for an FQDN-only DHCP option from the ISP DHCP server, and then resolve that FQDN and respond to DHCP clients on the homenet with an IP address.   Since the FQDN is not hard-coded, and the IP address is (one hopes) resolved either at query time or when its TTL expires, this ought to prevent a repeat of the firmware burn-in incident.

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 20:47:59 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F54E1AE2D6 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 20:47:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 HuMnUTI3wJDZ for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 20:47:58 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 1D7761ADFA1 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 20:47:58 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 28E1486DAB1 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 04:47:55 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 3C42786D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 04:47:42 +0000 (UTC)
Received: from mail7c25.carrierzone.com ([64.29.147.17]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <hmurray@megapathdsl.net>) id 1VnLQ3-0005kr-9D; Mon, 02 Dec 2013 04:47:42 +0000
X-POP-User: hmurray@megapathdsl.net
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by mail7c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id rB24lZUe018421; Mon, 2 Dec 2013 04:47:36 +0000
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id B78E0406060;  Sun,  1 Dec 2013 20:47:34 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Ted Lemon <ted.lemon@nominum.com>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Ted Lemon <ted.lemon@nominum.com> of "Sun, 01 Dec 2013 21:36:59 EST." <A775B456-E8F6-4111-AFB3-B51BB92ABFC7@nominum.com>
Mime-Version: 1.0
Date: Sun, 01 Dec 2013 20:47:34 -0800
Message-Id: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
X-CSC: 0
X-CHA: v=2.1 cv=DshvpgP+ c=1 sm=1 tr=0 a=OWgXOY7Tc8w5m7k7nGX6Zw==:117 a=OWgXOY7Tc8w5m7k7nGX6Zw==:17 a=Y6MaXbqoAAAA:8 a=g0qM3YM6AAAA:8 a=i5csljzfOyQA:10 a=sMgVN826qSoA:10 a=RocdOpmNmpoA:10 a=kj9zAlcOel0A:10 a=txtmwFjVAAAA:8 a=eTNsCY_WGJ8A:10 a=DGbFYnXxAAAA:8 a=pPXZawO-n647o8JyzaYA:9 a=zkSMJIqcxRd-kTPu:21 a=CatkSsKBnaLWpCuG:21 a=CjuIK1q_8ugA:10 a=bSyc6FVMW0oA:10
X-CTCH-RefID: str=0001.0A020209.529C10E9.001E, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-SA-Exim-Connect-IP: 64.29.147.17
X-SA-Exim-Rcpt-To: mayer@ntp.org, ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: hmurray@megapathdsl.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: hmurray@megapathdsl.net, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
a generic didn't-work?

How close does the time have to be for DNSSEC to work?

Could this problem be solved by setting up a bank of NTP servers at well 
known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
do that, I'd expect a serious problem would be overload because idiots would 
try to use them for normal NTP use rather than just getting off the ground.  
It might be possible to discourage that by making them return crappy time.


ted.lemon@nominum.com said:
> As for the home router use model, it may be that what you really want is for
> the home router to query for an FQDN-only DHCP option from the ISP DHCP
> server, and then resolve that FQDN and respond to DHCP clients on the
> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
> address is (one hopes) resolved either at query time or when its TTL
> expires, this ought to prevent a repeat of the firmware burn-in incident. 

Most ISPs already provide DNS servers for their customers.  How do their IP 
address get setup in home routers?  Could NTP servers piggyback on that 
mechanism if ISPs also provided NTP servers?



-- 
These are my opinions.  I hate spam.



_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 21:13:41 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46011AE42C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:13:41 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 KCyOjQqYqh58 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:13:40 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 40C621AE40B for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 21:13:40 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 6BBE186DABF for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 05:13:38 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 1BD4C86D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 05:13:31 +0000 (UTC)
Received: from exprod7og105.obsmtp.com ([64.18.2.163]) by mail1.ntp.org with smtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ted.Lemon@nominum.com>) id 1VnLp2-0005uD-P6 for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 05:13:31 +0000
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob105.postini.com ([64.18.6.12]) with SMTP ID DSNKUpwW+BtR8AcMv0cu665CT8QxhPaVQ5TG@postini.com; Sun, 01 Dec 2013 21:13:28 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 DE0D21B8224 for <ntpwg@lists.ntp.org>; Sun,  1 Dec 2013 21:13:27 -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 CFB62190043; Sun,  1 Dec 2013 21:13:27 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sun, 1 Dec 2013 21:13:27 -0800
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 2 Dec 2013 00:13:17 -0500
Message-ID: <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-SA-Exim-Connect-IP: 64.18.2.163
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, Bernie Volz <volz@cisco.com>, Olafur Gudmundsson <ogud@ogud.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 1, 2013, at 11:47 PM, Hal Murray <hmurray@megapathdsl.net> wrote:
> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
> a generic didn't-work?

A response with a bad clock fails to validate, which is the same as no response.

> How close does the time have to be for DNSSEC to work?

Closer than 1970.

> Could this problem be solved by setting up a bank of NTP servers at well 
> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
> do that, I'd expect a serious problem would be overload because idiots would 
> try to use them for normal NTP use rather than just getting off the ground.  
> It might be possible to discourage that by making them return crappy time.

History suggests otherwise.   If an IP address is hardcoded, it will get pummeled by devices that are too dumb to give up.

> Most ISPs already provide DNS servers for their customers.  How do their IP 
> address get setup in home routers?  Could NTP servers piggyback on that 
> mechanism if ISPs also provided NTP servers?

You mean DHCP?   Yes, that's what we're talking about.

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 21:27:49 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 320B31AE3FF for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:27:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=unavailable
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 UsTm8pcVL-oJ for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:27:48 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0738C1AE3E2 for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 21:27:48 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 266E186DB01 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 05:27:46 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 5D90486D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 05:27:40 +0000 (UTC)
Received: from static-108-1-140-117.bstnma.east.verizon.net ([108.1.140.117] helo=[10.10.10.102]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnM2i-0005zH-Q1; Mon, 02 Dec 2013 05:27:38 +0000
Message-ID: <529C1A31.2080900@ntp.org>
Date: Mon, 02 Dec 2013 00:27:13 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Hal Murray <hmurray@megapathdsl.net>,  Ted Lemon <ted.lemon@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
In-Reply-To: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 108.1.140.117
X-SA-Exim-Rcpt-To: hmurray@megapathdsl.net, ted.lemon@nominum.com, ntpwg@lists.ntp.org, dhcwg@ietf.org, volz@cisco.com, ogud@ogud.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 12/1/2013 11:47 PM, Hal Murray wrote:
> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
> a generic didn't-work?
> 
> How close does the time have to be for DNSSEC to work?
> 

That's a question that should be asked in the dnsext WG mailing list
(though technically the Working Group is now closed). Olafur and I
(apart from Ted who is IETF area director) are probably the only ones on
these lists who participate in that mailing list. Olafur was one of the
cochairs of the DNS ext working group.

The document does not describe the DNSSEC requirements for accurate time
and probably should so that it can be assessed in that light.
The ones I know about are RRSIG inception time and expiration time and
then there are certificate expiration date-times.

The proposal seems to suggest that a timestamp in 64-bit time_t be
distributed by DHCP. I'm not sure why not a NTP timestamp instead.
However most systems running a DNS server is likely to have a static
address in the first place and that is what DHCP distributes as
nameservers to query. Since they use static addresses do they
participate in DHCP services at all? And who says that the DHCP server
itself has accurate time?

> Could this problem be solved by setting up a bank of NTP servers at well 
> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
> do that, I'd expect a serious problem would be overload because idiots would 
> try to use them for normal NTP use rather than just getting off the ground.  
> It might be possible to discourage that by making them return crappy time.
> 

No, it would just overwhelm them. See the NIST time servers for an
example of heavy load.

> 
> ted.lemon@nominum.com said:
>> As for the home router use model, it may be that what you really want is for
>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>> server, and then resolve that FQDN and respond to DHCP clients on the
>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>> address is (one hopes) resolved either at query time or when its TTL
>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
> 
> Most ISPs already provide DNS servers for their customers.  How do their IP 
> address get setup in home routers?  Could NTP servers piggyback on that 
> mechanism if ISPs also provided NTP servers?

I wish they would provide NTP services in the same way. Unfortunately
although most ISP's will have NTP servers they do not usually tell their
customers about them and they certainly do not provide authenticated
packets like autokey.

Danny
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 21:37:54 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 57F321AE3FF for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:37:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 x7ao0AKBGO96 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 21:37:53 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 190601AE40E for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 21:37:53 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 49B8586DADD for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 05:37:51 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id C01EA86D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 05:37:45 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1VnMCF-00004p-O7; Mon, 02 Dec 2013 05:37:27 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Hal Murray <hmurray@megapathdsl.net>
In-reply-to: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net>
Comments: In-reply-to Hal Murray <hmurray@megapathdsl.net> message dated "Sun, 01 Dec 2013 20:47:34 -0800."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Mon, 02 Dec 2013 05:37:27 +0000
Message-Id: <E1VnMCF-00004p-O7@stenn.ntp.org>
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, Olafur Gudmundsson <ogud@ogud.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

We already know we want to discuss how long NTP will use an IP it got
from a DNS lookup.

We know there is no good API to get the TTL from this lookup.

An IP can easily be moved to another machine; there's no reason to have
a TTL for these.

On the other hand, there is a way to update ntpd's config file.

See http://support.ntp.org/Dev/GettingNtpdItsConfiguration for more
information, and we might want to look at "refreshing" URL-based
configurations on a schedule.

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Sun Dec  1 22:44:36 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B78071AE430 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 22:44:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 N2yA-0CvItgu for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Sun,  1 Dec 2013 22:44:35 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 34CAE1AE42E for <ntp-archives-ahFae6za@lists.ietf.org>; Sun,  1 Dec 2013 22:44:35 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 53CFF86DAE2 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 06:44:33 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 08BA686D4E1 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 06:44:23 +0000 (UTC)
Received: from mail-ie0-f171.google.com ([209.85.223.171]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <imp@bsdimp.com>) id 1VnNF0-0006No-FI for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 06:44:23 +0000
Received: by mail-ie0-f171.google.com with SMTP id ar20so19500896iec.2 for <ntpwg@lists.ntp.org>; Sun, 01 Dec 2013 22:44:16 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=hxuriIhvYgqb//cL5upEal9Qx4mZNSkISMD/QiiDoqU=; b=M5ni+20Z97trbvsYZMycBIWgBHpVw/8YC3Ez1d7gi04ZWkUInQThovp11hfhdzhRQr WwES0RvntEcVWPQo5rVA0uxdBm/9hIJvgnmDnmycXwmxMYETt5AZTu80oWK5yf4nCy0L eooR/JHduLKYUzZiSVjqTqhIQYw8eSMGA0ZVrm4xPGBE6nTlteBr0qJjFb9MUNMJxdop 1FJCgKU6W6bjP5pOFJe1iq7QOA/l/kYQjoVeQx64GoqTfQfBoIhVX4eCDMBmUjl2MSfr IqtlDMCvr00fD19pLSBHdFVhCJeyzheQvdgm+zDqAJVr5522K5IDQcacGcvk6GZBwFFR tG/Q==
X-Gm-Message-State: ALoCoQlcdhHUxxaFhgkI7Nbz8Af0goJOqYXoJmlJUuIjUDyQB5r0V3bnbiHlAKuOgThpw57Z3tvK
X-Received: by 10.43.106.198 with SMTP id dv6mr368644icc.51.1385966656579; Sun, 01 Dec 2013 22:44:16 -0800 (PST)
Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id u1sm64644385ige.1.2013.12.01.22.44.15 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sun, 01 Dec 2013 22:44:15 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
Date: Sun, 1 Dec 2013 23:44:14 -0700
Message-Id: <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 209.85.223.171
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: imp@bsdimp.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 1, 2013, at 10:13 PM, Ted Lemon wrote:
>> How close does the time have to be for DNSSEC to work?
> 
> Closer than 1970.

So 5 years in the future is no problem?

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 04:13:14 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 863241AE3F5 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 04:13:14 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.088
X-Spam-Level:
X-Spam-Status: No, score=-4.088 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] 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 Fu5L2w6LQTP6 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 04:13:13 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id F1EC51AE343 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 04:13:12 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id E0A2A86DABF for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 12:13:10 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id C869A86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 12:12:57 +0000 (UTC)
Received: from mail-pd0-x22d.google.com ([2607:f8b0:400e:c02::22d]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <ghane0@gmail.com>) id 1VnSMx-000Cbp-KV for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 12:12:57 +0000
Received: by mail-pd0-f173.google.com with SMTP id p10so17990743pdj.32 for <ntpwg@lists.ntp.org>; Mon, 02 Dec 2013 04:12:49 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=ZQ4IogRSQRzuxLogrj+B3LuXjhMBFim+6QpPRQy9b0g=; b=vhaQtzJCxfFiwTJSjIR3hD3lYn2+xP14g/mu8ElucP8VmHTh3s9DDkbUtwx1fQIPho lt2vSs0cv/R1Ske7QjoqsFT+vNP9CrlQBHJRfy1CXTcgjBPVnBZEAgcNoSllfnWz3Qoj QZQFK//Hb/QjsweDazXnwU4CqkXf1B25QJqvZ7rKh/lOqHc5Nvr0sG9AiYR8uajgIkId JlokGdS7s+menzfYdm+LTtAQlQqC1oFS5CmF8NIjvoRjVFHbL/Rfw98Yt7HCG9MGMjhJ wOlsFYyY8v9uMG7I0OdmyZWbTYJN+j5rP4zNWR5ih0lFn28KO+6kR2tsZLEHUVaBwV1r 71Mg==
X-Received: by 10.66.218.198 with SMTP id pi6mr67672766pac.107.1385986369597;  Mon, 02 Dec 2013 04:12:49 -0800 (PST)
MIME-Version: 1.0
Received: by 10.70.94.103 with HTTP; Mon, 2 Dec 2013 04:12:29 -0800 (PST)
In-Reply-To: <529BD4CF.6000408@ntp.org>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
From: Sanjeev Gupta <ghane0@gmail.com>
Date: Mon, 2 Dec 2013 20:12:29 +0800
Message-ID: <CAHZk5Wf4u4vrfVVO=jyPK=dtwYYYQvvbnYZuRX1+f0fH_M97VQ@mail.gmail.com>
To: mayer@ntp.org
X-SA-Exim-Connect-IP: 2607:f8b0:400e:c02::22d
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: ghane0@gmail.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, Olafur Gudmundsson <ogud@ogud.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: multipart/mixed; boundary="===============8279311008307240134=="
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

--===============8279311008307240134==
Content-Type: multipart/alternative; boundary=047d7b5d3ebe3937a804ec8c19b5

--047d7b5d3ebe3937a804ec8c19b5
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Dec 2, 2013 at 8:31 AM, Danny Mayer <mayer@ntp.org> wrote:

> The problem is that for NTP
> DNS names are preferred over IP addresses because that allows a server
> maintainer to retire an NTP server.
>

With the "server" directive, once the FQDN is resolved by the system
resolver, ntpd will continue with tah IP address, even if the FQDN changes,
till it is restarted.

We are talking only about time at startup, right?

Then, I do not see any issues if the DHCP server specifies a IP address; as
long as the server administrator can manage to check that the IP is valid
(for a short time in the future).

1. The DHCP server administrator SHOULD specify the IP address of a valid
NTP server.

or

2. DHCP Server software MUST resolve the NTP server name to an IP address
before providing it to clients

Or am I missing something even more basic?

-- 
Sanjeev Gupta
+65 98551208     http://www.linkedin.com/in/ghane

--047d7b5d3ebe3937a804ec8c19b5
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">=
On Mon, Dec 2, 2013 at 8:31 AM, Danny Mayer <span dir=3D"ltr">&lt;<a href=
=3D"mailto:mayer@ntp.org" target=3D"_blank">mayer@ntp.org</a>&gt;</span> wr=
ote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border=
-left:1px #ccc solid;padding-left:1ex">

<div id=3D":1nq" style=3D"overflow:hidden">The problem is that for NTP<br>
DNS names are preferred over IP addresses because that allows a server<br>
maintainer to retire an NTP server. </div></blockquote></div><br></div><div=
 class=3D"gmail_extra">With the &quot;server&quot; directive, once the FQDN=
 is resolved by the system resolver, ntpd will continue with tah IP address=
, even if the FQDN changes, till it is restarted.<br>

<br></div><div class=3D"gmail_extra">We are talking only about time at star=
tup, right?<br><br></div><div class=3D"gmail_extra">Then, I do not see any =
issues if the DHCP server specifies a IP address; as long as the server adm=
inistrator can manage to check that the IP is valid (for a short time in th=
e future). <br>

<br></div><div class=3D"gmail_extra">1. The DHCP server administrator SHOUL=
D specify the IP address of a valid NTP server.<br><br></div><div class=3D"=
gmail_extra">or<br><br></div><div class=3D"gmail_extra">2. DHCP Server soft=
ware MUST resolve the NTP server name to an IP address before providing it =
to clients<br>

</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Or am=
 I missing something even more basic?<br></div><div class=3D"gmail_extra"><=
br clear=3D"all"><div>-- <br>Sanjeev Gupta<br>+65 98551208=A0 =A0=A0 <a hre=
f=3D"http://www.linkedin.com/in/ghane">http://www.linkedin.com/in/ghane</a>=
</div>


</div></div>

--047d7b5d3ebe3937a804ec8c19b5--

--===============8279311008307240134==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--===============8279311008307240134==--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 06:38:36 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 678611AE49E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 06:38:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 L7F-pgl6wmad for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 06:38:35 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 051221AE49D for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 06:38:35 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 12F8F86DAA9 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 14:38:32 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4184986D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 14:38:22 +0000 (UTC)
Received: from exprod7og119.obsmtp.com ([64.18.2.16]) by mail1.ntp.org with smtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ted.Lemon@nominum.com>) id 1VnUdg-000DNI-LQ for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 14:38:22 +0000
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob119.postini.com ([64.18.6.12]) with SMTP ID DSNKUpybW8bxSKr6MfRJR9xJBltd3uZh3X5c@postini.com; Mon, 02 Dec 2013 06:38:20 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 86AD11B81DC for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 06:38:19 -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 7217E190043; Mon,  2 Dec 2013 06:38:19 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 06:38:19 -0800
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
Date: Mon, 2 Dec 2013 09:38:12 -0500
Message-ID: <E96CB645-2197-4475-B760-71E8B686C023@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com> <F53087EB-C5E0-4305-929D-5BFEA3C266AD@bsdimp.com>
To: Warner Losh <imp@bsdimp.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-SA-Exim-Connect-IP: 64.18.2.16
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 1:44 AM, Warner Losh <imp@bsdimp.com> wrote:
> So 5 years in the future is no problem?

I was being mildly facetious, since this is a question that's pretty easy to answer, but difficult to answer precisely.   The answer depends on the zone configuration, but generally speaking "within days" is probably good enough.   See http://tools.ietf.org/html/rfc6781#section-4.4.2.2

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 07:24:51 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C1911AE49D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 07:24:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] autolearn=unavailable
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 SQHthD6t0-vu for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 07:24:49 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 161771AE493 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 07:24:49 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1D78986DADC for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 15:24:47 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 713F286D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 15:24:39 +0000 (UTC)
Received: from [198.22.153.36] (helo=[10.2.64.86]) by mail1.ntp.org with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <mayer@ntp.org>) id 1VnVMP-000Dj4-RG; Mon, 02 Dec 2013 15:24:36 +0000
Message-ID: <529CA616.3010402@ntp.org>
Date: Mon, 02 Dec 2013 10:24:06 -0500
From: Danny Mayer <mayer@ntp.org>
Organization: NTP
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
In-Reply-To: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
X-Enigmail-Version: 1.6
X-SA-Exim-Connect-IP: 198.22.153.36
X-SA-Exim-Rcpt-To: ogud@ogud.com, hmurray@megapathdsl.net, ted.lemon@nominum.com, ntpwg@lists.ntp.org, dhcwg@ietf.org, volz@cisco.com
X-SA-Exim-Mail-From: mayer@ntp.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: mayer@ntp.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 12/2/2013 8:47 AM, Olafur Gudmundsson wrote:
> 
> On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:
> 
>> On 12/1/2013 11:47 PM, Hal Murray wrote:
>>> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
>>> a generic didn't-work?
>>>
>>> How close does the time have to be for DNSSEC to work?
>>>
>>
>> That's a question that should be asked in the dnsext WG mailing list
>> (though technically the Working Group is now closed). Olafur and I
>> (apart from Ted who is IETF area director) are probably the only ones on
>> these lists who participate in that mailing list. Olafur was one of the
>> cochairs of the DNS ext working group.
>>
>> The document does not describe the DNSSEC requirements for accurate time
>> and probably should so that it can be assessed in that light.
>> The ones I know about are RRSIG inception time and expiration time and
>> then there are certificate expiration date-times.
>>
>> The proposal seems to suggest that a timestamp in 64-bit time_t be
>> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
>> However most systems running a DNS server is likely to have a static
>> address in the first place and that is what DHCP distributes as
>> nameservers to query. Since they use static addresses do they
>> participate in DHCP services at all? And who says that the DHCP server
>> itself has accurate time?
>>
> 
> Danny, Thanks for the kind introduction 
> 
> The reason for time_t is the dhcp-client can feed that directly into following call:
> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)
> 
> If there is better construct I wold be happy to update the draft with that. 
> 
> Be careful when you say "most systems running a DNS server" 
> are you talking about resolver or authoritative server.  
> 

I actually mostly meant resolvers and authorative servers are really no
different in the sense being discussed here.

> In the second case you are right they are static and frequently well provisioned with good bandwidth, and 
> at boot time the system has good idea why the current time is, but for all practical purposes unless they are signing
> on the fly they do not need accurate time. 
> 
> ON THE OTHER HAND, resolvers and X.509 certificate checking is distributed and can take 
> place on any device. As I said in another message DNS resolution is being pushed to the edge 
> as devices that migrate between networks cannot count on the "local resolvers" to be "DNSSEC ready" 
> 
I doubt that the number of "local resolvers" used by the general
populace that can support DNSSEC reach even .1% today, never mind
whether the server has it enabled.

> You are right we can not count on the DHCP server to have good time, thus any DHCP server answering 
> with the proposed option would need to make sure it has "decent current time", that is the reason I say in the
> draft that the time should be within 10 minutes. 
> When playing with cheap home routers I discovered that the devices can easily drift an hour a day, if NTP is not
> invoked regularly, most of these devices just use 'ntpdate' and frequently run it from startup script once. 
> 
>>> Could this problem be solved by setting up a bank of NTP servers at well 
>>> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
>>> do that, I'd expect a serious problem would be overload because idiots would 
>>> try to use them for normal NTP use rather than just getting off the ground.  
>>> It might be possible to discourage that by making them return crappy time.
>>>
>>
>> No, it would just overwhelm them. See the NIST time servers for an
>> example of heavy load.
>>
>>>
>>> ted.lemon@nominum.com said:
>>>> As for the home router use model, it may be that what you really want is for
>>>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>>>> server, and then resolve that FQDN and respond to DHCP clients on the
>>>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>>>> address is (one hopes) resolved either at query time or when its TTL
>>>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
>>>
>>> Most ISPs already provide DNS servers for their customers.  How do their IP 
>>> address get setup in home routers?  Could NTP servers piggyback on that 
>>> mechanism if ISPs also provided NTP servers?
>>
>> I wish they would provide NTP services in the same way. Unfortunately
>> although most ISP's will have NTP servers they do not usually tell their
>> customers about them and they certainly do not provide authenticated
>> packets like autokey.
>>
>> Danny
> 
> Will a hotel network provide NTP server, and would you trust it? 
> Will a coffee shop provide NTP server ??? 
> 

I would consider them no better than the ISP's. They only provide basic
services and almost certainly not NTP. But then how many applications
out there will demand DNSSEC authenticated information? Generally there
is no API to specify that from an application. When this gets into
browser software and banks give DNSSEC authenticated addresses then it
might take off.

Danny


> 	Olafur
> 
> 
> 

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 07:32:22 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 285FA1AE49C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 07:32:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 CexDvgAaFKER for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 07:32:19 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 38C351AE499 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 07:32:19 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 415EC86D763 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 15:32:17 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 01E2186D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 15:32:12 +0000 (UTC)
Received: from mail-ie0-f172.google.com ([209.85.223.172]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <imp@bsdimp.com>) id 1VnVTm-000DmT-7B for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 15:32:11 +0000
Received: by mail-ie0-f172.google.com with SMTP id qd12so21404968ieb.17 for <ntpwg@lists.ntp.org>; Mon, 02 Dec 2013 07:32:04 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=9SR3GvhEptT54gn7lUwnPRYSCeME0P8YR+HWO1DQY/s=; b=jV9Ej5qzxYOR1WrKqFCHPFAQVElI8BIS3bi5beVnS7LRPDnbCkH1xKEcNVp5X/vVRJ uP4ozcgRDTDBe/ZPspjUxmXqDhAMNiRTJXhMsfyTQUkCdG22fGbHuXqp0uheYY6Iagzu 3BxlMbEJEE1SCtSChYbOpAtnFBvQ17OdWM+Qb8aZNpUI2FczWZD2frTlIQH/gjzzXy2k 8rLv/GKojptHIeN7WvmsEZ9n3Kom6dUwbadFwOaJDCltf1v2u4pXfMHLT0T8X8LZsK0h opNmaIpA9WiogGvDEBXu70nOI6aiwCIxXU5i5Ii10rccouYd9877FdFktob/hpNXbsfk OzXQ==
X-Gm-Message-State: ALoCoQnu4XNZS9Gh9HqNfjkvJSCOyqCcXrG3mjVSxCIs+3WERkg7Ba2a0yvo6q3LTMEaSrRn6KJh
X-Received: by 10.50.16.68 with SMTP id e4mr18460998igd.12.1385998324247; Mon, 02 Dec 2013 07:32:04 -0800 (PST)
Received: from 53.imp.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id da14sm26843873igc.1.2013.12.02.07.32.03 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 07:32:03 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <529CA616.3010402@ntp.org>
Date: Mon, 2 Dec 2013 08:32:02 -0700
Message-Id: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 209.85.223.172
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: imp@bsdimp.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 8:24 AM, Danny Mayer wrote:
>> Danny, Thanks for the kind introduction 
>> 
>> The reason for time_t is the dhcp-client can feed that directly into following call:
>> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)

During a leap second, the value of time_t is not well defined because by definition leap seconds don't happen in time_t/POSIX time scale (don't happen -- well don't consume space in the time_t timescale is more pedantically correct). Obscure point likely worth noting...  But using a NTP time stamp doesn't save you, since during a leap second its value is well defined, but the same as another second (ntp distinguishes in bits set in other parts of the header). Assuming the tolerance for this application is >> 1s, this won't matter, but might be worth specifying that during a leap second, the value returned shall be either the value of the prior second or the value of the next second to make it conform to most current usage.

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 09:02:19 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 006F81ACCE8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 09:02:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.801
X-Spam-Level:
X-Spam-Status: No, score=-1.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001] 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 T75hHVFSn3He for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 09:02:17 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 135781A1F76 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 09:02:17 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 18E5686DAF3 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 17:02:15 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 9347886D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 17:02:04 +0000 (UTC)
Received: from elasmtp-galgo.atl.sa.earthlink.net ([209.86.89.61]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <tglassey@earthlink.net>) id 1VnWsk-000EJQ-83 for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 17:02:04 +0000
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=dk20050327; d=earthlink.net; b=Pdl3de3z/ihHCVJN1kWouLcV6lalohWa+jM0RNlp8QkIAEphpzUjFLhvnvzDYnTp; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-ELNK-Trace:X-Originating-IP;
Received: from [67.180.133.21] (helo=localhost.localdomain) by elasmtp-galgo.atl.sa.earthlink.net with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.67) (envelope-from <tglassey@earthlink.net>) id 1VnWsd-0005Og-HH for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 12:01:55 -0500
Message-ID: <529CBD01.3010303@earthlink.net>
Date: Mon, 02 Dec 2013 09:01:53 -0800
From: TSG - personal <tglassey@earthlink.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131030 Thunderbird/17.0.10
MIME-Version: 1.0
To: ntpwg@lists.ntp.org
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
In-Reply-To: <529BD4CF.6000408@ntp.org>
X-ELNK-Trace: 01b7a7e171bdf5911aa676d7e74259b7b3291a7d08dfec79c943fbc76109c25575394d9f319d79ef350badd9bab72f9c350badd9bab72f9c350badd9bab72f9c
X-Originating-IP: 67.180.133.21
X-SA-Exim-Connect-IP: 209.86.89.61
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: tglassey@earthlink.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="windows-1252"; Format="flowed"
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On 12/01/2013 04:31 PM, Danny Mayer wrote:

Danny many entities running DNSSEC dont have the option to continue =

operations until such time as they get better time data under the certs. =

This is a policy level thing so its not something that they can =

technically ignore either.

Todd
> On 12/1/2013 5:29 PM, Ted Lemon wrote:
>> On Dec 1, 2013, at 5:05 PM, Olafur Gudmundsson <ogud@ogud.com> wrote:
>>> The "threat" the document is trying to address, device wants to
> DNSSEC or CERT validation but clock is far off thus VALID credentials
> fail validation.
>> Ah, thanks for explaining. This is what I was missing=97you're not
>> doing
> this to avoid a threat at all, but rather to simply make DNSSEC work in
> a possibly non-secure mode until such time as you can bootstrap better
> time information.
>> This would be worth mentioning in the introduction and/or the
>> security
> considerations section. You allude to it in the security considerations,
> but it's pretty oblique.
>> It is worth pointing out that NTP doesn't actually need DNS to
> work=97DHCP can deliver NTP server addresses as IP addresses. That said,
> this option seems to add value, since there is no guarantee that devices
> that implement the existing DHCP NTP will not send FQDNs rather than IP
> addresses.
>
> I had a long discussion with Bernie over the issue of delivering NTP IP
> addresses via DHCP. We understand the issues you raised concerning
> DNSSEC and have no disagreement about that. The problem is that for NTP
> DNS names are preferred over IP addresses because that allows a server
> maintainer to retire an NTP server. With an IP address there is no
> chance that your local instance will know about this and continue to
> bombard the old address. Moreover the newer pool option cannot be used
> to any advantage.
>
> When was the last time you looked at your NTP configuration and verified
> that all of the servers listed are still valid? How often will DHCP
> servers do this as a matter of course before providing such
> provisioning? We have systems that are being bombarded by requests even
> though no NTP server is responding to queries. We have plenty of
> evidence of this. Even worse we have seen home routers which have
> hard-coded IP addresses for NTP servers embedded. How long are those
> going to be in operation?
>
> I think we need to figure out how to get around the Catch-22 situation
> of DNSSEC requiring relatively good time and NTP wanting to be able to
> use DNS to find valid NTP servers.
>
> We need a joint agreement on how to deal with this between DHCP and NTP
> Working Groups assuming that is a viable option in the first place.
> RFC5908 was not a good indication of this.
>
> Danny
>
> _______________________________________________
> ntpwg mailing list
> ntpwg@lists.ntp.org
> http://lists.ntp.org/listinfo/ntpwg
>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 09:13:07 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A91AD1AD845 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 09:13:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 hUMjuHmqUVm1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 09:13:06 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0F2CF1AD7C2 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 09:13:06 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1391086DAF7 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 17:13:04 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 7917786D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 17:12:58 +0000 (UTC)
Received: from exprod7og104.obsmtp.com ([64.18.2.161]) by mail1.ntp.org with smtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ted.Lemon@nominum.com>) id 1VnX3I-000EOG-LM for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 17:12:58 +0000
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob104.postini.com ([64.18.6.12]) with SMTP ID DSNKUpy/mEBKf7aQXl5XBcSapD93ZrbbAmP2@postini.com; Mon, 02 Dec 2013 09:12:56 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 EA7731B82E6 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 09:12:55 -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 DE797190043; Mon,  2 Dec 2013 09:12:55 -0800 (PST)
Received: from [10.0.10.40] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 09:12:55 -0800
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
Date: Mon, 2 Dec 2013 12:12:48 -0500
Message-ID: <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
To: Warner Losh <imp@bsdimp.com>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-SA-Exim-Connect-IP: 64.18.2.161
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 10:32 AM, Warner Losh <imp@bsdimp.com> wrote:
> Assuming the tolerance for this application is >> 1s, this won't matter, but might be worth specifying that during a leap second, the value returned shall be either the value of the prior second or the value of the next second to make it conform to most current usage.

I think the expectation is that the time will be updated with a more accurate mechanism later, and an error of 1s is not worth worrying about for typical devices, so this is almost certainly overkill.

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 10:13:20 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6935B1AD9B8 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 10:13:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 IkPRHP6YmQwa for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 10:13:18 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 795D81AD959 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 10:13:18 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 738D786DAEC for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 18:13:16 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id E223086D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 18:13:07 +0000 (UTC)
Received: from mail-ie0-f174.google.com ([209.85.223.174]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <imp@bsdimp.com>) id 1VnXzV-000Eic-UZ for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 18:13:07 +0000
Received: by mail-ie0-f174.google.com with SMTP id at1so21479277iec.33 for <ntpwg@lists.ntp.org>; Mon, 02 Dec 2013 10:13:00 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=cfYwbFBhUBk+5kYSFEOqd73pn2n2nOvfZ+S7Tc8+O7A=; b=Gc6jL9zhFjqAtp7MbAAuitX+00WGwCuw8qbpyEvzO2TYoywkEr5IvYMAqD6BZWDqz+ dbrOaaI+3Ooo4RwvWrKZ4AsM5MJ9fJsx1+mueXGLwdfpbhPgj20vWSQnNY/2wSi3TL8q AICtFqz3EEA8eJaU0TJsZRWfPfKB0EEnRMDkAlgRre8Y4zsA5l3knRV+LxBrd5l48xS3 hm9jJ6BD49CNU4HjcrmQw24gT3dJek2g5j+y/cxztMjOWXsLzlnyP/OVke89dv2FUg18 1igMRGxES6r3zVwaQ75bfuJ1QRw7k3QnfZOt9G21zKn0Oh2e6Cn67RpZizPcvO23dog+ 8g8A==
X-Gm-Message-State: ALoCoQk+arI5kK+R/ncENJm13gGdcZ24/XHL9PygWl+duCQAA8VwxDwVIIiurzGynLh2N6G/gbxl
X-Received: by 10.42.42.132 with SMTP id t4mr1929976ice.90.1386007980059; Mon, 02 Dec 2013 10:13:00 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id x5sm67786946iga.6.2013.12.02.10.12.59 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 10:12:59 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
Date: Mon, 2 Dec 2013 11:12:57 -0700
Message-Id: <7C1A1F32-EED7-4990-A550-DB66BAB6AAD4@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <4AA650D3-2AD2-4C83-8450-DC3926AC9416@nominum.com>
To: Ted Lemon <ted.lemon@nominum.com>
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 209.85.223.174
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: imp@bsdimp.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 10:12 AM, Ted Lemon wrote:

> On Dec 2, 2013, at 10:32 AM, Warner Losh <imp@bsdimp.com> wrote:
>> Assuming the tolerance for this application is >> 1s, this won't matter, but might be worth specifying that during a leap second, the value returned shall be either the value of the prior second or the value of the next second to make it conform to most current usage.
> 
> I think the expectation is that the time will be updated with a more accurate mechanism later, and an error of 1s is not worth worrying about for typical devices, so this is almost certainly overkill.

This isn't to prevent an error of a second, but to bound the error to a second by adopting the main work arounds that are in practice today which do that.

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 10:57:09 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BCE91AD687 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 10:57:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 oKjtxEbaeOx0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 10:57:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 46CBC1ACCDF for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 10:57:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 420E086D60E for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 18:57:06 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id DA6EB86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 18:56:57 +0000 (UTC)
Received: from mail223c25.carrierzone.com ([64.29.147.237]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <hmurray@megapathdsl.net>) id 1VnYfs-000Ex5-Th for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 18:56:57 +0000
X-POP-User: hmurray@megapathdsl.net
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by mail223c25.carrierzone.com (8.13.6/8.13.1) with ESMTP id rB2IunTi027496 for <ntpwg@lists.ntp.org>; Mon, 2 Dec 2013 18:56:50 +0000
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id 91031406060;  Mon,  2 Dec 2013 10:56:48 -0800 (PST)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Ted Lemon <ted.lemon@nominum.com>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Ted Lemon <ted.lemon@nominum.com> of "Mon, 02 Dec 2013 00:13:17 EST." <D5CCC8A9-10FF-4D57-AB42-D39AB4D8730F@nominum.com>
Mime-Version: 1.0
Date: Mon, 02 Dec 2013 10:56:48 -0800
Message-Id: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
X-CSC: 0
X-CHA: v=2.1 cv=aKDJ99Nm c=1 sm=1 tr=0 a=OWgXOY7Tc8w5m7k7nGX6Zw==:117 a=OWgXOY7Tc8w5m7k7nGX6Zw==:17 a=Y6MaXbqoAAAA:8 a=g0qM3YM6AAAA:8 a=i5csljzfOyQA:10 a=sMgVN826qSoA:10 a=RocdOpmNmpoA:10 a=kj9zAlcOel0A:10 a=txtmwFjVAAAA:8 a=eTNsCY_WGJ8A:10 a=DGbFYnXxAAAA:8 a=KJE_JL5bt8-WbQPDp2wA:9 a=h-Le4KOJTSLWos5y:21 a=QawYSIss2mX5EQef:21 a=CjuIK1q_8ugA:10 a=bSyc6FVMW0oA:10
X-CTCH-RefID: str=0001.0A020203.529CD7F2.01C4, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: 
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-SA-Exim-Connect-IP: 64.29.147.237
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: hmurray@megapathdsl.net
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, hmurray@megapathdsl.net, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

ted.lemon@nominum.com said:
[Context is NTP servers next to root DNS servers.]
> History suggests otherwise.   If an IP address is hardcoded, it will get
> pummeled by devices that are too dumb to give up. 

That's why I was suggesting a crappy clock.  Can we get something that is 
crappy enough that nobody would use it for anything other than getting off 
the ground yet still good enough for DNSSEC to work?


>> Most ISPs already provide DNS servers for their customers.  How do their 
IP
>> address get setup in home routers?  Could NTP servers piggyback on that 
>> mechanism if ISPs also provided NTP servers?
> You mean DHCP?   Yes, that's what we're talking about. 

Are there two layers of DHCP?  ISP to home router and home router to PC.

If ISPs ran NTP servers, say next to their DNS servers, could DHCP provide IP 
Addresses for both DNS and NTP servers over both hops?

Is it reasonable to trust an ISP's NTP servers?


-- 
These are my opinions.  I hate spam.



_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 12:00:36 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EF311ADF32 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:00:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 91_6sq_tXTH0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:00:33 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 01C671ADF52 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 12:00:28 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id EB56686DAAD for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 20:00:26 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 9B09E86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 20:00:16 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1VnZdi-0000fA-CY; Mon, 02 Dec 2013 19:58:42 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Warner Losh <imp@bsdimp.com>
In-reply-to: <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com> message dated "Mon, 02 Dec 2013 08:32:02 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Mon, 02 Dec 2013 19:58:42 +0000
Message-Id: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Warner Losh writes:
>>> The reason for time_t is the dhcp-client can feed that directly into
>>> following call: settimeofday(const struct timeval *tp, const struct
>>> timezone *tzp)
> 
> During a leap second, the value of time_t is not well defined because
> by definition leap seconds don't happen in time_t/POSIX time scale
> (don't happen -- well don't consume space in the time_t timescale is
> more pedantically correct). Obscure point likely worth noting...  But
> using a NTP time stamp doesn't save you, since during a leap second
> its value is well defined, but the same as another second (ntp
> distinguishes in bits set in other parts of the header). Assuming the
> tolerance for this application is >> 1s, this won't matter, but might
> be worth specifying that during a leap second, the value returned
> shall be either the value of the prior second or the value of the next
> second to make it conform to most current usage.

It's actually fuzzier than that, and this situation (which is handled
differently with ntpd under unix, ntpd under windows, and on systems
that "smear" the leap second over a longer period) is one of the cases
handled by the General Timestamp API project at Network Time Foundation,
described at http://nwtime.org/projects/timestamp-api/ .

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 12:05:09 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B61441ADF10 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:05:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 9LoMyHzQIfA4 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:05:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 2A8FD1ADF46 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 12:05:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 0E61F86DAD5 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 20:05:05 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id AD9F886D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 20:05:01 +0000 (UTC)
Received: from exprod7og101.obsmtp.com ([64.18.2.155]) by mail1.ntp.org with smtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <Ted.Lemon@nominum.com>) id 1VnZjn-000FVt-MH for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 20:05:01 +0000
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob101.postini.com ([64.18.6.12]) with SMTP ID DSNKUpzn6zXwoFOqgyEugn96ByyxsQOChN7r@postini.com; Mon, 02 Dec 2013 12:04:59 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 0F0131B82C6 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 12:04:59 -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 03B63190043; Mon,  2 Dec 2013 12:04:59 -0800 (PST)
Received: from [192.168.1.3] (192.168.1.10) by CAS-01.WIN.NOMINUM.COM (192.168.1.100) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 2 Dec 2013 12:04:58 -0800
MIME-Version: 1.0 (Mac OS X Mail 7.0 \(1822\))
From: Ted Lemon <ted.lemon@nominum.com>
In-Reply-To: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 2 Dec 2013 15:04:54 -0500
Message-ID: <19044894-42C6-498C-88E5-85FCAE4C5F00@nominum.com>
References: <20131202185648.91031406060@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.1822)
X-Originating-IP: [192.168.1.10]
X-SA-Exim-Connect-IP: 64.18.2.155
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: Ted.Lemon@nominum.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 1:56 PM, Hal Murray <hmurray@megapathdsl.net> wrote:
> ted.lemon@nominum.com said:
> [Context is NTP servers next to root DNS servers.]
>> History suggests otherwise.   If an IP address is hardcoded, it will get
>> pummeled by devices that are too dumb to give up. 
> 
> That's why I was suggesting a crappy clock.  Can we get something that is 
> crappy enough that nobody would use it for anything other than getting off 
> the ground yet still good enough for DNSSEC to work?

No.   Think about this seriously.   Who is going to tweak this?   The end-user?   This isn't realistic.   We had millions of home gateways DDOSing a university NTP server for years because the router vendor burned the IP address of the NTP server into the firmware.   I doubt anybody got decent time out of this arrangement, but nevertheless it persisted.

> Are there two layers of DHCP?  ISP to home router and home router to PC.

Yes.

> If ISPs ran NTP servers, say next to their DNS servers, could DHCP provide IP 
> Addresses for both DNS and NTP servers over both hops?

Yes.

> Is it reasonable to trust an ISP's NTP servers?

See my first response on this thread: http://www.ietf.org/mail-archive/web/dhcwg/current/msg15039.html


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 12:09:28 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5321ADF56 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:09:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 MfAqEdqXzQX7 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 12:09:26 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 03B0F1ADF52 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 12:09:26 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 000D286DAD7 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 20:09:23 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id EB44086D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 20:09:17 +0000 (UTC)
Received: from mail-ie0-f175.google.com ([209.85.223.175]) by mail1.ntp.org with esmtps (TLSv1:RC4-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <imp@bsdimp.com>) id 1VnZnv-000FYt-0O for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 20:09:17 +0000
Received: by mail-ie0-f175.google.com with SMTP id x13so21321603ief.20 for <ntpwg@lists.ntp.org>; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=nD9qyZRQWP+8a0aK7r3rOhfixl0Br4i8b0ZCbbROZ5g=; b=UjaE3uRzHC7InQy/AZlex8Bm6JSfmblmvCn/EWGIDoymmljHzhkmQ/hpJG5zBmO3iu vmADI3feIGC6EFGhFWRWMl2uDptVXSQo5MZ9YwNaFP6naWKFJaOdC1Vzq/KywTBi5m3X EkR3HFvWLFVaibL6nbKoy+tUocSLGqO0cAjt6o3Pl1FmSrPZpd7lVBycudV+USGLzfn2 lXYPjwa780PBymQ6rdCT6gm9LQeeiSDL9U9AavRVncLXrnVqvXkCgL0sstlH/QWi8yfV Wo+gS6+h3fzwkcpye+MH5JTZAjZCbot9znwFfGJxeqSlZ2YM1apm7O5obN3MhhBEBE+s b4sA==
X-Gm-Message-State: ALoCoQm+FTgTPRchdVDhnUjOibkg6EuJoRkjNLq7mzemFPSccpxTv5oWsn6u/F7DGUHagr1RnhdA
X-Received: by 10.50.30.66 with SMTP id q2mr19728670igh.17.1386014949269; Mon, 02 Dec 2013 12:09:09 -0800 (PST)
Received: from fusionlt2834a.int.fusionio.com ([209.117.142.2]) by mx.google.com with ESMTPSA id j16sm67621228igf.6.2013.12.02.12.09.08 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 02 Dec 2013 12:09:08 -0800 (PST)
Mime-Version: 1.0 (Apple Message framework v1085)
From: Warner Losh <imp@bsdimp.com>
In-Reply-To: <E1VnZdi-0000fA-CY@stenn.ntp.org>
Date: Mon, 2 Dec 2013 13:09:06 -0700
Message-Id: <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org>
To: Harlan Stenn <stenn@ntp.org>
X-Mailer: Apple Mail (2.1085)
X-SA-Exim-Connect-IP: 209.85.223.175
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: imp@bsdimp.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 12:58 PM, Harlan Stenn wrote:

> Warner Losh writes:
>>>> The reason for time_t is the dhcp-client can feed that directly into
>>>> following call: settimeofday(const struct timeval *tp, const struct
>>>> timezone *tzp)
>> 
>> During a leap second, the value of time_t is not well defined because
>> by definition leap seconds don't happen in time_t/POSIX time scale
>> (don't happen -- well don't consume space in the time_t timescale is
>> more pedantically correct). Obscure point likely worth noting...  But
>> using a NTP time stamp doesn't save you, since during a leap second
>> its value is well defined, but the same as another second (ntp
>> distinguishes in bits set in other parts of the header). Assuming the
>> tolerance for this application is >> 1s, this won't matter, but might
>> be worth specifying that during a leap second, the value returned
>> shall be either the value of the prior second or the value of the next
>> second to make it conform to most current usage.
> 
> It's actually fuzzier than that, and this situation (which is handled
> differently with ntpd under unix, ntpd under windows, and on systems
> that "smear" the leap second over a longer period) is one of the cases
> handled by the General Timestamp API project at Network Time Foundation,
> described at http://nwtime.org/projects/timestamp-api/ .

Actually, in all those cases it is within a second of the 'real' time, hence specifying that it should be one second or the other seems appropriate. The timestamp APIs are for sub-second resolution, while the time_t in this protocol has only a second resolution... The main point is that it should be (a) specified to be what's going to most likely happen (or keep bounds on the error)  and (b) something sane that doesn't introduce errors > tolerance of the protocol. Having it be completely unspecified is a mistake, since -1 could be returned...

Warner

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 13:33:49 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A3F361ADF53 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 13:33:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 rWSr-6jN4ZR1 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 13:33:48 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 490721ADF4F for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 13:33:48 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 3DE7686DADE for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 21:33:46 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 75EA686D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 21:33:31 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vnb6D-0000lV-Gy; Mon, 02 Dec 2013 21:32:13 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Warner Losh <imp@bsdimp.com>
In-reply-to: <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com>
Comments: In-reply-to Warner Losh <imp@bsdimp.com> message dated "Mon, 02 Dec 2013 13:09:06 -0700."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Mon, 02 Dec 2013 21:32:13 +0000
Message-Id: <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Warner Losh writes:
> On Dec 2, 2013, at 12:58 PM, Harlan Stenn wrote:
>> It's actually fuzzier than that, and this situation (which is handled
>> differently with ntpd under unix, ntpd under windows, and on systems
>> that "smear" the leap second over a longer period) is one of the
>> cases handled by the General Timestamp API project at Network Time
>> Foundation, described at http://nwtime.org/projects/timestamp-api/ .
> 
> Actually, in all those cases it is within a second of the 'real' time,
> hence specifying that it should be one second or the other seems
> appropriate. The timestamp APIs are for sub-second resolution, while the
> time_t in this protocol has only a second resolution... The main point
> is that it should be (a) specified to be what's going to most likely
> happen (or keep bounds on the error)  and (b) something sane that
> doesn't introduce errors > tolerance of the protocol. Having it be
> completely unspecified is a mistake, since -1 could be returned...

I'd suspect that usually 1 second will be the ballpark, but it's pretty
easy to find situations where the system clock is out by more than that.

I mention the General Timestamp API because that effort is looking at
use cases like this one from a larger persepective.

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 14:03:50 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3966C1ADF97 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 14:03:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.791
X-Spam-Level:
X-Spam-Status: No, score=-1.791 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, RP_MATCHES_RCVD=-0.001, T_DKIM_INVALID=0.01] autolearn=no
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 MSrDAHpMQ-dO for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 14:03:49 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 092E51ADF96 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 14:03:49 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id F073286DAEB for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 22:03:46 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id C243586D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 22:03:37 +0000 (UTC)
Received: from mx.pao1.isc.org ([2001:4f8:0:2::2b]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <marka@isc.org>) id 1VnbaZ-000GBN-7h for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 22:03:37 +0000
Received: from mx.pao1.isc.org (localhost [127.0.0.1]) by mx.pao1.isc.org (Postfix) with ESMTP id 47B33C94C0; Mon,  2 Dec 2013 22:03:13 +0000 (UTC) (envelope-from marka@isc.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isc.org; s=dkim2012; t=1386021809; bh=xaXM16kQLJhvMxMUPLWuhXhPSHitZKWkP9oD0TH0Ko0=; h=To:Cc:From:References:Subject:In-reply-to:Date; b=b1+cMHZapIZCdDaamQbo4Hf1X9sFBVN9g9NrEUdcuPvT5wlQ996rb1JtcWVCSzwO6 5GPiPdi4YAjndWAH8zsmshtJ0xTy/U/4MsBlZBGGhM0cBPH0wtXkkweN4GY8kRwB+V eiEQ2ldqbZ93BZ1HdtBP3SmZrjXqs45pLcEWxG7w=
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.pao1.isc.org (Postfix) with ESMTP; Mon,  2 Dec 2013 22:03:13 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id A24D2160436; Mon,  2 Dec 2013 22:10:55 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 5D36316034F; Mon,  2 Dec 2013 22:10:55 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id 85669B04BBE; Tue,  3 Dec 2013 09:03:11 +1100 (EST)
To: Harlan Stenn <stenn@ntp.org>
From: Mark Andrews <marka@isc.org>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com> <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
In-reply-to: Your message of "Mon, 02 Dec 2013 21:32:13 -0000." <E1Vnb6D-0000lV-Gy@stenn.ntp.org>
Date: Tue, 03 Dec 2013 09:03:11 +1100
Message-Id: <20131202220311.85669B04BBE@rock.dv.isc.org>
X-DCC--Metrics: post.isc.org; whitelist
X-SA-Exim-Connect-IP: 2001:4f8:0:2::2b
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: marka@isc.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

The inception and expiration times in RRSIGs is specified as seconds
since 00:00:00 Jan 1 1970 UTC excluding leap seconds modulo 2^32.

There are no recommended fudge factors to use when evaluating these
times though named sets the expire time to 3600 seconds in the past
by default when generating RRSIGs.  I believe the other signers do
similar.  I've considered making the inception timestamp a whole
day in the past to cope with badly set timezones.

The signature validity intervals are on the order of days.  Named
defaults to 30 days.  They are regenerated about a week before they
are due expire if not already regenerated due to zone content
changes.  The records should expire from caches before they become
invalid if re-signing is being done properly.

So if the validator and the signer are both within 30 minutes of
the true time validation should succeed.

Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  2 14:15:51 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1221ADFA6 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 14:15:51 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.88
X-Spam-Level:
X-Spam-Status: No, score=-0.88 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MISSING_HEADERS=1.021, RP_MATCHES_RCVD=-0.001] autolearn=no
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 g9v58mK_xXXN for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  2 Dec 2013 14:15:50 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 223991ADFB7 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 14:15:50 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1732986DAA8 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  2 Dec 2013 22:15:48 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 8865B86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 22:15:41 +0000 (UTC)
Received: from mx.ams1.isc.org ([199.6.1.65]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <marka@isc.org>) id 1VnbmF-000GGA-QF for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 22:15:41 +0000
Received: from zmx1.isc.org (zmx1.isc.org [149.20.0.20]) by mx.ams1.isc.org (Postfix) with ESMTP id D130A2383B6; Mon,  2 Dec 2013 22:15:21 +0000 (UTC) (envelope-from marka@isc.org)
Received: from zmx1.isc.org (localhost [127.0.0.1]) by zmx1.isc.org (Postfix) with ESMTP id CB52D160436; Mon,  2 Dec 2013 22:23:03 +0000 (UTC)
Received: from rock.dv.isc.org (c211-30-183-50.carlnfd1.nsw.optusnet.com.au [211.30.183.50]) by zmx1.isc.org (Postfix) with ESMTPSA id 97C6D16034F; Mon,  2 Dec 2013 22:23:03 +0000 (UTC)
Received: from rock.dv.isc.org (localhost [IPv6:::1]) by rock.dv.isc.org (Postfix) with ESMTP id BF773B04CC1; Tue,  3 Dec 2013 09:15:19 +1100 (EST)
From: Mark Andrews <marka@isc.org>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org> <19575403-444E-4CBA-8818-5F46328787AE@bsdimp.com> <E1VnZdi-0000fA-CY@stenn.ntp.org> <220ED02D-AE73-436F-A81F-BDF54611173B@bsdimp.com> <E1Vnb6D-0000lV-Gy@stenn.ntp.org> <20131202220311.85669B04BBE@rock.dv.isc.org>
In-reply-to: Your message of "Tue, 03 Dec 2013 09:03:11 +1100." <20131202220311.85669B04BBE@rock.dv.isc.org>
Date: Tue, 03 Dec 2013 09:15:19 +1100
Message-Id: <20131202221519.BF773B04CC1@rock.dv.isc.org>
X-SA-Exim-Connect-IP: 199.6.1.65
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: marka@isc.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

In message <20131202220311.85669B04BBE@rock.dv.isc.org>, Mark Andrews writes:
> 
> The inception and expiration times in RRSIGs is specified as seconds
> since 00:00:00 Jan 1 1970 UTC excluding leap seconds modulo 2^32.
> 
> There are no recommended fudge factors to use when evaluating these
> times though named sets the expire time to 3600 seconds in the past

That should read "inception time to 3600 seconds in the past"

> by default when generating RRSIGs.  I believe the other signers do
> similar.  I've considered making the inception timestamp a whole
> day in the past to cope with badly set timezones.
> 
> The signature validity intervals are on the order of days.  Named
> defaults to 30 days.  They are regenerated about a week before they
> are due expire if not already regenerated due to zone content
> changes.  The records should expire from caches before they become
> invalid if re-signing is being done properly.
> 
> So if the validator and the signer are both within 30 minutes of
> the true time validation should succeed.
> 
> Mark
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: marka@isc.org
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec  3 04:27:55 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 469DA1AE12C for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:27:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 PoIHhR2MgspK for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:27:54 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 0DDAD1AE128 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 04:27:54 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id BED8E86DADD for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 12:27:51 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 124AD86D422 for <ntpwg@lists.ntp.org>; Tue,  3 Dec 2013 12:27:31 +0000 (UTC)
Received: from juliette.telenet-ops.be ([195.130.137.74]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kurt@roeckx.be>) id 1Vnp4b-000Pi5-Iw for ntpwg@lists.ntp.org; Tue, 03 Dec 2013 12:27:31 +0000
Received: from intrepid.roeckx.be ([94.226.199.45]) by juliette.telenet-ops.be with bizsmtp id x0TR1m00R0zFtyu060TRSQ; Tue, 03 Dec 2013 13:27:26 +0100
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id 5B30F1FE0213; Tue,  3 Dec 2013 13:27:25 +0100 (CET)
Date: Tue, 3 Dec 2013 13:27:25 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Danny Mayer <mayer@ntp.org>
Message-ID: <20131203122725.GD2329@roeckx.be>
References: <20131201204227.7978.2067.idtracker@ietfa.amsl.com> <83842BD2-0261-472F-9CA1-AFBFB47EAD91@ogud.com> <C0A2F49F-7695-47E9-8AB0-7F94116437F9@nominum.com> <B0A571B5-438A-47AB-AAA4-00D3FC077E22@ogud.com> <331C154E-1A09-4BDD-A70A-AB67BEA2E1E8@nominum.com> <529BD4CF.6000408@ntp.org>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <529BD4CF.6000408@ntp.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: 195.130.137.74
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: kurt@roeckx.be
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Ted Lemon <ted.lemon@nominum.com>, "Bernie Volz \(volz\)" <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Sun, Dec 01, 2013 at 07:31:11PM -0500, Danny Mayer wrote:
> I think we need to figure out how to get around the Catch-22 situation
> of DNSSEC requiring relatively good time and NTP wanting to be able to
> use DNS to find valid NTP servers.

If the box doesn't have an rtc, and so maybe starts in 1970, and
doesn't have anything it can trust there is no way out of it.  You
first need _something_ you can trust be it time or some
certificate.

I do not trust my ISP, so I don't see how I can get that started
and be sure that both my time are correct and dnssec validates
properly.  The only way I see around this is that someone manually
checks that the time is correct.


Kurt

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec  3 04:35:06 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A31281AE13A for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:35:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 w62G599qhMwy for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:35:04 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 5954F1AE13D for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 04:35:04 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 110DF86DAD2 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 12:35:02 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 4A85A86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 13:47:06 +0000 (UTC)
Received: from smtp82.ord1c.emailsrvr.com ([108.166.43.82]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <ogud@ogud.com>) id 1VnTq3-000D8U-8z for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 13:47:06 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp3.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 7B9DF50326; Mon,  2 Dec 2013 08:47:02 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp3.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id F16D55031A;  Mon,  2 Dec 2013 08:47:01 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <529C1A31.2080900@ntp.org>
Date: Mon, 2 Dec 2013 08:47:01 -0500
Message-Id: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1510)
X-SA-Exim-Connect-IP: 108.166.43.82
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: ogud@ogud.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Tue, 03 Dec 2013 12:34:54 +0000
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:

> On 12/1/2013 11:47 PM, Hal Murray wrote:
>> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
>> a generic didn't-work?
>> 
>> How close does the time have to be for DNSSEC to work?
>> 
> 
> That's a question that should be asked in the dnsext WG mailing list
> (though technically the Working Group is now closed). Olafur and I
> (apart from Ted who is IETF area director) are probably the only ones on
> these lists who participate in that mailing list. Olafur was one of the
> cochairs of the DNS ext working group.
> 
> The document does not describe the DNSSEC requirements for accurate time
> and probably should so that it can be assessed in that light.
> The ones I know about are RRSIG inception time and expiration time and
> then there are certificate expiration date-times.
> 
> The proposal seems to suggest that a timestamp in 64-bit time_t be
> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
> However most systems running a DNS server is likely to have a static
> address in the first place and that is what DHCP distributes as
> nameservers to query. Since they use static addresses do they
> participate in DHCP services at all? And who says that the DHCP server
> itself has accurate time?
> 

Danny, Thanks for the kind introduction 

The reason for time_t is the dhcp-client can feed that directly into following call:
	 settimeofday(const struct timeval *tp, const struct timezone *tzp)

If there is better construct I wold be happy to update the draft with that. 

Be careful when you say "most systems running a DNS server" 
are you talking about resolver or authoritative server.  

In the second case you are right they are static and frequently well provisioned with good bandwidth, and 
at boot time the system has good idea why the current time is, but for all practical purposes unless they are signing
on the fly they do not need accurate time. 

ON THE OTHER HAND, resolvers and X.509 certificate checking is distributed and can take 
place on any device. As I said in another message DNS resolution is being pushed to the edge 
as devices that migrate between networks cannot count on the "local resolvers" to be "DNSSEC ready" 

You are right we can not count on the DHCP server to have good time, thus any DHCP server answering 
with the proposed option would need to make sure it has "decent current time", that is the reason I say in the
draft that the time should be within 10 minutes. 
When playing with cheap home routers I discovered that the devices can easily drift an hour a day, if NTP is not
invoked regularly, most of these devices just use 'ntpdate' and frequently run it from startup script once. 

>> Could this problem be solved by setting up a bank of NTP servers at well 
>> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
>> do that, I'd expect a serious problem would be overload because idiots would 
>> try to use them for normal NTP use rather than just getting off the ground.  
>> It might be possible to discourage that by making them return crappy time.
>> 
> 
> No, it would just overwhelm them. See the NIST time servers for an
> example of heavy load.
> 
>> 
>> ted.lemon@nominum.com said:
>>> As for the home router use model, it may be that what you really want is for
>>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>>> server, and then resolve that FQDN and respond to DHCP clients on the
>>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>>> address is (one hopes) resolved either at query time or when its TTL
>>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
>> 
>> Most ISPs already provide DNS servers for their customers.  How do their IP 
>> address get setup in home routers?  Could NTP servers piggyback on that 
>> mechanism if ISPs also provided NTP servers?
> 
> I wish they would provide NTP services in the same way. Unfortunately
> although most ISP's will have NTP servers they do not usually tell their
> customers about them and they certainly do not provide authenticated
> packets like autokey.
> 
> Danny

Will a hotel network provide NTP server, and would you trust it? 
Will a coffee shop provide NTP server ??? 

	Olafur

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec  3 04:35:10 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AA4E1AE13D for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:35:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 bDBlKJ9SbvBP for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:35:08 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id EA5A61AE13A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 04:35:07 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id A68D986DAF1 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 12:35:05 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 21ABB86D422 for <ntpwg@lists.ntp.org>; Mon,  2 Dec 2013 15:31:57 +0000 (UTC)
Received: from smtp98.ord1c.emailsrvr.com ([108.166.43.98]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <ogud@ogud.com>) id 1VnVTW-000DmD-8r for ntpwg@lists.ntp.org; Mon, 02 Dec 2013 15:31:57 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.ord1c.emailsrvr.com (SMTP Server) with ESMTP id 495C11B00B1; Mon,  2 Dec 2013 10:31:53 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp5.relay.ord1c.emailsrvr.com (Authenticated sender: ogud-AT-ogud.com) with ESMTPSA id BB2DA1B00B2;  Mon,  2 Dec 2013 10:31:52 -0500 (EST)
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <ogud@ogud.com>
In-Reply-To: <529CA616.3010402@ntp.org>
Date: Mon, 2 Dec 2013 10:31:50 -0500
Message-Id: <D82E52A5-F0CF-4A0A-AE1B-0440CAAC8CE7@ogud.com>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <529CA616.3010402@ntp.org>
To: mayer@ntp.org
X-Mailer: Apple Mail (2.1510)
X-SA-Exim-Connect-IP: 108.166.43.98
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: ogud@ogud.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
X-Mailman-Approved-At: Tue, 03 Dec 2013 12:34:54 +0000
Cc: NTP Working Group <ntpwg@lists.ntp.org>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>, Hal Murray <hmurray@megapathdsl.net>, Ted Lemon <ted.lemon@nominum.com>, Bernie Volz <volz@cisco.com>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Dec 2, 2013, at 10:24 AM, Danny Mayer <mayer@ntp.org> wrote:

> On 12/2/2013 8:47 AM, Olafur Gudmundsson wrote:
>> 
>> On Dec 2, 2013, at 12:27 AM, Danny Mayer <mayer@ntp.org> wrote:
>> 
>>> On 12/1/2013 11:47 PM, Hal Murray wrote:
>>>> Does DNS using DNSSEC return a specific error code for time-invalid?  Or just 
>>>> a generic didn't-work?
>>>> 
>>>> How close does the time have to be for DNSSEC to work?
>>>> 
>>> 
>>> That's a question that should be asked in the dnsext WG mailing list
>>> (though technically the Working Group is now closed). Olafur and I
>>> (apart from Ted who is IETF area director) are probably the only ones on
>>> these lists who participate in that mailing list. Olafur was one of the
>>> cochairs of the DNS ext working group.
>>> 
>>> The document does not describe the DNSSEC requirements for accurate time
>>> and probably should so that it can be assessed in that light.
>>> The ones I know about are RRSIG inception time and expiration time and
>>> then there are certificate expiration date-times.
>>> 
>>> The proposal seems to suggest that a timestamp in 64-bit time_t be
>>> distributed by DHCP. I'm not sure why not a NTP timestamp instead.
>>> However most systems running a DNS server is likely to have a static
>>> address in the first place and that is what DHCP distributes as
>>> nameservers to query. Since they use static addresses do they
>>> participate in DHCP services at all? And who says that the DHCP server
>>> itself has accurate time?
>>> 
>> 
>> Danny, Thanks for the kind introduction 
>> 
>> The reason for time_t is the dhcp-client can feed that directly into following call:
>> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)
>> 
>> If there is better construct I wold be happy to update the draft with that. 
>> 
>> Be careful when you say "most systems running a DNS server" 
>> are you talking about resolver or authoritative server.  
>> 
> 
> I actually mostly meant resolvers and authorative servers are really no
> different in the sense being discussed here.
> 
>> In the second case you are right they are static and frequently well provisioned with good bandwidth, and 
>> at boot time the system has good idea why the current time is, but for all practical purposes unless they are signing
>> on the fly they do not need accurate time. 
>> 
>> ON THE OTHER HAND, resolvers and X.509 certificate checking is distributed and can take 
>> place on any device. As I said in another message DNS resolution is being pushed to the edge 
>> as devices that migrate between networks cannot count on the "local resolvers" to be "DNSSEC ready" 
>> 
> I doubt that the number of "local resolvers" used by the general
> populace that can support DNSSEC reach even .1% today, never mind
> whether the server has it enabled.
> 

Chrome and Firefox have DNSSEC validation libraries in testing. 
Once they turn that on the numbers will jump. 
X.509 cert checks happen on edge devices today in large numbers. 
This is not just for DNSSEC this is for any device that wants to do time check before NTP can finish. 


>> You are right we can not count on the DHCP server to have good time, thus any DHCP server answering 
>> with the proposed option would need to make sure it has "decent current time", that is the reason I say in the
>> draft that the time should be within 10 minutes. 
>> When playing with cheap home routers I discovered that the devices can easily drift an hour a day, if NTP is not
>> invoked regularly, most of these devices just use 'ntpdate' and frequently run it from startup script once. 
>> 
>>>> Could this problem be solved by setting up a bank of NTP servers at well 
>>>> known IP Addresses?  Say, one next to each root DNS server.  If you tried to 
>>>> do that, I'd expect a serious problem would be overload because idiots would 
>>>> try to use them for normal NTP use rather than just getting off the ground.  
>>>> It might be possible to discourage that by making them return crappy time.
>>>> 
>>> 
>>> No, it would just overwhelm them. See the NIST time servers for an
>>> example of heavy load.
>>> 
>>>> 
>>>> ted.lemon@nominum.com said:
>>>>> As for the home router use model, it may be that what you really want is for
>>>>> the home router to query for an FQDN-only DHCP option from the ISP DHCP
>>>>> server, and then resolve that FQDN and respond to DHCP clients on the
>>>>> homenet with an IP address.   Since the FQDN is not hard-coded, and the IP
>>>>> address is (one hopes) resolved either at query time or when its TTL
>>>>> expires, this ought to prevent a repeat of the firmware burn-in incident. 
>>>> 
>>>> Most ISPs already provide DNS servers for their customers.  How do their IP 
>>>> address get setup in home routers?  Could NTP servers piggyback on that 
>>>> mechanism if ISPs also provided NTP servers?
>>> 
>>> I wish they would provide NTP services in the same way. Unfortunately
>>> although most ISP's will have NTP servers they do not usually tell their
>>> customers about them and they certainly do not provide authenticated
>>> packets like autokey.
>>> 
>>> Danny
>> 
>> Will a hotel network provide NTP server, and would you trust it? 
>> Will a coffee shop provide NTP server ??? 
>> 
> 
> I would consider them no better than the ISP's. They only provide basic
> services and almost certainly not NTP. But then how many applications
> out there will demand DNSSEC authenticated information? Generally there
> is no API to specify that from an application. When this gets into
> browser software and banks give DNSSEC authenticated addresses then it
> might take off.
> 
> Danny
> 
See above, 

	Olafur

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec  3 04:49:42 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 147511AE13E for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:49:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 s0M3GPtybyPs for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 04:49:40 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id 806531ADEA6 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 04:49:40 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 1D74D86DAA7 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 12:49:37 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id A604C86D422 for <ntpwg@lists.ntp.org>; Tue,  3 Dec 2013 12:49:31 +0000 (UTC)
Received: from georges.telenet-ops.be ([195.130.137.68]) by mail1.ntp.org with esmtp (Exim 4.77 (FreeBSD)) (envelope-from <kurt@roeckx.be>) id 1VnpPu-000Prt-CI for ntpwg@lists.ntp.org; Tue, 03 Dec 2013 12:49:31 +0000
Received: from intrepid.roeckx.be ([94.226.199.45]) by georges.telenet-ops.be with bizsmtp id x0pS1m00X0zFtyu060pShZ; Tue, 03 Dec 2013 13:49:28 +0100
Received: by intrepid.roeckx.be (Postfix, from userid 1000) id F0B141FE0213; Tue,  3 Dec 2013 13:49:25 +0100 (CET)
Date: Tue, 3 Dec 2013 13:49:25 +0100
From: Kurt Roeckx <kurt@roeckx.be>
To: Olafur Gudmundsson <ogud@ogud.com>
Message-ID: <20131203124925.GE2329@roeckx.be>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-SA-Exim-Connect-IP: 195.130.137.68
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: kurt@roeckx.be
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

On Mon, Dec 02, 2013 at 08:47:01AM -0500, Olafur Gudmundsson wrote:
> 
> The reason for time_t is the dhcp-client can feed that directly into following call:
> 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)

I don't think that is something we want every dhcp client to do.
If ntpd is running you really don't want something else to change
the time.


Kurt

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec  3 17:40:47 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3C1D91AE011 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 17:40:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 dESLdAXcIliV for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue,  3 Dec 2013 17:40:45 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 629081AE018 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue,  3 Dec 2013 17:40:45 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id BC2A786DAE0 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed,  4 Dec 2013 01:40:42 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from stenn.ntp.org (stenn.ntp.org [IPv6:2001:4f8:fff7:1::30]) by lists.ntp.org (Postfix) with ESMTP id 75E7986D4E1 for <ntpwg@lists.ntp.org>; Wed,  4 Dec 2013 01:40:27 +0000 (UTC)
Received: from localhost.ntp.org ([::1] helo=stenn.ntp.org) by stenn.ntp.org with esmtp (Exim 4.80.1 (FreeBSD)) (envelope-from <stenn@stenn.ntp.org>) id 1Vo1Rq-0001tQ-05; Wed, 04 Dec 2013 01:40:18 +0000
From: Harlan Stenn <stenn@ntp.org>
To: Kurt Roeckx <kurt@roeckx.be>
In-reply-to: <20131203124925.GE2329@roeckx.be>
References: <20131202044734.B78E0406060@ip-64-139-1-69.sjc.megapath.net> <529C1A31.2080900@ntp.org> <258D838F-F4BA-45D2-AA41-BB05E3AB147C@ogud.com> <20131203124925.GE2329@roeckx.be>
Comments: In-reply-to Kurt Roeckx <kurt@roeckx.be> message dated "Tue, 03 Dec 2013 13:49:25 +0100."
X-Mailer: MH-E 7.4.2; nmh 1.5; XEmacs 21.4 (patch 22)
Mime-Version: 1.0 (generated by tm-edit 1.8)
Date: Wed, 04 Dec 2013 01:40:17 +0000
Message-Id: <E1Vo1Rq-0001tQ-05@stenn.ntp.org>
Cc: Hal Murray <hmurray@megapathdsl.net>, Bernie Volz <volz@cisco.com>, NTP Working Group <ntpwg@lists.ntp.org>, Ted Lemon <ted.lemon@nominum.com>, "dhcwg@ietf.org WG" <dhcwg@ietf.org>
Subject: Re: [ntpwg] [dhcwg] Fwd: New Version Notification for draft-ogud-dhc-udp-time-option-01.txt
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Kurt Roeckx writes:
> > 	 settimeofday(const struct timeval *tp, const struct timezone *tzp)
> 
> I don't think that is something we want every dhcp client to do.
> If ntpd is running you really don't want something else to change
> the time.

There is a difference between DHCP at startup and a DHCP "refresh".

I suspect that a DHCP refresh should leave the clock alone.

For the startup case:

I think the best solution to this problem for LAN-connected devices will
turn out to be PTP.  And if that is not available, if you can't trust
your DHCP server to tell you what time it is, why would you trust it to
give you an IP address?

H
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Fri Dec  6 13:03:18 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2DE521AE062 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  6 Dec 2013 13:03:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level:
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001] 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 heREF_ZUgZpo for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Fri,  6 Dec 2013 13:03:16 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by ietfa.amsl.com (Postfix) with ESMTP id 19B341AE105 for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  6 Dec 2013 13:03:14 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 9048B86D9AE for <ntp-archives-ahFae6za@lists.ietf.org>; Fri,  6 Dec 2013 21:03:10 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id D17DD86D33D for <ntpwg@lists.ntp.org>; Fri,  6 Dec 2013 21:02:51 +0000 (UTC)
Received: from smtp168.dfw.emailsrvr.com ([67.192.241.168]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <odonoghue@isoc.org>) id 1Vp2Xx-000I0x-91 for ntpwg@lists.ntp.org; Fri, 06 Dec 2013 21:02:51 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp6.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 04474270C75; Fri,  6 Dec 2013 16:02:43 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp6.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 77E8C270BF6;  Fri,  6 Dec 2013 16:02:42 -0500 (EST)
Message-ID: <52A23B71.1000305@isoc.org>
Date: Fri, 06 Dec 2013 16:02:41 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: "tictoc@ietf.org" <tictoc@ietf.org>,  NTP Working Group <ntpwg@lists.ntp.org>
Content-Type: multipart/mixed; boundary="------------020201000108020404010307"
X-SA-Exim-Connect-IP: 67.192.241.168
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: odonoghue@isoc.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: [ntpwg] minutes for joint meeting of ntp/tictoc at IETF 88
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: odonoghue@isoc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

This is a multi-part message in MIME format.
--------------020201000108020404010307
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Folks,

Below are the minutes for the joint meeting of tictoc and ntp at IETF 
88. If you have any questions or comments, feel free to provide them.

Regards,
Karen



--------------020201000108020404010307
Content-Type: text/plain; charset=UTF-8;
 name="ntp tictoc ietf88 minutes.txt"
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
 filename="ntp tictoc ietf88 minutes.txt"

Minutes for joint meeting of TICTOC and NTP WGs - IETF 88
Tuesday, 5 November 2013, 1420-1550 PST (2220-2350 UTC)


Karen O'Donoghue and Yaakov Stein called the meeting to 
order. The note well was reviewed, and the blue sheets 
circulated. 

Karen O'Donoghue went over the NTP WG status. Drafts on the 
ntp extension field and the ntpv4 control protocol will be 
adopted as working group drafts in the Standards Track. In 
addition, the draft on the ntp checksum trailer will be 
adopted as a working group draft with the intention to 
publish it as Experimental. There is still a need for an 
editor for the Interleave messages effort. 

Dieter Sibold presented the current status of the Network 
Time Security effort. There is a list of issues that need 
to be addressed, and contributions are requested. 

The chairs presented the current status of the TICTOC WG. 
The MIB and Security Requirements documents are awaiting 
doc shepherding write-up. Discussions are ongoing to 
complete the MPLS timing and PTP Enterprise Profile 
efforts. The draft on multi-path synchronization will be 
adopted as an Experimental effort. 

Doug Arnold provided an update on the status of the P1588 
Working Group. The first face to face meeting was held in 
September. Subcommittees on Maintenance, Architecture, High 
Accuracy, Management, and Security have been established. 
Slides are in the proceedings for full details. 

Karen O'Donoghue provided the latest update from Stefano 
Ruffini regarding the ITU-T SG15/Q13 work. Slides are in 
the proceedings for full details. 

Doug Arnold discussed the Enterprise profile for IEEE 1588. 
There have been several updates since the last meeting, but 
the draft was mailed to the mailing list 
(http://www.ietf.org/mail-
archive/web/tictoc/current/msg01518.html). The updated 
draft will be posted in the official repository after the 
IETF meeting. Doug raised a few remaining issues and asked 
for contributions. It is hoped to take this document to 
WGLC prior to the London IETF. 

Greg Mirsky presented his new draft from the MPLS working 
group on Residence Time Measurement. There were a number of 
questions related to the technical content of the draft. 
Discussion should continue on the tictoc and mpls mailing 
lists. (draft-mirsky-mpls-residence-time-00.txt)

The subject of the current draft on Timing over MPLS that 
is being working in the tictoc working group was addressed. 
There are still concerns regarding a way forward for this 
draft. After much discussion, it was decided that the draft 
would proceed in the tictoc working group as an 
Experimental RFC. Sharam will update the draft based on the 
discussion, and we will do another WGLC based on the new 
status. It was also decided that going forward the tictoc 
working group should address timing requirements for MPLS, 
and the MPLS working group should address the actual 
mechanisms within MPLS to meet those requirements. 

The final presentation was by Michael Ackermann and Nalini 
Elkins on the Usage of NTP for the PDM DOH IPv6 Extension 
Header (draft-ackermann-tictoc-pdm-ntp-usage-00). There 
wasn't enough time to fully discuss the draft, and it was 
suggested that discussion move to the mailing list. 

The meeting adjourned slightly after 15:50 PST. 

--------------020201000108020404010307
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
--------------020201000108020404010307--

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Mon Dec  9 07:12:13 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A34F51AE33A for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  9 Dec 2013 07:12:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 y35X0rVwz6da for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon,  9 Dec 2013 07:12:12 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id EC7761AE30E for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Dec 2013 07:12:11 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id 6A50586D76B for <ntp-archives-ahFae6za@lists.ietf.org>; Mon,  9 Dec 2013 15:12:07 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id 20B9486D333 for <ntpwg@lists.ntp.org>; Mon,  9 Dec 2013 15:11:46 +0000 (UTC)
Received: from mx0a-0016f401.pphosted.com ([67.231.148.174]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <talmi@marvell.com>) id 1Vq2Ur-0005fk-VC for ntpwg@lists.ntp.org; Mon, 09 Dec 2013 15:11:46 +0000
Received: from pps.filterd (m0045849.ppops.net [127.0.0.1]) by mx0a-0016f401.pphosted.com (8.14.5/8.14.5) with SMTP id rB9FBakg012899; Mon, 9 Dec 2013 07:11:36 -0800
Received: from sc-owa02.marvell.com ([199.233.58.137]) by mx0a-0016f401.pphosted.com with ESMTP id 1gkbrg3a99-2 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Mon, 09 Dec 2013 07:11:36 -0800
Received: from YK-HUB01.marvell.com (10.4.102.51) by sc-owa02.marvell.com (10.93.76.22) with Microsoft SMTP Server (TLS) id 8.3.327.1; Mon, 9 Dec 2013 07:11:35 -0800
Received: from IL-MB01.marvell.com ([10.4.102.53]) by YK-HUB01.marvell.com ([10.4.102.51]) with mapi; Mon, 9 Dec 2013 17:11:32 +0200
From: Tal Mizrahi <talmi@marvell.com>
To: "odonoghue@isoc.org" <odonoghue@isoc.org>, "tictoc@ietf.org" <tictoc@ietf.org>, NTP Working Group <ntpwg@lists.ntp.org>, "Shahram Davari (davari@broadcom.com)" <davari@broadcom.com>, Gregory Mirsky <gregory.mirsky@ericsson.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>, "Stewart Bryant <stbryant@cisco.com> (stbryant@cisco.com)" <stbryant@cisco.com>
Date: Mon, 9 Dec 2013 17:11:21 +0200
Thread-Topic: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
Thread-Index: Ac7yxolZEFCybs8QR3qXqj67ZM5dJACKCxOQ
Message-ID: <74470498B659FA4687F0B0018C19A89C01CAF450D842@IL-MB01.marvell.com>
References: <52A23B71.1000305@isoc.org>
In-Reply-To: <52A23B71.1000305@isoc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
acceptlanguage: en-US
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.11.72, 1.0.14, 0.0.0000 definitions=2013-12-09_01:2013-12-09, 2013-12-09, 1970-01-01 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 spamscore=0 suspectscore=0 phishscore=0 adultscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=7.0.1-1305240000 definitions=main-1312090079
X-SA-Exim-Connect-IP: 67.231.148.174
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: talmi@marvell.com
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Hi,

I apologize for this late comment, as I could not attend the IETF meeting.

>Greg Mirsky presented his new draft from the MPLS working 
>group on Residence Time Measurement. There were a number of 
>questions related to the technical content of the draft. 
>Discussion should continue on the tictoc and mpls mailing 
>lists. (draft-mirsky-mpls-residence-time-00.txt)
>
>The subject of the current draft on Timing over MPLS that 
>is being working in the tictoc working group was addressed. 
>There are still concerns regarding a way forward for this 
>draft. After much discussion, it was decided that the draft 
>would proceed in the tictoc working group as an 
>Experimental RFC.

It looks like we are heading towards having two drafts that solve the same problem, which is most unfortunate. 
Isn't there a way to update Shahram's draft in a way that will satisfy Greg and Sasha's concerns and eliminate the need for draft-mirsky-mpls-residence-time? For example using GAL instead of a dedicated LSP in Shahram's draft is an option that has been discussed before, and may be the least painful compromise.

Honestly, the worst possible outcome is to define two different solutions. We obviously don't expect vendors to implement both solutions.

I believe it is our obligation to reach a single solution for this problem.

Thanks,
Tal.


-----Original Message-----
From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Karen O'Donoghue
Sent: Friday, December 06, 2013 11:03 PM
To: tictoc@ietf.org; NTP Working Group
Subject: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88

Folks,

Below are the minutes for the joint meeting of tictoc and ntp at IETF 88. If you have any questions or comments, feel free to provide them.

Regards,
Karen


_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg

From ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org  Tue Dec 10 15:34:01 2013
Return-Path: <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>
X-Original-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Delivered-To: ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6D871AE1C0 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 10 Dec 2013 15:34:01 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level:
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.001] 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 6eLASiqWdVLY for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Tue, 10 Dec 2013 15:33:59 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [IPv6:2001:4f8:fff7:1::7]) by ietfa.amsl.com (Postfix) with ESMTP id D88771AD845 for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 10 Dec 2013 15:33:59 -0800 (PST)
Received: from lists.ntp.org (lists.ntp.org [149.20.68.7]) by lists.ntp.org (Postfix) with ESMTP id D4F5486D78A for <ntp-archives-ahFae6za@lists.ietf.org>; Tue, 10 Dec 2013 23:33:54 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (mail1.ntp.org [IPv6:2001:4f8:fff7:1::5]) by lists.ntp.org (Postfix) with ESMTP id AD9CA86D333 for <ntpwg@lists.ntp.org>; Tue, 10 Dec 2013 23:33:36 +0000 (UTC)
Received: from smtp158.dfw.emailsrvr.com ([67.192.241.158]) by mail1.ntp.org with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <odonoghue@isoc.org>) id 1VqWo2-0000lX-QS for ntpwg@lists.ntp.org; Tue, 10 Dec 2013 23:33:36 +0000
Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp5.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 8103B58643; Tue, 10 Dec 2013 18:33:28 -0500 (EST)
X-Virus-Scanned: OK
Received: by smtp5.relay.dfw1a.emailsrvr.com (Authenticated sender: odonoghue-AT-isoc.org) with ESMTPSA id 5150D58358;  Tue, 10 Dec 2013 18:33:27 -0500 (EST)
Message-ID: <52A7A4C6.5020503@isoc.org>
Date: Tue, 10 Dec 2013 18:33:26 -0500
From: Karen O'Donoghue <odonoghue@isoc.org>
Organization: ISOC
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:24.0) Gecko/20100101 Thunderbird/24.1.1
MIME-Version: 1.0
To: Tal Mizrahi <talmi@marvell.com>, "tictoc@ietf.org" <tictoc@ietf.org>,  NTP Working Group <ntpwg@lists.ntp.org>, "Shahram Davari (davari@broadcom.com)" <davari@broadcom.com>,  Gregory Mirsky <gregory.mirsky@ericsson.com>, Alexander Vainshtein <Alexander.Vainshtein@ecitele.com>,  "Stewart Bryant <stbryant@cisco.com> (stbryant@cisco.com)" <stbryant@cisco.com>, jdrake@juniper.net
References: <52A23B71.1000305@isoc.org> <74470498B659FA4687F0B0018C19A89C01CAF450D842@IL-MB01.marvell.com>
In-Reply-To: <74470498B659FA4687F0B0018C19A89C01CAF450D842@IL-MB01.marvell.com>
X-SA-Exim-Connect-IP: 67.192.241.158
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: odonoghue@isoc.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.14
Precedence: list
Reply-To: odonoghue@isoc.org
List-Id: IETF Working Group for Network Time Protocol <ntpwg.lists.ntp.org>
List-Unsubscribe: <http://lists.ntp.org/options/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=unsubscribe>
List-Archive: <http://lists.ntp.org/pipermail/ntpwg>
List-Post: <mailto:ntpwg@lists.ntp.org>
List-Help: <mailto:ntpwg-request@lists.ntp.org?subject=help>
List-Subscribe: <http://lists.ntp.org/listinfo/ntpwg>, <mailto:ntpwg-request@lists.ntp.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org
Sender: ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org

Tal,

While I understand your concerns, I believe the point that we came to 
was that there
was no clear consensus between the MPLS and TICTOC working groups regarding
the solution on the table. It also became clear that there wasn't a clearly
understood (across both working groups) set of requirements regarding
the problem to be solved. An experimental RFC gives the community a 
chance to
continue to explore the option that has been documented and discussed 
for a couple
years now while allowing additional time to develop requirements and 
consensus on
a standardized solution. Our AD suggested this as a possible way 
forward, and all
the main parties to the discussion were in agreement at the meeting.

Regards,
Karen

On 12/9/13 10:11 AM, Tal Mizrahi wrote:
> Hi,
>
> I apologize for this late comment, as I could not attend the IETF meeting.
>
>> Greg Mirsky presented his new draft from the MPLS working
>> group on Residence Time Measurement. There were a number of
>> questions related to the technical content of the draft.
>> Discussion should continue on the tictoc and mpls mailing
>> lists. (draft-mirsky-mpls-residence-time-00.txt)
>>
>> The subject of the current draft on Timing over MPLS that
>> is being working in the tictoc working group was addressed.
>> There are still concerns regarding a way forward for this
>> draft. After much discussion, it was decided that the draft
>> would proceed in the tictoc working group as an
>> Experimental RFC.
> It looks like we are heading towards having two drafts that solve the same problem, which is most unfortunate.
> Isn't there a way to update Shahram's draft in a way that will satisfy Greg and Sasha's concerns and eliminate the need for draft-mirsky-mpls-residence-time? For example using GAL instead of a dedicated LSP in Shahram's draft is an option that has been discussed before, and may be the least painful compromise.
>
> Honestly, the worst possible outcome is to define two different solutions. We obviously don't expect vendors to implement both solutions.
>
> I believe it is our obligation to reach a single solution for this problem.
>
> Thanks,
> Tal.
>
>
> -----Original Message-----
> From: TICTOC [mailto:tictoc-bounces@ietf.org] On Behalf Of Karen O'Donoghue
> Sent: Friday, December 06, 2013 11:03 PM
> To: tictoc@ietf.org; NTP Working Group
> Subject: [TICTOC] minutes for joint meeting of ntp/tictoc at IETF 88
>
> Folks,
>
> Below are the minutes for the joint meeting of tictoc and ntp at IETF 88. If you have any questions or comments, feel free to provide them.
>
> Regards,
> Karen
>
>

_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg
