[core] Fwd: I-D Action: draft-ietf-core-problem-details-02.txt

[Carsten Bormann <[e-mail]>]

The problem-details specification has been parked for a while
(since July 2020) waiting for CoRAL to complete.

In the meantime, 3GPP has written the problem-details specification
into their client-server specifications and is expecting to cut a
release in June 2022.
It is unlikely that the CoRAL is complete by then.
This would cause problem-details to be written out of the specification
(and probably be replaced by an ad-hoc mechanism).

The trial ballon that -02 is, proposes to define a concise problem 
details structure that is simple enough so it can be completed 
within a couple of months.
This would keep the problem details approach within the 3GPP system
and will allow us to add a more complete CoRAL version later.

Note that Thomas also has a slightly different approach that we should
explore; we have an agenda item for that later today at the CoRE interim 
(and I hope to have my slides for that up soon).

Grüße, Carsten


> Begin forwarded message:
> 
> From: [e-mail]
> Subject: [core] I-D Action: draft-ietf-core-problem-details-02.txt
> Date: 2022-04-27 at 13:01:40 CEST
> To: <[e-mail]>
> Cc: [e-mail]
> Reply-To: [e-mail]
> Archived-At: <https://mailarchive.ietf.org/arch/msg/core/QQCfTB5uN55-_cSGjebXkPJdd_Y>
> Message-Id: <[e-mail]>
> 
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Constrained RESTful Environments WG of the IETF.
> 
>        Title           : Concise Problem Details For CoAP APIs
>        Authors         : Thomas Fossati
>                          Carsten Bormann
> 	Filename        : draft-ietf-core-problem-details-02.txt
> 	Pages           : 10
> 	Date            : 2022-04-27
> 
> Abstract:
>   This document defines a "problem detail" as a way to carry machine-
>   readable details of errors in a REST response to avoid the need to
>   define new error response formats for REST APIs.  The format is
>   inspired by, but intended to be more concise than, the Problem
>   Details for HTTP APIs defined in RFC 7807.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-core-problem-details/
> 
> There is also an HTML version available at:
> https://www.ietf.org/archive/id/draft-ietf-core-problem-details-02.html
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-core-problem-details-02