Re: [Secdispatch] EDHOC Summary

"Martin Thomson" <mt@lowentropy.net> Wed, 10 April 2019 02:57 UTC

Return-Path: <mt@lowentropy.net>
X-Original-To: secdispatch@ietfa.amsl.com
Delivered-To: secdispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90512120143 for <secdispatch@ietfa.amsl.com>; Tue, 9 Apr 2019 19:57:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=i30xwR+d; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CIoCrU/N
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 vd_pOOqavcqA for <secdispatch@ietfa.amsl.com>; Tue, 9 Apr 2019 19:57:22 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 456FA12009C for <secdispatch@ietf.org>; Tue, 9 Apr 2019 19:57:22 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5318E264E0; Tue, 9 Apr 2019 22:57:21 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 09 Apr 2019 22:57:21 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm1; bh=yolbJ jG0KtY+DPL6VX/WKJajt3SmHnH5HPwk2d4SX5o=; b=i30xwR+dTHv3D/+2jHbCt S+Y6w1ynsowwBFbfEbi2M3fyCbg+YvzXg4BnqLhEnrKWili9J2vEBiozTn2G7ie3 6JIWfw88ezHIRKSC+MvIv2sg5GVfs7ZguMj5pn987yNS1VQwXJ5dWgC0jQEHHCDD tuf/ySrprDE/ZFH0rb1wPBZcidHSjmm4VJvze/3h4GGKIWZYh107DE1t+kAjeJeV KyP9XftXoXsHKkKva7e9MRRdWz7uaWCz/9zXiTEHoRAn5fNaNg/rO+c3bewQocd1 lZscXXceDD7l6PtmGszK7i1S3zd1uf37Ff60K1WbxVnPnMR99EvPOx+2+M4ShIow w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=yolbJjG0KtY+DPL6VX/WKJajt3SmHnH5HPwk2d4SX 5o=; b=CIoCrU/NruanTpiPbmg7fjiEe1znNJtZeYoo4aVN4tW3grSdVyjr6Yvdt B8lbZR2zLcIYNTwU9C0WRKLyhUVF+33CMsbXSZUC9513Z2+4W9l6p/qLNaphuu1m nDKN2FK2bkV7SAXXSmA0a0EzotdlfcskivaKCSTgfafvnOdBwDswt1ZPC86TtAJ3 BblBZWXkjdGCV2DE7fVicezqqGomyAQyGz07eemUl2k9/XdYaeZtMBDF95FIN5NV WuqCrZCD2W56Mkd+XOUOJrxRGMmV6j0gqr7UOO885VeZgyQHndHCo7Bhjbbr6PdA wvW2kYDmSFBhoa2uQLGQT5SCB/CqQ==
X-ME-Sender: <xms:kFutXN0FyqeRYmjTaOefPtBexObaP4FhsJ0CXt2tEzAkWC55nejEbw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrudeigdeiiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefofgggkfgjfhffhffvufgtgfesthhqredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehivghtfhdrohhrghenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehl ohifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:kFutXLDH2QG4Y7LCcDOMdwgCFJ8GdFg9TE3qHtGJOx6GX7KJZzXtoA> <xmx:kFutXG1b1fPyQo4ONn3xF0oGgq2fy2AnXfuUJl5f0Vh_Es2wOr-Lvw> <xmx:kFutXCrTRa0vcuLg2QSWtadKWF_-tBZxJJuGN7JGjORz_aqiGEe61g> <xmx:kVutXOG62jDB3r-SbJN08v5fuoLYIPWeMj1p5WnVAzvFlToC15-xEg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C2C0F7C1B9; Tue, 9 Apr 2019 22:57:20 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.6-329-gf4aae99-fmstable-20190329v1
Mime-Version: 1.0
X-Me-Personality: 92534000
Message-Id: <8e8873a9-2352-40af-8e60-370012393ccc@www.fastmail.com>
In-Reply-To: <721B6044-8DA1-4173-BE73-87D37136DFEE@ericsson.com>
References: <359EC4B99E040048A7131E0F4E113AFC01B3311A9F@marchand> <012a4798-fc70-4b5d-b0da-373221c95d38@www.fastmail.com> <721B6044-8DA1-4173-BE73-87D37136DFEE@ericsson.com>
Date: Tue, 09 Apr 2019 22:57:22 -0400
From: Martin Thomson <mt@lowentropy.net>
To: Göran Selander <goran.selander@ericsson.com>, "secdispatch@ietf.org" <secdispatch@ietf.org>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/hVwsmDB6ys3kQb8RKeD6v-lHd5g>
Subject: Re: [Secdispatch] EDHOC Summary
X-BeenThere: secdispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Security Dispatch <secdispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/secdispatch/>
List-Post: <mailto:secdispatch@ietf.org>
List-Help: <mailto:secdispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/secdispatch>, <mailto:secdispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 10 Apr 2019 02:57:25 -0000

On Tue, Apr 9, 2019, at 21:57, Göran Selander wrote:
> [GS] There seems to be consensus on the summary provided by the 
> Security ADs, which includes the problem statement.

The entire point of my mail was to contest that point.
 
> [GS] There is no competing solution to the problem statement. As been 
> witnessed, people have waited for years for this to progress. Therefore 
> I don't see anything premature with assuming EDHOC to be a starting 
> point for the WG. 

So you would prefer to disregard the work done by Eric and Jim completely?
 
> [GS] Concrete targets with numbers have been presented, for example here:
> https://mailarchive.ietf.org/arch/msg/secdispatch/vNR7nT20fsvYjYXhAPjOpLjZGCU

Presented, yes.  Agreed, no.

> [GS] A lightweight AKE on application layer, which this specific WG is 
> proposed to work on, is actually a missing enabler for constrained 
> nodes to  "communicate among themselves and with the wider Internet". 
> Indeed, if the security protocol is too heavy or needs to terminate in 
> a gateway due to change of transport etc., then end-to-end secure 
> communication between the endpoints will not take place, thus 
> preventing "to partake in permissionless innovation".  

I think that you missed my point.  If the goal is to provide an AKE, then any AKE will do.  If the goal is to communicate with other Internet nodes, then you might argue that any AKE will do, but you at least have to consider what existing Internet nodes do in making that call.