[Ntp] Flag day (was Re: Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard)

Watson Ladd <watsonbladd@gmail.com> Wed, 19 February 2020 14:55 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 7806B1200B5 for <ntp@ietfa.amsl.com>; Wed, 19 Feb 2020 06:55:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
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: 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 3a8xqdz6d_r2 for <ntp@ietfa.amsl.com>; Wed, 19 Feb 2020 06:55:51 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::22c]) (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 76203120129 for <ntp@ietf.org>; Wed, 19 Feb 2020 06:55:51 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id r19so695431ljg.3 for <ntp@ietf.org>; Wed, 19 Feb 2020 06:55:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=Q1/WEttKAXoWz4/kijJH2WSQClWKVyrYGrdtpJrazhE=; b=SBPndE/2iXz3gGR9Y7zQdZRUhLjRf+joMXjvVF8cSsSn7u40kdGOZETHMAszacfFqr 5amJQgdh6/pFk5f07xk/1j2slMlKoPG+Fu/k4Ftz8S0pzzEA2bdXh3+ldgqsZ5ItTKru bgDODq+wILRbHcd4IlJWc/RpOC8eakHYhCsajz3eGL+gbjoj75Vm2Y1L9eOoVmimxCar I5KKLjhGlYTC7gsIBHC2blqT6Ee75UY2dL93Yzg3wvIWDQkDaGuI7t9KWt54HGkESUHK Zu9GKgSLS8Xv+8NML9H2kr8Pxx0MG0aTR5wkqXA/Uv5Sb1f1b5C4yO7gWLK6S+hEi725 I//Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=Q1/WEttKAXoWz4/kijJH2WSQClWKVyrYGrdtpJrazhE=; b=UHIXVY37Y0FyHjYCTDAFcMWL1fJDS0LVahwxPCYjCk+9/NfhquikOXRiT2S9MmjW68 9LBmjv2mj2H69rvvPgnpj/CSQd8evutU7ghNjvhnodFBdNtk21Gfcks7l17+A9rTwi5z hdJq2buXOC2izrV3T0VylnwPIQsiilRXibN37Ep+cFVfi5qsOGSY82Yr8JbPz7I8UxC/ mzjiwhNgU7vjl63ixLL3LDYenMcTABlAsPn2C9XWT0z5oBcrRTyzsG1EnnkD41/DA4id GDVcawFhd9Aw3eqyZJWlPzKcApg0pmMR2BIFUs/mzEm7D8tbVvplNeI7jzzZYXLFUJhT OvMQ==
X-Gm-Message-State: APjAAAV8EJEP6t6VF6sD3jqLADkTNT3u7in3zuS87DHbFL+czqDGWjEr JCZv7D0y8bAR/v/0/IMXKmIfxJT1Gz4DMjOTA2y57L7C
X-Google-Smtp-Source: APXvYqweyo4qdYVpza7p6Wt+bjEsUFCxj4fAiERG4Hbrkl7kn+fW6bnaVTuusumloGMKkLip7pz8vlwJDLzEOItMPlc=
X-Received: by 2002:a2e:98ca:: with SMTP id s10mr16272865ljj.160.1582124149500; Wed, 19 Feb 2020 06:55:49 -0800 (PST)
MIME-Version: 1.0
From: Watson Ladd <watsonbladd@gmail.com>
Date: Wed, 19 Feb 2020 06:55:38 -0800
Message-ID: <CACsn0cn9RnKz+3BF8yStQugu8EtCTjM-6F7LRzuaERJ_Mbi5-w@mail.gmail.com>
To: Miroslav Lichvar <mlichvar@redhat.com>
Cc: NTP WG <ntp@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/oKaHIEncolE8I3dbn8gijoK4xVo>
Subject: [Ntp] Flag day (was Re: Last Call: <draft-ietf-ntp-using-nts-for-ntp-22.txt> (Network Time Security for the Network Time Protocol) to Proposed Standard)
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: Wed, 19 Feb 2020 14:55:56 -0000

>
> Yes, that would help. However, the NTS-KE port is different between
> the implementations, so there will still probably be a flag day.

At least for my implementation it's a configuration detail.

We could start listening on the new port, then drop the old one
slowly. Right now I'm seeing very little NTS traffic, but changing the
ports will take me a few days, so I might do it in one shot unless I
hear otherwise.

I believe at the virtual interim we discussed an IANA early request as
a means to get ahead of the RFC publication process: I'm not sure if
on was made or not. For flags the flags we are using would be part of
the IANA request.

Unfortunately there has been a lot of controversy over flag
assignments, with one implementation and Wireshark asserting structure
on flag assignments that doesn't actually exist. I'd prefer we have a
delineated experimental range and have the flags we were using come
from that, and instead use flags from a non-experimental range, but
maybe I can't always get what I want.

Sincerely,
Watson Ladd