IETF Logo Mail Archive

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

Hal Murray <hmurray@megapathdsl.net> Mon, 23 March 2020 08:08 UTC

Return-Path: <hmurray@megapathdsl.net>
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 A42E43A08BD for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 01:08:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.035
X-Spam-Level: **
X-Spam-Status: No, score=2.035 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CTE_8BIT_MISMATCH=0.998, HELO_DYNAMIC_IPADDR=1.951, PP_MIME_FAKE_ASCII_TEXT=0.001, RDNS_DYNAMIC=0.982, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 qxOaOzMJ8sOL for <ntp@ietfa.amsl.com>; Mon, 23 Mar 2020 01:08:13 -0700 (PDT)
Received: from ip-64-139-1-69.sjc.megapath.net (ip-64-139-1-69.sjc.megapath.net [64.139.1.69]) by ietfa.amsl.com (Postfix) with ESMTP id ED6D73A08A6 for <ntp@ietf.org>; Mon, 23 Mar 2020 01:08:11 -0700 (PDT)
Received: from shuksan (localhost [127.0.0.1]) by ip-64-139-1-69.sjc.megapath.net (Postfix) with ESMTP id AABC540605C; Mon, 23 Mar 2020 01:08:10 -0700 (PDT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.3
To: Ragnar Sundblad <ragge@netnod.se>
cc: Watson Ladd <watsonbladd@gmail.com>, Hal Murray <hmurray@megapathdsl.net>, NTP WG <ntp@ietf.org>
From: Hal Murray <hmurray@megapathdsl.net>
In-Reply-To: Message from Ragnar Sundblad <ragge@netnod.se> of "Mon, 23 Mar 2020 08:38:35 BST." <2410977C-1EF3-43BF-BD81-54563E5D153A@netnod.se>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 23 Mar 2020 01:08:10 -0700
Message-Id: <20200323080810.AABC540605C@ip-64-139-1-69.sjc.megapath.net>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/VZm1satf3kQj-LGy6huWf2xXZh8>
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 08:08:18 -0000

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.

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

-- 
These are my opinions.  I hate spam.

v2.23.0 | Report a Bug | By Email