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

Daniel Franke <dfoxfranke@gmail.com> Mon, 13 April 2020 14:21 UTC

Return-Path: <dfoxfranke@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 1D3DD3A16AC for <ntp@ietfa.amsl.com>; Mon, 13 Apr 2020 07:21:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 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, 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 a5XUmOc_EiEe for <ntp@ietfa.amsl.com>; Mon, 13 Apr 2020 07:21:52 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 214E63A16B0 for <ntp@ietf.org>; Mon, 13 Apr 2020 07:21:52 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id i2so7737466ils.12 for <ntp@ietf.org>; Mon, 13 Apr 2020 07:21:52 -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=rPYP/ECdJoiZzui3UzDQFiJtQ/SQnam/L7SEL1KPbHY=; b=gC4k5M+cWUIGx5X683z8W6gh90jxeQT1itPJoBqZHx0EhJKH9EaU9Jvh1rev4Cjyiu R0XEXguFINHHo8xGsHtODlSMr7/icAumXgJULdceADm+L6DSUpV0JQECwh9nnV94JYFd iZ67GfPZH6ba/jVVfaumb1oXwZTAkkoiv9BDYRx8j2p4qQknMSxn9msUNAyElISmnwur QD7TIvqgbdgbpUbv5Y5MbAc4pOdtJy6ky+r5wpUwrGx6CONoA1BHDIkporyMkgIRw9D1 iZP46t4igzMvTGua4R/2Si9eZqZvgLTADR0uPjEPTcWRnOV0MOII2w/vNGAqlOyaUD2j 7oPg==
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=rPYP/ECdJoiZzui3UzDQFiJtQ/SQnam/L7SEL1KPbHY=; b=m8R4j2sk3S66MTANW01T9RCMigvls3lgjMnORvaYmLdUuhTeCb4xA6kx5uqJObDoN8 oKthGp1gpGJdGs1H8csgRyEIK3g4URR3DNYJ7wv3ZZ05+3r2EmSftdyCHNxAjaQEPXNP rjGzdbmmjwssHpWiKoxzWJlaeYmZHp2ZbzzYy5UN/2/iqn+hfvmtmG+/EnfB3rDFWYdl cjv4Ky6zseDS6ebsCTjOk6knu3g6ASAnCXTs9hS9LyQBv67Yl+FqaQ+1LLxjwmoNSaws MUO9DHUhtBxoeu14RQTyzX08qKYcnWg9NV6oKrYfCX9y4Wlm/r+fqGR6AP4W9IWXil7Q qQLA==
X-Gm-Message-State: AGi0PubJ8yTMWQOEUQQhmqi9Qyo/JxAzCPvYr69B7GrAUGbvI0l0mpc1 tANjwXhpV2kZIb7kwOmze7C/w4IS/Mx+MW7txFpgIHbH
X-Google-Smtp-Source: APiQypJ7a0RTR19QC9Hmra/aAU8ta5/65hzuUFn/io0G8w5fDzSZSM69JrxhIN6E9TVY4j1GvgZtnjkkH+K5+tgfbmU=
X-Received: by 2002:a92:dccf:: with SMTP id b15mr2671827ilr.246.1586787711338; Mon, 13 Apr 2020 07:21:51 -0700 (PDT)
MIME-Version: 1.0
References: <CACsn0c=zzDKP6iBjPJWGF0rkqSaY3AY738ynGwDZO14sdBJ-Bg@mail.gmail.com>
In-Reply-To: <CACsn0c=zzDKP6iBjPJWGF0rkqSaY3AY738ynGwDZO14sdBJ-Bg@mail.gmail.com>
From: Daniel Franke <dfoxfranke@gmail.com>
Date: Mon, 13 Apr 2020 10:21:40 -0400
Message-ID: <CAJm83bB2A3VUxXX47Y0ubmS9Xne7PRSyV_xHY_D9YvHjqE-vFA@mail.gmail.com>
To: Watson Ladd <watsonbladd@gmail.com>
Cc: NTP WG <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/iGhvhwRdA0nFE1jd89Meh_pUlRQ>
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 14:21:53 -0000

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.

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.