IETF Logo Mail Archive

Re: [Ntp] New Version Notification for draft-rsalz-update-registries-00.txt

Miroslav Lichvar <mlichvar@redhat.com> Mon, 04 January 2021 14:47 UTC

Return-Path: <mlichvar@redhat.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 EBCC23A0D96 for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 06:47:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.469
X-Spam-Level:
X-Spam-Status: No, score=-0.469 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.25, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.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 IdpOwvOVLaOG for <ntp@ietfa.amsl.com>; Mon, 4 Jan 2021 06:47:44 -0800 (PST)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [63.128.21.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67CFB3A0D95 for <ntp@ietf.org>; Mon, 4 Jan 2021 06:47:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1609771663; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=c3qIymBIa2DgRK2GQVp3bZRve2eXJqqBuI8ZAu3+ibE=; b=D9Ud6l51rtf22QZXgEhYyKYdr4i8uGz14kdc/wA22F2TyAB81Jzz2x6ww2ZgLKzuSHmsoB IA/N03eSemHK8Z/tIoTDmrXFPCJsQtPISjljCnCu/2VYrvyrJrtM/Ot2rvkbip757RqVmD M6X6s0Kj+FKtnWUvmY1gH1ZLkVaEiAE=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com [209.132.183.4]) (Using TLS) by relay.mimecast.com with ESMTP id us-mta-418-_FGqGmTnPUa6Pkvg1RtpKg-1; Mon, 04 Jan 2021 09:47:40 -0500
X-MC-Unique: _FGqGmTnPUa6Pkvg1RtpKg-1
Received: from smtp.corp.redhat.com (int-mx05.intmail.prod.int.phx2.redhat.com [10.5.11.15]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 30A1F80ED8A; Mon, 4 Jan 2021 14:47:39 +0000 (UTC)
Received: from localhost (holly.tpb.lab.eng.brq.redhat.com [10.43.134.11]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 6C65F5D756; Mon, 4 Jan 2021 14:47:37 +0000 (UTC)
Date: Mon, 04 Jan 2021 15:47:35 +0100
From: Miroslav Lichvar <mlichvar@redhat.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
Cc: "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <20210104144735.GA2992437@localhost>
References: <160866842930.12375.2768184613474168188@ietfa.amsl.com> <8E362353-B91C-445B-B16E-166BE3A9045A@akamai.com>
MIME-Version: 1.0
In-Reply-To: <8E362353-B91C-445B-B16E-166BE3A9045A@akamai.com>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.15
Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=mlichvar@redhat.com
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/QACrUNGJo6rMJc9wJ32ZWE-_Xq8>
Subject: Re: [Ntp] New Version Notification for draft-rsalz-update-registries-00.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, 04 Jan 2021 14:47:46 -0000

On Tue, Dec 22, 2020 at 08:25:49PM +0000, Salz, Rich wrote:
> This is the promise draft to update all NTP/NTS registries.  Contributions, pull requests, etc., encouraged.  Discuss on this list, or at https://github.com/richsalz/draft-rsalz-update-registries

Is it ok to refer to RFC 5906 for the swapped values, when it's only
used by the (one existing) implementation and not the specification?

I liked the Daniel's idea to keep them both, the original values
unchanged and then mark the swapped set as reserved, occupied, or
similar.

I'm ok with the the proposed range 0xD000-0xFFFF for experimenal
extension fields, but others here probably will not like it as it will
randomly set the "response" and "error" flags in their interpretation
of the value.

Thanks,

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email