IETF Logo Mail Archive

Re: [core] Request-Token (in draft-ietf-core-new-block-06 and draft-ietf-core-echo-request-tag-11)

Carsten Bormann <cabo@tzi.org> Wed, 20 January 2021 15:29 UTC

Return-Path: <cabo@tzi.org>
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 9FB4F3A149E for <core@ietfa.amsl.com>; Wed, 20 Jan 2021 07:29:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.919
X-Spam-Level:
X-Spam-Status: No, score=-1.919 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 Tb1sqU7RFriO for <core@ietfa.amsl.com>; Wed, 20 Jan 2021 07:29:43 -0800 (PST)
Received: from gabriel-vm-2.zfn.uni-bremen.de (gabriel-vm-2.zfn.uni-bremen.de [134.102.50.17]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 130963A14B2 for <core@ietf.org>; Wed, 20 Jan 2021 07:29:43 -0800 (PST)
Received: from [192.168.217.118] (p548dc939.dip0.t-ipconnect.de [84.141.201.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-vm-2.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4DLTwP2Vwtzyv7; Wed, 20 Jan 2021 16:29:41 +0100 (CET)
Content-Type: text/plain; charset="utf-8"
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.4\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <6C682C0B-BE8F-45A8-8020-CB8365985CAD@arm.com>
Date: Wed, 20 Jan 2021 16:29:40 +0100
Cc: "mohamed.boucadair@orange.com" <mohamed.boucadair@orange.com>, "core@ietf.org" <core@ietf.org>
X-Mao-Original-Outgoing-Id: 632849380.8343951-65f6062d3748cc01d9a5a88e0facf298
Content-Transfer-Encoding: quoted-printable
Message-Id: <2F78CEF4-5747-4B31-8A82-5328CB111A50@tzi.org>
References: <B57FD1F8-80A2-4B53-96A5-DBD1489F0692@arm.com> <32212_1611137297_60080111_32212_473_1_787AE7BB302AE849A7480A190F8B9330315BD735@OPEXCAUBMA2.corporate.adroot.infra.ftgroup> <6C682C0B-BE8F-45A8-8020-CB8365985CAD@arm.com>
To: Lauri Piikivi <Lauri.Piikivi@pelion.com>
X-Mailer: Apple Mail (2.3608.120.23.2.4)
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/de_478C28l9tGQlh1e6jBQj-I5c>
Subject: Re: [core] Request-Token (in draft-ietf-core-new-block-06 and draft-ietf-core-echo-request-tag-11)
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: Wed, 20 Jan 2021 15:29:53 -0000

On 2021-01-20, at 15:31, Lauri Piikivi <Lauri.Piikivi@pelion.com> wrote:
> 
> First of all the request-tag it is defined to overcome the weaknesses of token 

Well, the CoAP Token isn’t weak, it is solving a different problem.

A request tag is not needed if there is some other way to differentiate different block-wise interactions, but if there isn’t, it can serve as the no-op cache-key.

Grüße, Carsten

v2.23.0 | Report a Bug | By Email