IETF Logo Mail Archive

Re: [Secdispatch] EDHOC Summary

Jim Schaad <ietf@augustcellars.com> Thu, 28 March 2019 20:27 UTC

Return-Path: <ietf@augustcellars.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 A5CC612004F for <secdispatch@ietfa.amsl.com>; Thu, 28 Mar 2019 13:27:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, 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 5dFu6EesB67K for <secdispatch@ietfa.amsl.com>; Thu, 28 Mar 2019 13:27:50 -0700 (PDT)
Received: from mail2.augustcellars.com (augustcellars.com [50.45.239.150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 96691120005 for <secdispatch@ietf.org>; Thu, 28 Mar 2019 13:27:49 -0700 (PDT)
Received: from Jude (31.133.152.241) by mail2.augustcellars.com (192.168.0.56) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Thu, 28 Mar 2019 13:27:43 -0700
From: Jim Schaad <ietf@augustcellars.com>
To: 'Michael Richardson' <mcr+ietf@sandelman.ca>, secdispatch@ietf.org
References: <359EC4B99E040048A7131E0F4E113AFC01B3311A9F@marchand> <002701d4e55a$8e886db0$ab994910$@augustcellars.com> <7565.1553790307@dooku.sandelman.ca>
In-Reply-To: <7565.1553790307@dooku.sandelman.ca>
Date: Thu, 28 Mar 2019 21:27:40 +0100
Message-ID: <009f01d4e5a4$b267c790$173756b0$@augustcellars.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Outlook 16.0
Thread-Index: AQKfGLPmwj7uBgha/YkI9i6FfschWgIS2kHdAbQosOekbt/HgA==
Content-Language: en-us
X-Originating-IP: [31.133.152.241]
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/d9hm6cKqReHIucbXGAbqTTwAWyY>
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 20:27:52 -0000


> -----Original Message-----
> From: Secdispatch <secdispatch-bounces@ietf.org> On Behalf Of Michael
> Richardson
> Sent: Thursday, March 28, 2019 5:25 PM
> To: secdispatch@ietf.org
> Subject: Re: [Secdispatch] EDHOC Summary
> 
> 
> Jim Schaad <ietf@augustcellars.com> wrote:
>     > I am strongly in agreement with doing this.
> 
> ....
>     >> 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.

I managed to get the first round of COSE done in 15 months

Jim

> 
> I would propose (and will volunteer, unless you'd rather do this to
yourself
> Roman) to ask some past IESG chairs (Russ, Jari) about when we have done
> this in the past, and then find out from relevant (past?) ADs if there are
> lessons to be learned.
> 
> --
> Michael Richardson <mcr+IETF@sandelman.ca>, Sandelman Software Works
> -= IPv6 IoT consulting =-
> 
>

v2.23.0 | Report a Bug | By Email