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

Daniel Franke <dfoxfranke@gmail.com> Wed, 29 March 2017 15:48 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 CCC0812984A for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 29 Mar 2017 08:48:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.092
X-Spam-Level:
X-Spam-Status: No, score=-1.092 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, DKIM_SIGNED=0.1, FREEMAIL_FORGED_FROMDOMAIN=0.197, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_SPAM=0.5, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (2048-bit key) reason="fail (message has been altered)" header.d=gmail.com
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 SyU36r5eGm5U for <ietfarch-ntp-archives-ahFae6za@ietfa.amsl.com>; Wed, 29 Mar 2017 08:48:11 -0700 (PDT)
Received: from lists.ntp.org (psp3.ntp.org [185.140.48.241]) by ietfa.amsl.com (Postfix) with ESMTP id 2FC8D129562 for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 29 Mar 2017 08:48:11 -0700 (PDT)
Received: from psp3.ntp.org (localhost.ntp.org [127.0.0.1]) by lists.ntp.org (Postfix) with ESMTP id D05BB86DC1E for <ntp-archives-ahFae6za@lists.ietf.org>; Wed, 29 Mar 2017 15:48:10 +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 6355986DAE6 for <ntpwg@lists.ntp.org>; Wed, 29 Mar 2017 15:48:07 +0000 (UTC)
Received: from mail-qk0-f178.google.com ([209.85.220.178]) by mail1.ntp.org with esmtps (TLSv1:AES128-SHA:128) (Exim 4.77 (FreeBSD)) (envelope-from <dfoxfranke@gmail.com>) id 1ctFpH-000BHm-DN for ntpwg@lists.ntp.org; Wed, 29 Mar 2017 15:48:07 +0000
Received: by mail-qk0-f178.google.com with SMTP id f11so16501473qkb.0 for <ntpwg@lists.ntp.org>; Wed, 29 Mar 2017 08:47:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gT3cDwS9JbIfkcImlypoIlN9rx0FBRt9rJ8GIDEpioU=; b=MGNYgoDV5sUha0D9ONU8f2FMdxMuUpp2huY+uYHvKDEPWgfvfRYzMj+QinGSIJEZcj 03TlWLn10+XrUoFqRrduPF7W1+xwz9rthkVb7zijBZoinzGaOgZfbpobq5qoFI8GfbrA Rkjnf1zxUSWaxUARUEfY+vxI24nZUYkgXqrZwbBhiFoNvkncDLQx8tIeJTO00fRGQ5YA Kp/6tNB1fwtI3BHh5Jnmk56r0PEWPQBxfBNrHPv9HerfE8xD6Vvfhxl0HWHNThMnY554 uls+x3nPbctptVxzf4CmJr3ByR0YSN6d1aqzf/wSatp4vzMnLbgx5xIAH36WDAgjcPo5 lcwg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gT3cDwS9JbIfkcImlypoIlN9rx0FBRt9rJ8GIDEpioU=; b=NJWeuXS01V7ZpQFPVaho5/Srnj3BYyjoVeOkq7RfEB/JekwTO5ddBTlLlVKZjiZGCN xDDy0IVdreDvP4LowvUHTWrJVyoGv4jKzSmqLifcPwlvmPTFyy9IDatADW8ggKqQ2xQI Cj7MqYhuCvyUlRpP9KgcwJnJHInNAibgK6U5esF++XgfuRsqBqQaMw4lBwpUlq2vte90 cDoyqLookD0ccpECQ/i6IckNaWIss7jJ8vq91mlpi+epn0jZ75EaArvHX0kylCGNI1Cd 7MXMhileOsovpMRwEA283cF8ZmoVgDC5JK7ZLg9/h9N5C0CTuqFVclq78eBb2vywkKUN mV9w==
X-Gm-Message-State: AFeK/H1T7bZxUxdrOvIJ+QE7TeoT8GpVSLK5pP/hNxbP2Q8pGxUhKGJVi68uQVJcJSwrvyCWb8wvzWJxNgUn0g==
X-Received: by 10.55.5.136 with SMTP id 130mr1274505qkf.279.1490802478815; Wed, 29 Mar 2017 08:47:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.12.136.119 with HTTP; Wed, 29 Mar 2017 08:47:58 -0700 (PDT)
In-Reply-To: <8D2BF679AAC7C346848A489074F9F8BF8C4D05AC@sjsrvexchmbx2.microsemi.net>
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> <20170329094115.GC23511@localhost> <8D2BF679AAC7C346848A489074F9F8BF8C4D05AC@sjsrvexchmbx2.microsemi.net>
From: Daniel Franke <dfoxfranke@gmail.com>
Date: Wed, 29 Mar 2017 11:47:58 -0400
Message-ID: <CAJm83bDN64c-a7Q7kE1YO264GBPU1WAn--4soFFTnskAsL1mqQ@mail.gmail.com>
To: Greg Dowd <Greg.Dowd@microsemi.com>
X-SA-Exim-Connect-IP: 209.85.220.178
X-SA-Exim-Rcpt-To: ntpwg@lists.ntp.org
X-SA-Exim-Mail-From: dfoxfranke@gmail.com
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" <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/29/17, Greg Dowd <Greg.Dowd@microsemi.com> wrote:
> IIRC, there is a randomizer of a second or two attached to the calculation
> of the next poll in ntpd?

IIRC you're correct, but the randomization is some number of whole
seconds. The fractional part of the second is determined by whenever
the SIGALRM happens to come in, which is not random. Anyhow, I think
this is clearly out-of-scope for the IETF and should be taken to NTP
implementations' respective development lists.
_______________________________________________
ntpwg mailing list
ntpwg@lists.ntp.org
http://lists.ntp.org/listinfo/ntpwg