Re: [Ntp] The bump, or why NTP v5 must specify impulse response

Watson Ladd <watsonbladd@gmail.com> Mon, 13 April 2020 19:15 UTC

Return-Path: <watsonbladd@gmail.com>
X-Original-To: ntp@ietfa.amsl.com
Delivered-To: ntp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4349B3A1C6E for <ntp@ietfa.amsl.com>; Mon, 13 Apr 2020 12:15:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) 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 KwjB7JnLA1KI for <ntp@ietfa.amsl.com>; Mon, 13 Apr 2020 12:15:40 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4BB763A1C6B for <ntp@ietf.org>; Mon, 13 Apr 2020 12:15:40 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id q22so9935136ljg.0 for <ntp@ietf.org>; Mon, 13 Apr 2020 12:15:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wF0YKLwFJGXtnDobUQYpI8ibZqid8IFvOx7twbU1VPo=; b=fIausasEOkgCMoLMxhIiBxeeTD8JWIur/2hLswd/1W0XeW8vGMmiZ/dNCXM+SZueqc LuagwXLCcw3SvQyyKVQe87jmR8+5mcupitevpxZ7x3nxKZkVDdbdgyh/i9xNvAnVbQ8j O+MtgeLtqRR1r7bk3e1OyvSfjswyZvIRlGyWIhZr3DTNaXj/vZVLIw9++6vEwwXlPL3W Ax3LIRpSvYbgPYedhLdUS+1ovCcy/WeJt99oM+8yYwZSbmsu02oQxWpA1JUUDLq80aW0 n8YnCUwLty+AbBRZjqIkvM8bFt3cqnJxyE1yf31vxp0lJDprog0o2WDqKZ+TKLUP/QjW vybg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wF0YKLwFJGXtnDobUQYpI8ibZqid8IFvOx7twbU1VPo=; b=bnTwSmJNZm+eua1U+9Fcr48afw9qq/s+EL1YZI/kGd4ZbMQaC1ujzpv1kssXuOFnJk etbCia9tJVF22ISkKgLmXmTXLo7/UPpIWGRfqgc28M8jo/XgQg5gIz1aUq8b0Mjs73Gk KIRj/4wg9mCp8gvi6NAQZKMT/hVddNpQXHeuceWac/0n1rxbDH3zmtECzr9ZOde3BrnT L2WKWMSpZXdBEvrtR3f015/GnsUFL0kdqQN2rDYwmT0/Hrer2lmyWXR+eVJpplgqVDfZ Hh9d365LIKX1mJLRuWIT6xckS9iibys7XYeg4YX0gkayt27T1LfMvxU5+vcsOYpNrh7J akyQ==
X-Gm-Message-State: AGi0PuZppTt69sp3H6iV1+cIfoutrElxpNHXPmzMF/GnhakaZd0qUhrX XfzJpmS/h1ChP4hZ/QZNjvNVPTZT0Zr5HiGVguk=
X-Google-Smtp-Source: APiQypIJnqirYiZ3dyR9JZCw/Iu2tZEziMSHIKPnBghtxvWFmrIspkJKZgG4FXPzKhG9C+G1ok28s0pBry6oIbh3TC8=
X-Received: by 2002:a05:651c:108:: with SMTP id a8mr8149235ljb.160.1586805338471; Mon, 13 Apr 2020 12:15:38 -0700 (PDT)
MIME-Version: 1.0
References: <CACsn0c=zzDKP6iBjPJWGF0rkqSaY3AY738ynGwDZO14sdBJ-Bg@mail.gmail.com> <CAJm83bB2A3VUxXX47Y0ubmS9Xne7PRSyV_xHY_D9YvHjqE-vFA@mail.gmail.com>
In-Reply-To: <CAJm83bB2A3VUxXX47Y0ubmS9Xne7PRSyV_xHY_D9YvHjqE-vFA@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Mon, 13 Apr 2020 12:15:27 -0700
Message-ID: <CACsn0cm3jpKZTUQ=novTgVaFhc1xCJgmUF3oOgdrzQa-HgOCUQ@mail.gmail.com>
To: Daniel Franke <dfoxfranke@gmail.com>
Cc: NTP WG <ntp@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000087019105a330e869"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/2aLG9A9pzb7QHImnbYJNhIiAP1s>
Subject: Re: [Ntp] The bump, or why NTP v5 must specify impulse response
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <ntp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ntp>, <mailto:ntp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ntp/>
List-Post: <mailto:ntp@ietf.org>
List-Help: <mailto:ntp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ntp>, <mailto:ntp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Apr 2020 19:15:43 -0000

On Mon, Apr 13, 2020, 7:21 AM Daniel Franke <dfoxfranke@gmail.com> wrote:

> On Sun, Apr 12, 2020 at 6:11 PM Watson Ladd <watsonbladd@gmail.com> wrote:
> > Section 14.5 of Phase Lock Techniques by Floyd Gardner describes
> > difficult problems caused by the accumulation of errors in a chain of
> > PLLs under benign conditions, and section 2.2.4 describes the root
> > cause, namely an inevitable peak in the transfer function of a second
> > order filter. I don't think these are insolvable in NTP v5, but they
> > should give pause to the idea that we can avoid needing to specify the
> > the synchronization algorithm. The peaking of the PLL needs to be
> > controlled, or some thing more complex needs to be specified.
>
> Are the algorithms in RFC 5905 vulnerable to this? If so, I think that
> shoots down any implication that it's a practical necessity to solve
> this in the NTPv5 spec, since we've obviously been getting by okay so
> far.
>

v4 limits the length of the chain and specifies the input response to have,
which solves the problem.


> Just to be clear, though, I'm not proposing that the WG should be
> *silent* on synchronization algorithms in v5. Just that whatever we
> have to say about it should be in a separate, Informational document,
> and can discuss the design space and suggest multiple possibilities
> rather than require one particular thing.
>