IETF Logo Mail Archive

Re: [Ntp] Quick review of WGLC for status change for draft-ietf-ntp-update-registries

Miroslav Lichvar <mlichvar@redhat.com> Wed, 17 August 2022 09:00 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 4193DC14CE23 for <ntp@ietfa.amsl.com>; Wed, 17 Aug 2022 02:00:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.678
X-Spam-Level:
X-Spam-Status: No, score=-7.678 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.571, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=redhat.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VXYYUWR7PuAV for <ntp@ietfa.amsl.com>; Wed, 17 Aug 2022 02:00:32 -0700 (PDT)
Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5026C14CF0B for <ntp@ietf.org>; Wed, 17 Aug 2022 02:00:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1660726831; 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: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=sAzL0pBe40c0Xjg9lLcs19LOXu41446L7vl3267EVxs=; b=ZOhx1RjGtc2fV6u4Lg8ritYBLGbTPgS9afTD+F4v0lUWylkMkyci1UcwpwajqVUx7mMugA QcGVovA1FUlMxRly+ExvkRmVq6psUZIKy/yULJLHC6H9CPgyf3O+xzght/jZwvGC5rksfr k/pRbzjmtk0LnuKQuS8nZ1dtroZxfJY=
Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-141-vWi-tzcENk6KsUpO_MLE7A-1; Wed, 17 Aug 2022 05:00:27 -0400
X-MC-Unique: vWi-tzcENk6KsUpO_MLE7A-1
Received: from smtp.corp.redhat.com (int-mx09.intmail.prod.int.rdu2.redhat.com [10.11.54.9]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 802CA3C11046; Wed, 17 Aug 2022 09:00:27 +0000 (UTC)
Received: from localhost (unknown [10.43.135.229]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 83F67492CA5; Wed, 17 Aug 2022 09:00:25 +0000 (UTC)
Date: Wed, 17 Aug 2022 11:00:24 +0200
From: Miroslav Lichvar <mlichvar@redhat.com>
To: Harlan Stenn <stenn@nwtime.org>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Danny Mayer <mayer@pdmconsulting.net>, "ntp@ietf.org" <ntp@ietf.org>
Message-ID: <YvyuKIG5SthVkgTh@localhost>
References: <0b57b7db-772e-f5e6-e6a0-a433673f3d77@nwtime.org> <YvED7T5R0UsRWbv3@localhost> <b64c6a0a-ea2e-0a19-4bb9-38bfaa2e5032@nwtime.org> <YvIUIu1LaloEjJMb@localhost> <a500eea8-e6a1-c10f-2385-3a05fb0e9638@pdmconsulting.net> <Yvomi1Y5hWhPi8Av@localhost> <4723f2b2-43b0-a9ee-4d80-6e31d74b9d3a@pdmconsulting.net> <YvtBSLkHF1JpGH07@localhost> <A2E4FF6B-89FE-41B0-9047-7A64ED3411CD@akamai.com> <39f8b373-20c1-ad2f-de3c-22902eb2ea4f@nwtime.org>
MIME-Version: 1.0
In-Reply-To: <39f8b373-20c1-ad2f-de3c-22902eb2ea4f@nwtime.org>
X-Scanned-By: MIMEDefang 2.85 on 10.11.54.9
X-Mimecast-Spam-Score: 0
X-Mimecast-Originator: redhat.com
Content-Type: text/plain; charset="WINDOWS-1252"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/1qg0B4MHQQBu9hBq06_6JqPDhQg>
Subject: Re: [Ntp] Quick review of WGLC for status change for draft-ietf-ntp-update-registries
X-BeenThere: ntp@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Network Time Protocol <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, 17 Aug 2022 09:00:38 -0000

On Tue, Aug 16, 2022 at 05:27:53PM -0700, Harlan Stenn wrote:
> On 8/16/2022 6:32 AM, Salz, Rich wrote:
> >  >    The document discussed here is trying
> >  >    to update the IANA table to include both sets of values in order to
> >  >    prevent conflicts with newly specified extension fields, as already
> >  >    happened with NTS.
> > 
> > Yes, exactly.
> 
> Shenanigans.
> 
> I have asked for specific details about the conflict and nobody has answered
> me.

The main problem is that the conflict exists.

I agree that in this specific case it can be resolved by sufficiently
robust NTP implementation. Nobody is saying that it cannot be done.
But it shouldn't be necessary. If there was a conflict between
different extension fields, it might not be possible.

The whole point of maintaning the IANA table is to avoid conflicts and
enable interoperability between different implementations.

-- 
Miroslav Lichvar

v2.23.0 | Report a Bug | By Email