IETF Logo Mail Archive

Re: [core] I-D Action: draft-ietf-core-stateless-01.txt

Christian Amsüss <christian@amsuess.com> Tue, 26 March 2019 09:30 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 246461202A1; Tue, 26 Mar 2019 02:30:06 -0700 (PDT)
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, URIBL_BLOCKED=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 qnUEsXcAJQe6; Tue, 26 Mar 2019 02:30:03 -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 9EB28120282; Tue, 26 Mar 2019 02:30:00 -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 AC2EC4380B; Tue, 26 Mar 2019 10:29:58 +0100 (CET)
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 30FE136; Tue, 26 Mar 2019 10:29:57 +0100 (CET)
Received: from hephaistos.amsuess.com (unknown [IPv6:2001:67c:370:128:7cd3:6870:45f3:3bdb]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id C539774; Tue, 26 Mar 2019 10:29:56 +0100 (CET)
Received: (nullmailer pid 7736 invoked by uid 1000); Tue, 26 Mar 2019 09:29:56 -0000
Date: Tue, 26 Mar 2019 10:29:56 +0100
From: Christian Amsüss <christian@amsuess.com>
To: draft-ietf-core-stateless@ietf.org
Cc: core@ietf.org
Message-ID: <20190326092954.GA3240@hephaistos.amsuess.com>
References: <155229700298.16968.3257053096174949406@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="cNdxnHkX5QqsyA0e"
Content-Disposition: inline
In-Reply-To: <155229700298.16968.3257053096174949406@ietfa.amsl.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/aP1AhHBxLwfwLRc9PF4_dPSB2jY>
Subject: Re: [core] I-D Action: draft-ietf-core-stateless-01.txt
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, 26 Mar 2019 09:30:06 -0000

Hello Klaus,

On Mon, Mar 11, 2019 at 02:36:43AM -0700, internet-drafts@ietf.org wrote:
>         Title           : Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)
>         Author          : Klaus Hartke
> 	Filename        : draft-ietf-core-stateless-01.txt

given this is listed on today's agenda with "WGLC!", I've looked through
the current version.

I'm generally happy with the text.

In section 3.3, I've had a hard time plucking out what the parts of the
message processing those MUSTs relate to, and would have it easier if
it'd either (in an informative way) briefly describe what can *not* be
done in the stateless case that could be done with a short token, or
give an example.

Thanks for your work on this
Christian

-- 
To use raw power is to make yourself infinitely vulnerable to greater powers.
  -- Bene Gesserit axiom

v2.23.0 | Report a Bug | By Email