IETF Logo Mail Archive

Re: [core] WG Last Call on draft-ietf-core-new-block

"Christian M. Amsüss" <christian@amsuess.com> Thu, 18 February 2021 16:43 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 36F203A136C; Thu, 18 Feb 2021 08:43:54 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 ikpC00kFSe0Z; Thu, 18 Feb 2021 08:43:52 -0800 (PST)
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 466793A142D; Thu, 18 Feb 2021 08:43:49 -0800 (PST)
Received: from poseidon-mailhub.amsuess.com (unknown [IPv6:2a02:b18:c13b:8010:a800:ff:fede:b1bd]) by prometheus.amsuess.com (Postfix) with ESMTPS id DCDED40887; Thu, 18 Feb 2021 17:43:47 +0100 (CET)
Received: from poseidon-mailbox.amsuess.com (hermes.amsuess.com [10.13.13.254]) by poseidon-mailhub.amsuess.com (Postfix) with ESMTP id DF2EAFD; Thu, 18 Feb 2021 17:43:46 +0100 (CET)
Received: from hephaistos.amsuess.com (hephaistos.amsuess.com [IPv6:2a02:b18:c13b:8010::aa6]) by poseidon-mailbox.amsuess.com (Postfix) with ESMTPSA id 9DB99190; Thu, 18 Feb 2021 17:43:46 +0100 (CET)
Received: (nullmailer pid 839522 invoked by uid 1000); Thu, 18 Feb 2021 16:43:46 -0000
Date: Thu, 18 Feb 2021 17:43:46 +0100
From: "Christian M. Amsüss" <christian@amsuess.com>
To: supjps-ietf@jpshallow.com
Cc: draft-ietf-core-new-block@ietf.org, dots@ietf.org, core@ietf.org
Message-ID: <YC6ZQktwMjVZcaZc@hephaistos.amsuess.com>
References: <022401d6e440$06763ba0$1362b2e0$@jpshallow.com> <YCxikyadpukaiK5I@hephaistos.amsuess.com> <004601d705f8$acbec250$063c46f0$@jpshallow.com> <YC5sPGW0TD/PybvD@hephaistos.amsuess.com> <00f901d70614$5ab51b50$101f51f0$@jpshallow.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="aDaF68xRb12J6Va2"
Content-Disposition: inline
In-Reply-To: <00f901d70614$5ab51b50$101f51f0$@jpshallow.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/IQgIr2_9B6ZeDdybzCpyrHCg68w>
Subject: Re: [core] WG Last Call on draft-ietf-core-new-block
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: Thu, 18 Feb 2021 16:43:54 -0000

Hello Jon,

On Thu, Feb 18, 2021 at 04:37:32PM -0000, supjps-ietf@jpshallow.com wrote:
> I guess that we need an expert understanding of what to do here.
> - Maybe leave out the CDDL definition and give an example?

the CDDL definition is fine and following the state-of-the-art
workaround.

But what it means is that the array wrapping is only there on paper to
make the CDDL happy. And as the array header does not hit the wire (and
is not generally constructed in memory either), the implementation note
is moot.

BR
c

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

v2.23.0 | Report a Bug | By Email