IETF Logo Mail Archive

Re: [core] New Version Notification for draft-amsuess-core-pd-body-error-position-00.txt

Carsten Bormann <cabo@tzi.org> Mon, 06 February 2023 13:51 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: core@ietfa.amsl.com
Delivered-To: core@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0A874C14CF13 for <core@ietfa.amsl.com>; Mon, 6 Feb 2023 05:51:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.188
X-Spam-Level:
X-Spam-Status: No, score=-4.188 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, T_SPF_TEMPERROR=0.01] autolearn=ham autolearn_force=no
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 RQDeeqk635yt for <core@ietfa.amsl.com>; Mon, 6 Feb 2023 05:51:20 -0800 (PST)
Received: from smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71FA8C14CE3F for <core@ietf.org>; Mon, 6 Feb 2023 05:51:18 -0800 (PST)
Received: from [192.168.217.124] (p548dc9a4.dip0.t-ipconnect.de [84.141.201.164]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4P9SN44wchzDCnC; Mon, 6 Feb 2023 14:51:16 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <CAObGJnN5=MjnBNiWS8gdNcPXAZHFTQtBmzvR30HjpkMxzSMe+g@mail.gmail.com>
Date: Mon, 06 Feb 2023 14:51:16 +0100
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, Christian Amsüss <christian@amsuess.com>, core@ietf.org
X-Mao-Original-Outgoing-Id: 697384276.103416-0ac7f4af20d3539c485f13a73582b1e5
Content-Transfer-Encoding: quoted-printable
Message-Id: <81A45221-48F1-460F-A191-CAA1624A7409@tzi.org>
References: <Y97e6dWnME7brk7r@hephaistos.amsuess.com> <2225873.1675603784@dyas> <CAObGJnNiy6sWBQnoCq6LzSxDv+m26aqORKvDp0sjTFh0uwQCbw@mail.gmail.com> <2297764.1675690174@dyas> <CAObGJnN5=MjnBNiWS8gdNcPXAZHFTQtBmzvR30HjpkMxzSMe+g@mail.gmail.com>
To: Thomas Fossati <tho.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/Uz3w980FlMWX-dyzla75xR5QtWM>
Subject: Re: [core] New Version Notification for draft-amsuess-core-pd-body-error-position-00.txt
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "Constrained RESTful Environments \(CoRE\) Working Group list" <core.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/core>, <mailto:core-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/core/>
List-Post: <mailto:core@ietf.org>
List-Help: <mailto:core-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/core>, <mailto:core-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Feb 2023 13:51:27 -0000

>> I am sad that publishing an RFC is (rightly) perceived as having become such a large effort.

Indeed.

> Are you thinking of a "IANA track" for RFCs that only register
> codepoints, which would avoid going through the massive IETF QA
> process?

This registry doesn’t need an RFC for its "specification required" ranges.

For comparison, many CBOR tags are registered based on Github repos.
We could do this here, but an archivable IETF document is better.
Hence an I-D.

We have managed to move tag 38 from a github repo to an RFC, and I think that “large effort” is the understatement of the decade :-)

The notable-tags draft was started to provide a better home for many of the registrations.
I think we can extend the idea of this draft to problem details and other map key registration registries; it is just intended for a different WG.
So we could do a notable-core-parameters draft; maybe not a bad idea after all with all those weird CoAP options out there...

Grüße, Carsten

v2.23.0 | Report a Bug | By Email