Re: [httpapi] [Technical Errata Reported] RFC9457 (7731)

Erik Wilde <erik.wilde@dret.net> Thu, 14 December 2023 09:00 UTC

Return-Path: <erik.wilde@dret.net>
X-Original-To: httpapi@ietfa.amsl.com
Delivered-To: httpapi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6DC18C14F5EC for <httpapi@ietfa.amsl.com>; Thu, 14 Dec 2023 01:00:27 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.908
X-Spam-Level:
X-Spam-Status: No, score=-6.908 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable 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 bQfoLKpQ53Bv for <httpapi@ietfa.amsl.com>; Thu, 14 Dec 2023 01:00:25 -0800 (PST)
Received: from mxout012.mail.hostpoint.ch (mxout012.mail.hostpoint.ch [IPv6:2a00:d70:0:e::312]) (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 46572C14F5FA for <httpapi@ietf.org>; Thu, 14 Dec 2023 01:00:19 -0800 (PST)
Received: from [10.0.2.45] (helo=asmtp012.mail.hostpoint.ch) by mxout012.mail.hostpoint.ch with esmtps (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.96.2 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1rDhZl-0003Ct-0h; Thu, 14 Dec 2023 10:00:13 +0100
Received: from [185.110.72.103] (helo=[192.168.1.135]) by asmtp012.mail.hostpoint.ch with esmtpa (Exim 4.96.2 (FreeBSD)) (envelope-from <erik.wilde@dret.net>) id 1rDhZk-000NQo-0d; Thu, 14 Dec 2023 10:00:13 +0100
X-Authenticated-Sender-Id: erik.wilde@dret.net
Message-ID: <4db72919-cb1c-46df-9f57-1ed10c782da2@dret.net>
Date: Thu, 14 Dec 2023 10:00:11 +0100
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
To: RFC Errata System <rfc-editor@rfc-editor.org>, mnot@mnot.net, sanjay.dalal@cal.berkeley.edu, superuser@gmail.com, francesca.palombini@ericsson.com, darrel@tavis.ca, rsalz@akamai.com
Cc: roman.kovarik@magnolia-cms.com, httpapi@ietf.org
References: <20231214080037.C84E919864E3@rfcpa.amsl.com>
From: Erik Wilde <erik.wilde@dret.net>
In-Reply-To: <20231214080037.C84E919864E3@rfcpa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Vs-State: 0
Archived-At: <https://mailarchive.ietf.org/arch/msg/httpapi/3O9ME-tWI5DxKt7NlST1lETijmY>
Subject: Re: [httpapi] [Technical Errata Reported] RFC9457 (7731)
X-BeenThere: httpapi@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Building Blocks for HTTP APIs <httpapi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/httpapi>, <mailto:httpapi-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/httpapi/>
List-Post: <mailto:httpapi@ietf.org>
List-Help: <mailto:httpapi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/httpapi>, <mailto:httpapi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 14 Dec 2023 09:00:27 -0000

hello.

On 2023-12-14 09:00, RFC Errata System wrote:
> Notes
> -----
> As the schema doesn't have  "additionalProperties": true, the schema validation fails with additional fields although those are allowed according to https://www.rfc-editor.org/rfc/rfc9457#name-extension-members. Also the example in https://www.rfc-editor.org/rfc/rfc9457#name-the-problem-details-json-ob fails the validation for the same reason.
> 
> --------------------------------------
> RFC9457 (draft-ietf-httpapi-rfc7807bis-07)
> --------------------------------------
> Title               : Problem Details for HTTP APIs
> Publication Date    : July 2023
> Author(s)           : M. Nottingham, E. Wilde, S. Dalal
> Category            : PROPOSED STANDARD
> Source              : Building Blocks for HTTP APIs
> Area                : Applications and Real-Time
> Stream              : IETF
> Verifying Party     : IESG

that seems like a valid and useful point to me. given the extension 
model that the spec describes the schema should be designed to 
accommodate extensions, if present.

thanks and cheers,

dret.

-- 
Erik Wilde | mailto:erik.wilde@dret.net    |
            | https://youtube.com/ErikWilde |