Re: [core] New Version Notification for draft-hoeglund-core-oscore-key-limits-01.txt

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 16 July 2021 14:51 UTC

Return-Path: <mcr+ietf@sandelman.ca>
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 0176D3A39F2 for <core@ietfa.amsl.com>; Fri, 16 Jul 2021 07:51:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, 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 6CeGSbQeXHOj for <core@ietfa.amsl.com>; Fri, 16 Jul 2021 07:51:34 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BBEC73A39EC for <core@ietf.org>; Fri, 16 Jul 2021 07:51:34 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 8305738A67; Fri, 16 Jul 2021 10:54:37 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id fRPUyI-B_i2t; Fri, 16 Jul 2021 10:54:33 -0400 (EDT)
Received: from sandelman.ca (obiwan.sandelman.ca [IPv6:2607:f0b0:f:2::247]) by tuna.sandelman.ca (Postfix) with ESMTP id 2F31238A5F; Fri, 16 Jul 2021 10:54:33 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id EA4BA2DD; Fri, 16 Jul 2021 10:51:27 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: =?us-ascii?Q?=3D=3Fiso-8859-1=3FQ=3FRikard=5FH=3DF6glund=3F=3D?= <rikard.hoglund=40ri.se@dmarc.ietf.org>
cc: "core\@ietf.org" <core@ietf.org>
In-Reply-To: <AM9P189MB1571439A130A663EC13540A783119@AM9P189MB1571.EURP189.PROD.OUTLOOK.COM>
References: <162610065278.15528.15134519536449122090@ietfa.amsl.com> <AM9P189MB1571439A130A663EC13540A783119@AM9P189MB1571.EURP189.PROD.OUTLOOK.COM>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 26.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature"
Date: Fri, 16 Jul 2021 10:51:27 -0400
Message-ID: <9597.1626447087@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/core/ZWVXc_AA3ousZ67XeXqfKeG8S6U>
Subject: Re: [core] New Version Notification for draft-hoeglund-core-oscore-key-limits-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: Fri, 16 Jul 2021 14:51:40 -0000

Rikard Höglund <rikard.hoglund=40ri.se@dmarc.ietf.org> wrote:
    > This document considers the CFRG draft at [1], and accordingly defines
    > how two peers using OSCORE must take limits of the used AEAD algorithm
    > into account,

Good.

    > and what steps to take in order to preserve the security
    > of their communications, e.g., performing a rekeying. Also, this
    > document specifies a lightweight method that two peers can use to
    > update their keying material and establish a new OSCORE Security
    > Context.

I'm concerned that this part will need significantly far more review, and
should be split off into a new document.
Maybe even, punt it into LAKE.

but, in the meantime, can you ask the authors of cfrg-aead-limits to review?

    > 1) The proposed key limits have been revised, mostly based on input
    > from John Mattsson as per slide 11 of [3].

    > 2) As reflected by the title change, the document scope has been
    > broadened to include also a key update method, that the two peers can
    > use to update their OSCORE Security Context.

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide