IETF Logo Mail Archive

[Cbor] Base-URI Re: [core] WG Last Call on draft-ietf-core-problem-details

Carsten Bormann <cabo@tzi.org> Wed, 25 May 2022 10:28 UTC

Return-Path: <cabo@tzi.org>
X-Original-To: cbor@ietfa.amsl.com
Delivered-To: cbor@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2E89BC15E6D3; Wed, 25 May 2022 03:28:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, 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 EsI-5W1xIzia; Wed, 25 May 2022 03:28:16 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 8403BC15E6CD; Wed, 25 May 2022 03:28:15 -0700 (PDT)
Received: from [192.168.217.118] (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4L7S2N1Kz3zDCdj; Wed, 25 May 2022 12:28:12 +0200 (CEST)
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: <YoesjAXIKQS+PBLX@hephaistos.amsuess.com>
Date: Wed, 25 May 2022 12:28:11 +0200
Cc: draft-ietf-core-problem-details@ietf.org, "core@ietf.org WG (core@ietf.org)" <core@ietf.org>, cbor@ietf.org, httpapi@ietf.org
X-Mao-Original-Outgoing-Id: 675167291.743299-b276c98b42182f1bede5b0153469cdc0
Content-Transfer-Encoding: quoted-printable
Message-Id: <18CB1C8E-651F-48C9-8D32-55E1CAEDC63D@tzi.org>
References: <3a2fb1c8-5c50-fa7a-0672-a73c3b6f1a5f@ri.se> <YoesjAXIKQS+PBLX@hephaistos.amsuess.com>
To: Christian Amsüss <christian@amsuess.com>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/cbor/1pdOB9Gdq3cUfq8kDaFAJY9uuqU>
Subject: [Cbor] Base-URI Re: [core] WG Last Call on draft-ietf-core-problem-details
X-BeenThere: cbor@ietf.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "Concise Binary Object Representation \(CBOR\)" <cbor.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cbor>, <mailto:cbor-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cbor/>
List-Post: <mailto:cbor@ietf.org>
List-Help: <mailto:cbor-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cbor>, <mailto:cbor-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2022 10:28:19 -0000

> * The presence of the response-code attribute implies to me that this is
>  intended for persisting the problem details, and/or for exposing them
>  on a different protocol. Both usually bring a change in the Base URI,
>  so whoever sets the response-code WOULD PROBABLY also want to resolve
>  the instance URI.
> 
>  And what of URIs for which the entity that adds the response-code
>  doesn't even know they're URIs?

Exactly (after s/URIs/URI references/).  
So resolving the instance URI reference is not enough; preserving more of the context would be.

There probably should be a general means for preserving a base URI with a stored (or otherwise uprooted) representation of response content (think file-magic…). Adding

For now we could decide to put in another SPDe for the base URI.

Let’s discuss this today.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email