IETF Logo Mail Archive

Re: [Secdispatch] EDHOC Summary

Alexey Melnikov <alexey.melnikov@isode.com> Thu, 28 March 2019 17:40 UTC

Return-Path: <alexey.melnikov@isode.com>
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 151D1120247 for <secdispatch@ietfa.amsl.com>; Thu, 28 Mar 2019 10:40:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isode.com
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 nGOPCQS3b9-3 for <secdispatch@ietfa.amsl.com>; Thu, 28 Mar 2019 10:40:25 -0700 (PDT)
Received: from waldorf.isode.com (waldorf.isode.com [62.232.206.188]) by ietfa.amsl.com (Postfix) with ESMTP id F00951202E1 for <secdispatch@ietf.org>; Thu, 28 Mar 2019 10:40:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1553794816; d=isode.com; s=june2016; i=@isode.com; bh=z07EMhdExM2yOmkm75fH5nz6K7C2aqfAefMy/Ycv3H0=; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version: In-Reply-To:References:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description; b=NjbEXjTCd54b916qOobyJi0m0KDZkhb2XDC7iODN8k2KtxTDmNg8Niya6PO8tjsHWCBv1A 4MKCc6TsQXXiWJldWthi128Sts4YAIkLlw/GfXDQueSuj6UD5QgC/uemanYX3YNRBC4CE/ zXbgctHBGzG7OzUTGsbaXPepdOEshwc=;
Received: from [10.228.207.1] ((unknown) [85.255.236.104]) by waldorf.isode.com (submission channel) via TCP with ESMTPSA id <XJ0G=wB6105e@waldorf.isode.com>; Thu, 28 Mar 2019 17:40:16 +0000
X-SMTP-Protocol-Errors: NORDNS
From: Alexey Melnikov <alexey.melnikov@isode.com>
X-Mailer: iPhone Mail (15G77)
In-Reply-To: <7565.1553790307@dooku.sandelman.ca>
Date: Thu, 28 Mar 2019 18:40:14 +0100
Cc: secdispatch@ietf.org
Message-Id: <44712CC3-F8FC-48BD-AB5A-8108FFBC0B5F@isode.com>
References: <359EC4B99E040048A7131E0F4E113AFC01B3311A9F@marchand> <002701d4e55a$8e886db0$ab994910$@augustcellars.com> <7565.1553790307@dooku.sandelman.ca>
To: Michael Richardson <mcr+ietf@sandelman.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/uXisa3L3kBPEwhF58a6zCP0wJG4>
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: Thu, 28 Mar 2019 17:40:28 -0000

Hi Michael,

On 28 Mar 2019, at 17:25, Michael Richardson <mcr+ietf@sandelman.ca> wrote:

>>> Chartering a narrowly scoped, short-lived WG in this space with EDHOC
>>> as a starting point seems to be an attractive path forward, but we
>>> would like to
>>> receive community feedback on the degree of support for this approach.
> 
> I believe that that our experience with narrowly scoped short-lived WGs has
> been poor.  I can't think of a positive, or really, any example.
> I would dearly like this to not be the case... so maybe we can do better.
> Maybe there is some RFC3999 we can try here.

This can vary by area, but we had several examples in ART, with a single document deliverable. One example is IMAPMOVE.

Best Regards,
Alexey

v2.23.0 | Report a Bug | By Email