IETF Logo Mail Archive

Re: [Ntp] I-D Action: draft-ietf-ntp-using-nts-for-ntp-26.txt

Ragnar Sundblad <ragge@netnod.se> Mon, 23 March 2020 10:02 UTC

Return-Path: <ragge@netnod.se>
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 EC2533A0433 for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 03:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=netnod-se.20150623.gappssmtp.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 eyMyLaQy7PDC for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 03:02:17 -0700 (PDT)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) (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 DD36D3A0408 for <ntp@ietf.org>; Mon, 23 Mar 2020 03:02:16 -0700 (PDT)
Received: by mail-lj1-x235.google.com with SMTP id w4so13784086lji.11 for <ntp@ietf.org>; Mon, 23 Mar 2020 03:02:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netnod-se.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MiSqAzE/4/+sZQEcRf6w1hVbEDkpeuWu9RCJ7JT1uBE=; b=M0SSmeJna5RRrFWQlYlGKAmz+Z0He1/ShVXYaQ3rh76IpJqa9w34Nl1jeGKSmGLwgt 7A4u5jMvApLpCqm2yJGvQi4mfUNYHDmKaQyG3rOMs/JIpa/JxodKcA9nPddP0GwaDUAV v2ef9FAcan6dyoBY/S6lunop5NQB0M47WWz+UbjU8CUEt7SaqA/HSVLHmL0UW8KiLXaw JGsYkeQPvzrofcuYmpUw4Psid98K8m4PcqAKJI5J82ihBcv5CfQmLFhGLcxbSxDRF2cH K87vvkXc3vGA2I3zQsCcOLCGF8TPbi0Aabthg+8rdqNRzcDQJor56K0vgtNywbpTpMwo 4KCw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=MiSqAzE/4/+sZQEcRf6w1hVbEDkpeuWu9RCJ7JT1uBE=; b=A3yTQcBMUTXj607El7x6QW/i0J2a46eqPlta5nVdn1+eKkdcygFhLquZ25VIASv7Qe fKQJWMfvThDa4Fs6H+TUMijTTN50pMdw/Nyqi0EVSEDO7E+GFeknao7Adoos2Cmi8sAb tZxtMBa95QCCeBx3BNfQUOD5uxCxbzWZhGent3wRRsspBh0wuqq3eYsYvGgO67PMEWY1 8AsmNYedYogxnCdE2cLyur6tVoAnkzbZzNDfKaTzhsKzXjZdHiczegVHqWrUf/fEXG4c hTRY8mealEa5CQ1U762idilowR6ceFQ02Axr1YOeKsvWv/fHrcsTkdXg/YfQl9nFGJq5 JYvg==
X-Gm-Message-State: ANhLgQ3muh1P+yXExAOwSFeSfuJqAp5mbKQQGz3VC+n4zR6eVhTcwfFJ Tpan+2R10YMqyZtCZ2Tdd6iHnQ==
X-Google-Smtp-Source: ADFU+vtcZjr0UE3Q0tECX6V449n3UaJcKvB7TiL30NiA68HqqPaFAQ00/I7ZrjAmFDdiCWMnB7FMfQ==
X-Received: by 2002:a2e:9a90:: with SMTP id p16mr13708416lji.277.1584957735036; Mon, 23 Mar 2020 03:02:15 -0700 (PDT)
Received: from [10.0.1.14] (h-122-211.A530.priv.bahnhof.se. [213.80.122.211]) by smtp.gmail.com with ESMTPSA id a8sm7567352lfb.59.2020.03.23.03.02.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 23 Mar 2020 03:02:14 -0700 (PDT)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3608.60.0.2.5\))
From: Ragnar Sundblad <ragge@netnod.se>
In-Reply-To: <20200323080810.AABC540605C@ip-64-139-1-69.sjc.megapath.net>
Date: Mon, 23 Mar 2020 11:02:12 +0100
Cc: Watson Ladd <watsonbladd@gmail.com>, NTP WG <ntp@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5481EAB8-3258-4E56-8855-2A5CB237935C@netnod.se>
References: <20200323080810.AABC540605C@ip-64-139-1-69.sjc.megapath.net>
To: Hal Murray <hmurray@megapathdsl.net>
X-Mailer: Apple Mail (2.3608.60.0.2.5)
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/4y6dWWrAyGEqErh-RgODzJrwwC4>
Subject: Re: [Ntp] I-D Action: draft-ietf-ntp-using-nts-for-ntp-26.txt
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, 23 Mar 2020 10:02:20 -0000

> On 23 Mar 2020, at 09:08, Hal Murray <hmurray@megapathdsl.net> wrote:
> 
> 
> ragge@netnod.se said:
>> If you actually have users: Note that it isn’t forbidden to support both, but
>> preferably only for a while, I believe in the server would be easiest, the
>> most natural, and then you could log any usage of the old one. 
> 
> How do you support both?  How does either the client or server know which one 
> the other is going to use?  That string doesn't get sent across the wire.

Right, sorry!

The server would have to keep track of that client and try the other one
the next time, or something like that, and you would have to switch
at the next connection before TLS starts (ugly, almost horrible...)

> We are talking about the "TLS export disambiguating label string" used to make the client-2-server and server-2-client keys.  Right?

We are.

/ragge

v2.23.0 | Report a Bug | By Email