Re: [core] Review of draft-fossati-core-coap-problem-02

Christian Amsüss <christian@amsuess.com> Tue, 07 April 2020 12:32 UTC

Return-Path: <christian@amsuess.com>
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 914B03A080E; Tue, 7 Apr 2020 05:32:39 -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, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tdRaz_B_mbt1; Tue, 7 Apr 2020 05:32:37 -0700 (PDT)
Received: from prometheus.amsuess.com (prometheus.amsuess.com [5.9.147.112]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 518873A0805; Tue, 7 Apr 2020 05:32:36 -0700 (PDT)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id C7AA540142; Tue, 7 Apr 2020 14:32:32 +0200 (CEST)
Received: from poseidon-mailbox.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bf]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id 0AA8814B; Tue, 7 Apr 2020 14:32:31 +0200 (CEST)
Received: from hephaistos.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:2d54:7976:cdc9:1eab]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id BD7E4381; Tue, 7 Apr 2020 14:32:30 +0200 (CEST)
Received: (nullmailer pid 2762080 invoked by uid 1000); Tue, 07 Apr 2020 12:32:30 -0000
Date: Tue, 7 Apr 2020 14:32:30 +0200
From: Christian =?iso-8859-1?Q?Ams=FCss?= <christian@amsuess.com>
To: Jim Schaad <ietf@augustcellars.com>, Thomas Fossati <Thomas.Fossati@arm.com>
Cc: draft-fossati-core-coap-problem@ietf.org, core@ietf.org
Message-ID: <20200407123230.GC2743407@hephaistos.amsuess.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="xgyAXRrhYN0wYx8y"
Content-Disposition: inline
In-Reply-To: <703EAB3E-A9CC-4260-8B52-6690BACFA62C@arm.com> <010b01d6076d$ab36bfd0$01a43f70$@augustcellars.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/aypkvGo5fnBGrWUTtAJAVBz5BBE>
Subject: Re: [core] Review of draft-fossati-core-coap-problem-02
X-BeenThere: core@ietf.org
X-Mailman-Version: 2.1.29
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: Tue, 07 Apr 2020 12:32:40 -0000

Hello Thomas and Jim,

On Wed, Apr 01, 2020 at 10:36:10AM +0000, Thomas Fossati wrote:
> > [JLS] Given that I would want to test the problem info being returned,
> > getting unexpected errors with information is useful for me.  This is
> > the basic method that I have been using for my ACE server where a
> > diagnostic string with the problem details is returned, but a stack
> > trace is included in unexpected conditions (i.e. the code threw an
> > exception).
> 
> I am certainly not opposed to that.  Happy to call it "diagnostic"?

Are these cases not independent cases anyway?

If there is a known condition, its problem-detail is returned. On
exceptions, there is no problem-detail but a stack-trace (without a
content format).

Of course, a framework might create an entry for (ns=my-framework,
type=0, title="Exception in resource handler", response-code=5.00,
coapp-roblem-details-extension = [* stackframe])

But as I understand that use case, you don't need both simultaneously.

KR
c

-- 
You don't use science to show that you're right, you use science to
become right.
  -- Randall Munroe