[Ntp] Antw: [EXT] Re: New Version Notification for draft-rsalz-update-registries-00.txt
Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de> Tue, 19 January 2021 07:46 UTC
Return-Path: <Ulrich.Windl@rz.uni-regensburg.de>
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 1626B3A12A7 for <ntp@ietfa.amsl.com>; Mon, 18 Jan 2021 23:46:11 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable 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 lEQ0AXS9LZMp for <ntp@ietfa.amsl.com>; Mon, 18 Jan 2021 23:46:06 -0800 (PST)
Received: from mx2.uni-regensburg.de (mx2.uni-regensburg.de [IPv6:2001:638:a05:137:165:0:3:bdf8]) (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 46BC93A13DD for <ntp@ietf.org>; Mon, 18 Jan 2021 23:45:41 -0800 (PST)
Received: from mx2.uni-regensburg.de (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5AFBA6000052 for <ntp@ietf.org>; Tue, 19 Jan 2021 08:45:37 +0100 (CET)
Received: from gwsmtp.uni-regensburg.de (gwsmtp1.uni-regensburg.de [132.199.5.51]) by mx2.uni-regensburg.de (Postfix) with ESMTP id 35B9B6000051 for <ntp@ietf.org>; Tue, 19 Jan 2021 08:45:29 +0100 (CET)
Received: from uni-regensburg-smtp1-MTA by gwsmtp.uni-regensburg.de with Novell_GroupWise; Tue, 19 Jan 2021 08:45:29 +0100
Message-Id: <60068E16020000A10003E53C@gwsmtp.uni-regensburg.de>
X-Mailer: Novell GroupWise Internet Agent 18.3.0
Date: Tue, 19 Jan 2021 08:45:26 +0100
From: Ulrich Windl <Ulrich.Windl@rz.uni-regensburg.de>
To: Rich Salz <rsalz=40akamai.com@dmarc.ietf.org>, Daniel Franke <dfoxfranke@gmail.com>, stenn@nwtime.org, mayer@pdmconsulting.net
Cc: "ntp@ietf.org" <ntp@ietf.org>, mlichvar@redhat.com
References: <160866842930.12375.2768184613474168188@ietfa.amsl.com> <8E362353-B91C-445B-B16E-166BE3A9045A@akamai.com> <20210104144735.GA2992437@localhost> <3FBAA9E7-A251-4C68-9231-A0271227EF6C@akamai.com> <43EFABEB-5829-443B-A29B-C3B4D1228BFD@akamai.com> <CAJm83bB3DmjF0y0G-FC-s_bHCW3-tw5SDpko8Eoftt9QsH8xcQ@mail.gmail.com> <A0E76A23-7064-4800-A821-62BA22F12257@akamai.com> <4b46f71b-34b7-9342-f3ec-48f094dd75c6@pdmconsulting.net> <148533b9-972d-331a-3ae5-06914456194e@nwtime.org> <b2098c1d-71f3-478c-ff29-c97ae35c626a@pdmconsulting.net>
In-Reply-To: <b2098c1d-71f3-478c-ff29-c97ae35c626a@pdmconsulting.net>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Archived-At: <https://mailarchive.ietf.org/arch/msg/ntp/jmYyJyeAPq-NobfAEyZ_ch_MWW4>
Subject: [Ntp] Antw: [EXT] Re: 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: Tue, 19 Jan 2021 07:46:11 -0000
>>> Danny Mayer <mayer@pdmconsulting.net> schrieb am 19.01.2021 um 02:24 in Nachricht <b2098c1d-71f3-478c-ff29-c97ae35c626a@pdmconsulting.net>: > On 1/18/21 12:29 AM, Harlan Stenn wrote: >> Danny, >> >> On 1/17/2021 7:35 PM, Danny Mayer wrote: >>> On 1/6/21 2:51 PM, Salz, Rich wrote: >>>> On Wed, Jan 6, 2021 at 10:42 AM Salz, Rich >>>> <rsalz=40akamai.com@dmarc.ietf.org >>>> <mailto:40akamai.com@dmarc.ietf.org>> wrote: >>>> >>>> And also where are the response and error flags defined? A quick >>>> search in RFC 5905 didn't find anything obvious. >>>> >>>> * They're only defined within the context of Autokey. RFC 5906 >>>> describes them, but fails to reserve the registry space that it >>>> would need to use them correctly. >>>> >>>> >>>> >>>> Thanks for the pointer. Reading Section 10 of RFC 5906 closely, it >>>> looks like the partitioning of the field type into R/E/Code/Field >>>> parts is limited purely to autokey, and not intended to apply to >>>> extensions overall. >>>> >>>> >>>> >>> That was the intent of the registry entries and it may have been >>> incorrectly set up. It was a bad idea to put these bits into the >>> extension id field in the first place so this was the best way to >>> reserve the fields so that the rest of the ID's were available without >>> totally destroying the way extension fields were meant to be. >> Are you talking about the top few bits of the EF? If so, I'd agree with >> you if you were right. >> >> There's clear implementation benefit to having at least the >> Query/Response bit visible very early. I've written about this many >> times. Dave has said this, too. > I don't disagree that having the Query/Response/Error bits visible very > early. The disagreement is where they should go. They belong in the body > of the extension field and not in the extension field ID. The bits are > private to the extension field. Nothing else needs to know about them. I fully agree. >> It is a clear feature, not a bug. > It's a misimplemented feature. I'm not calling it a bug. >>> It took a while to get this set up but at least it allowed autokey >>> (RFC5906) to move forward. >> Huh? >> > I spent 3 months working on this with Dave to get this RFC draft into a > form acceptable to the IETF because of this issue. > > Danny > > _______________________________________________ > ntp mailing list > ntp@ietf.org > https://www.ietf.org/mailman/listinfo/ntp
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Daniel Franke
- Re: [Ntp] New Version Notification for draft-rsal… Miroslav Lichvar
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Daniel Franke
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Miroslav Lichvar
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Salz, Rich
- Re: [Ntp] New Version Notification for draft-rsal… Danny Mayer
- Re: [Ntp] New Version Notification for draft-rsal… Harlan Stenn
- Re: [Ntp] New Version Notification for draft-rsal… Danny Mayer
- [Ntp] Antw: [EXT] Re: New Version Notification fo… Ulrich Windl
- Re: [Ntp] Antw: [EXT] Re: New Version Notificatio… Salz, Rich