IETF Logo Mail Archive

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

Michael Richardson <mcr+ietf@sandelman.ca> Sun, 05 February 2023 13:29 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 D4587C14F6EC for <core@ietfa.amsl.com>; Sun, 5 Feb 2023 05:29:49 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] 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 SFeKrmYfPPLR for <core@ietfa.amsl.com>; Sun, 5 Feb 2023 05:29:48 -0800 (PST)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00:e000:2bb::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A81EC14F6EB for <core@ietf.org>; Sun, 5 Feb 2023 05:29:47 -0800 (PST)
Received: from dyas.sandelman.ca (dynamic-089-204-154-071.89.204.154.pool.telefonica.de [89.204.154.71]) by relay.sandelman.ca (Postfix) with ESMTPS id CF98C1F47B; Sun, 5 Feb 2023 13:29:45 +0000 (UTC)
Received: by dyas.sandelman.ca (Postfix, from userid 1000) id 3A120A1E6E; Sun, 5 Feb 2023 08:29:44 -0500 (EST)
Received: from dyas (localhost [127.0.0.1]) by dyas.sandelman.ca (Postfix) with ESMTP id 377E6A1DF3; Sun, 5 Feb 2023 14:29:44 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>, core@ietf.org
In-reply-to: <Y97e6dWnME7brk7r@hephaistos.amsuess.com>
References: <Y97e6dWnME7brk7r@hephaistos.amsuess.com>
Comments: In-reply-to Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com> message dated "Sat, 04 Feb 2023 23:40:41 +0100."
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.3
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha512"; protocol="application/pgp-signature"
Date: Sun, 05 Feb 2023 14:29:44 +0100
Message-ID: <2225873.1675603784@dyas>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/KFhpVn1c16C5NSRxaMZJh7w_ODI>
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: Sun, 05 Feb 2023 13:29:49 -0000

Christian Amsüss <christian@amsuess.com> wrote:
    > While no WG or even IETF action is required for this, I'd appreciate a
    > few eyes and/or comments before sending this to IANA and eventually the
    > experts, Thomas and Carsten.

I read the document.
I am saddened by Document Lifecycle, but I understand it.
I found a few places where the wording was difficult, and I'll try to send
you some wordsmithing, but fundamentally it all made sense to me, and I had
little to add.

I have frequently been frustrated with (Li)nux kernel's use of EINVAL as a
"you lose" error value, when there are potentially dozens of places I could
have gone wrong.  Did I really need to do printk() debugging to figure out
what I was doing wrong?   I wish that the kernel could have told me where my
input was wrong.

So I applaud this effort.

--
Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

v2.23.0 | Report a Bug | By Email