Re: [Ntp] The NTP WG has placed draft-roughtime-aanchal in state "Call For Adoption By WG Issued"

Watson Ladd <> Wed, 11 September 2019 14:42 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 651D312012A for <>; Wed, 11 Sep 2019 07:42:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 8MGfRmktDpK3 for <>; Wed, 11 Sep 2019 07:42:54 -0700 (PDT)
Received: from ( [IPv6:2a00:1450:4864:20::12e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 51D7C1208C4 for <>; Wed, 11 Sep 2019 07:42:52 -0700 (PDT)
Received: by with SMTP id r22so5372291lfm.1 for <>; Wed, 11 Sep 2019 07:42:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=O5yQfXEC9tKinlZgpWMwTZsTY9Fs65Ltc3J54b/fzrc=; b=Fg14Mb8/AUYfUd19foGVbMxaZFKEB+tT5YmH2nJDsy/VpcaUg2fbUk78VYlpvR1YG5 Oe7wg3X3Rdqmmte8NfnREq//LZa6xqkpmkG0Aw6YqXG0aEARW+DLKoNWD4EEQB/TvEAl PQ1J+yxnfpzKU3MX83N8tQSZOp9m9J9PB4BVDdIgw0anbGcA48/tsuIm+rHbkFfFqflH cM16F+JsYiOACdnd/9TObeUVcS7PTBfeMQITnKqcVPjE/0hoE8M/tdIZdxjhXo6f5WEb HU9VwSgw1oYJ13MfW3sXKcnVkygI8FweDZ1gEJTaNMVZjNvM9R/Atwffdye79mFFDDVL 5FQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=O5yQfXEC9tKinlZgpWMwTZsTY9Fs65Ltc3J54b/fzrc=; b=OGtEyyJ4Sin/ZcutbySSJSHw/DFmzRHUtnkMzyC9gOlEjhUwHXjnLPH3vphwk42xCb ffl9eWoBNXNgXSHEFX6i7CknJuU7tAlQo2Ds+fMEXLO5R2y+chSU50OCuXOG2O+WhVdr bWJgGLMFcmwshyqyEn4UkzIaG0IceN6fZO7BHgrzF4z0PE364ppXRiCuZQ9ApE1Zby/A bnZ9yjqFHEN83sfPIHbFP36dTIG+5f4KHQ91V0IgJ/LzZSLm1RdMeuk+LIyKzHKA3zpx avviKLCF8VuQvow3GwV7lQBoGT8jnyJaFZZ/FfW7nG3c5dw/cg3JnQ8653dE8l0G5cCi i1SQ==
X-Gm-Message-State: APjAAAXd196i8QJs+9N8nE/iIZyEpFvwcgRC4MIL72ViO1hZTYgR/aeV loup+N/vu+QktBVgI6zb6p27t7rzVLz8p+sCRwA=
X-Google-Smtp-Source: APXvYqxc1IMxgrIKetBpBnaj/zyTgo+UjHapPajZ6YHt21uw8YqCR85End5AMsThAznFNcGQbx31EB7uh6ovA1qkzNU=
X-Received: by 2002:ac2:5ec1:: with SMTP id d1mr23681553lfq.83.1568212970479; Wed, 11 Sep 2019 07:42:50 -0700 (PDT)
MIME-Version: 1.0
References: <> <> <> <> <> <20190911070549.GF21704@localhost>
In-Reply-To: <20190911070549.GF21704@localhost>
From: Watson Ladd <>
Date: Wed, 11 Sep 2019 07:42:38 -0700
Message-ID: <>
To: Miroslav Lichvar <>
Cc: NTP WG <>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <>
Subject: Re: [Ntp] The NTP WG has placed draft-roughtime-aanchal in state "Call For Adoption By WG Issued"
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 11 Sep 2019 14:42:57 -0000

On Wed, Sep 11, 2019 at 12:06 AM Miroslav Lichvar <>; wrote:
> On Tue, Sep 10, 2019 at 10:30:23PM +0200, Marcus Dansarie wrote:
> > As someone (Daniel or Watson?) said in today's interim meeting: the
> > purpose of Roughtime is generally not to set the system's clock, but for
> > other purposes such as certificate verification.
> It would be good to explain that in the draft. But I'm not sure how
> exactly that makes it different from NTP. An NTP client doesn't have
> to synchronize the system clock and it doesn't need any special
> privileges. There are of applications that don't trust the system
> clock and use NTP to verify the current time, even though it might
> seem like a terrible idea.
> If I understand it correctly, Roughtime could be specified as an NTP
> extension field, possibly as an extension to NTS. So, I think the
> document should explain why a new protocol using a different transport
> was needed. I guess one reason could be that Roughtime is easier to
> implement than NTP, especially in some specific frameworks.

The signing negatively affects the possible timing accuracy, and you
need to track things differently on the server.

Based on discussions in Prague we're also adding TCP transport, which
doesn't work for NTP.

What are the benefits from adding it as an extension?