Re: [ntpwg] call for adoption (draft-dfranke-ntp-data-minimization)

Harlan Stenn <stenn@nwtime.org> Mon, 27 March 2017 21:01 UTC

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 (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A0136129659 for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 27 Mar 2017 14:01:33 -0700 (PDT)
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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=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 d2m9WWEV13Oz for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Mon, 27 Mar 2017 14:01:31 -0700 (PDT)
Received: from lists.ntp.org (psp3.ntp.org [185.140.48.241]) by ietfa.amsl.com (Postfix) with ESMTP id 8F9DD127601 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 27 Mar 2017 14:01:30 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by lists.ntp.org (Postfix) with ESMTP id 5520786DBF4 for <ntp-archives-ahFae6za@lists.ietf.org>; Mon, 27 Mar 2017 21:01:29 +0000 (UTC)
X-Original-To: ntpwg@lists.ntp.org
Delivered-To: ntpwg@lists.ntp.org
Received: from mail1.ntp.org (fortinet.ntp.org [10.224.90.254]) by lists.ntp.org (Postfix) with ESMTP id 93A3386D77E for <ntpwg@lists.ntp.org>; Mon, 27 Mar 2017 21:01:26 +0000 (UTC)
Received: from chessie.everett.org ([66.220.13.234]) by mail1.ntp.org with esmtps (TLSv1:CAMELLIA256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <stenn@nwtime.org>) id 1csblM-000BKZ-9r for ntpwg@lists.ntp.org; Mon, 27 Mar 2017 21:01:26 +0000
Received: from localhost (localhost [127.0.0.1]) by chessie.everett.org (Postfix) with SMTP id 179C8B836 for <ntpwg@lists.ntp.org>; Mon, 27 Mar 2017 21:01:14 +0000 (UTC)
Received: from hms-mbp11.pfcs.com (96-41-177-107.dhcp.mdfd.or.charter.com [96.41.177.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by chessie.everett.org (Postfix) with ESMTPSA id D7914B825; Mon, 27 Mar 2017 21:01:13 +0000 (UTC)
To: Daniel Franke <dfoxfranke@gmail.com>
References: <CA564C5C-6CED-4810-BA2F-5433F2525249@isoc.org> <20170327133842.GK8192@localhost> <CAJHGrrTvY0gdPdrWDDJiEbD3hnA6vKWhva4cFzNgt=e6zGY5tA@mail.gmail.com> <20170327153535.GA16225@localhost> <CAMbs7ks+zcZV+d0sRxq=0LD-UbLjOhhpaK=GxvPEX0KJ7rz0=g@mail.gmail.com> <CAJm83bCT5PeSWq6kG8gfOz6Yfw7i8+3ix1yQazNuM9d0-OL3AQ@mail.gmail.com> <346830ae-cffd-0470-ae20-16fee166aa36@nwtime.org> <CAJm83bCvGR4rcRYHKFO57GOy5ZQDYfp0M4fkY7sq=1nsT0Lrfg@mail.gmail.com>
From: Harlan Stenn <stenn@nwtime.org>
Message-ID: <1513b050-1fe3-4ad7-db27-a4990810bdc8@nwtime.org>
Date: Mon, 27 Mar 2017 14:01:13 -0700
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.8; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <CAJm83bCvGR4rcRYHKFO57GOy5ZQDYfp0M4fkY7sq=1nsT0Lrfg@mail.gmail.com>
X-DSPAM-Result: Innocent
X-DSPAM-Processed: Mon Mar 27 21:01:14 2017
X-DSPAM-Confidence: 0.9899
X-DSPAM-Improbability: 1 in 9809 chance of being spam
X-DSPAM-Probability: 0.0000
X-DSPAM-Signature: 6384,58d97d9a107507672921025
X-SA-Exim-Connect-IP: 66.220.13.234
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: stenn@nwtime.org
X-SA-Exim-Version: 4.2
X-SA-Exim-Scanned: Yes (on mail1.ntp.org)
Subject: Re: [ntpwg] call for adoption (draft-dfranke-ntp-data-minimization)
X-BeenThere: ntpwg@lists.ntp.org
X-Mailman-Version: 2.1.20
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>
Cc: ntpwg@lists.ntp.org
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 <ntpwg-bounces+ntp-archives-ahfae6za=lists.ietf.org@lists.ntp.org>


On 3/27/17 1:50 PM, Daniel Franke wrote:
> On 3/27/17, Harlan Stenn <stenn@nwtime.org> wrote:
>> It would help if you properly quoted your context.
>>
>> I don't see a '32' anywhere in what Aanchal said, above.
> 
> The context I should have included was from Miroslav upthread:
> 
>     My suggestion is to remove Precision from that list and add before
>     that paragraph: Precision SHALL (or SHOULD?) be set to 32.
> 
>     Anyway, do the all other fields need to be zero? As long as they are
>     constant and not unique to the individual clients, as in most SNTP
>     implementations they currently are, it wouldn't be a problem, right?
> 
>> Assuming this is about the poll interval, I have 2 comments:
>>
>> - Bluntly, OpenNTPD would not be my first choice for a source for NTP
>> protocol experience or knowledge.
> 
> Regardless of your opinion of OpenNTPD design choices, the facts
> remain that it's in wide deployment and sets the precision field to
> zero.  Those facts alone make it a good choice for standardization
> since:
> 
> 1. Matching an existing implementation leads to one less opportunity
> for fingerprinting.
> 2. Existing widespread use of this value means we can be confident it
> won't break anything.

If they made a suboptimal choice we should take this opportunity to make
a better choice.

My previous discussions on the usefulness of this sort of fingerprinting
are still unanswered.

There is no reason to believe that one arbitrary value for this is
somehow "magical" and a different arbitrary value would be dangerous.

>> - There is likely benefit to knowing the client's poll interval in
>> certain situations so the server can recommend changes to the poll
>> interval.  This becomes more difficult if the server doesn't know what
>> the client's poll interval is.
> 
> You were confused here about which field we were discussing. Zeroing
> the poll interval is already a MAY in the current draft, partly
> because we want to allow for exactly this sort of thing.

OK.

-- 
Harlan Stenn <stenn@nwtime.org>
http://networktimefoundation.org - be a member!

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