[COSE] Fwd: Last Call: <draft-ietf-core-echo-request-tag-11.txt> (CoAP: Echo, Request-Tag, and Token Processing) to Proposed Standard
Benjamin Kaduk <kaduk@mit.edu> Mon, 23 November 2020 03:28 UTC
Return-Path: <kaduk@mit.edu>
X-Original-To: cose@ietfa.amsl.com
Delivered-To: cose@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id F1B723A126A
for <cose@ietfa.amsl.com>; Sun, 22 Nov 2020 19:28:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.019
X-Spam-Level:
X-Spam-Status: No, score=-0.019 tagged_above=-999 required=5
tests=[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 tTLq2A70y9R3 for <cose@ietfa.amsl.com>;
Sun, 22 Nov 2020 19:28:28 -0800 (PST)
Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11])
(using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 427143A1267
for <cose@ietf.org>; Sun, 22 Nov 2020 19:28:27 -0800 (PST)
Received: from kduck.mit.edu ([24.16.140.251]) (authenticated bits=56)
(User authenticated as kaduk@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.14.7/8.12.4) with ESMTP id 0AN3SLaD026563
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT)
for <cose@ietf.org>; Sun, 22 Nov 2020 22:28:25 -0500
Date: Sun, 22 Nov 2020 19:28:20 -0800
From: Benjamin Kaduk <kaduk@mit.edu>
To: cose@ietf.org
Message-ID: <20201123032820.GZ39170@kduck.mit.edu>
References: <160576598797.13448.13519029767702511285@ietfa.amsl.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <160576598797.13448.13519029767702511285@ietfa.amsl.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/cose/GBGgkVLruQ2RF3hSMAhm8g0mVy0>
Subject: [COSE] Fwd: Last Call: <draft-ietf-core-echo-request-tag-11.txt>
(CoAP: Echo, Request-Tag, and Token Processing) to Proposed Standard
X-BeenThere: cose@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: CBOR Object Signing and Encryption <cose.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cose>,
<mailto:cose-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cose/>
List-Post: <mailto:cose@ietf.org>
List-Help: <mailto:cose-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cose>,
<mailto:cose-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Nov 2020 03:28:30 -0000
The Echo Option in this draft seems like it could come in handy in some COSE scenarios. Forwarding the last-call note here since I didn't see previous mention of this draft on the WG list. -Ben On Wed, Nov 18, 2020 at 10:06:28PM -0800, The IESG wrote: > > The IESG has received a request from the Constrained RESTful Environments WG > (core) to consider the following document: - 'CoAP: Echo, Request-Tag, and > Token Processing' > <draft-ietf-core-echo-request-tag-11.txt> as Proposed Standard > > The IESG plans to make a decision in the next few weeks, and solicits final > comments on this action. Please send substantive comments to the > last-call@ietf.org mailing lists by 2020-12-02. Exceptionally, comments may > be sent to iesg@ietf.org instead. In either case, please retain the beginning > of the Subject line to allow automated sorting. > > Abstract > > > This document specifies enhancements to the Constrained Application > Protocol (CoAP) that mitigate security issues in particular use > cases. The Echo option enables a CoAP server to verify the freshness > of a request or to force a client to demonstrate reachability at its > claimed network address. The Request-Tag option allows the CoAP > server to match block-wise message fragments belonging to the same > request. This document updates RFC7252 with respect to the client > Token processing requirements, forbidding non-secure reuse of Tokens > to ensure binding of response to request when CoAP is used with a > security protocol, and with respect to amplification mitigation, > where the use of Echo is now recommended. > > > > > The file can be obtained via > https://datatracker.ietf.org/doc/draft-ietf-core-echo-request-tag/ > > > > No IPR declarations have been submitted directly on this I-D. > > > > > > _______________________________________________ > IETF-Announce mailing list > IETF-Announce@ietf.org > https://www.ietf.org/mailman/listinfo/ietf-announce
- [COSE] Fwd: Last Call: <draft-ietf-core-echo-requ… Benjamin Kaduk