IETF Logo Mail Archive

Re: [Secdispatch] EDHOC Summary

Michael Richardson <mcr+ietf@sandelman.ca> Fri, 29 March 2019 07:56 UTC

Return-Path: <mcr@sandelman.ca>
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 67E7A1201ED for <secdispatch@ietfa.amsl.com>; Fri, 29 Mar 2019 00:56:22 -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, 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 BUtndn-8aczt for <secdispatch@ietfa.amsl.com>; Fri, 29 Mar 2019 00:56:19 -0700 (PDT)
Received: from relay.sandelman.ca (relay.cooperix.net [IPv6:2a01:7e00::f03c:91ff:feae:de77]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A53941201AE for <secdispatch@ietf.org>; Fri, 29 Mar 2019 00:56:19 -0700 (PDT)
Received: from dooku.sandelman.ca (unknown [IPv6:2001:67c:370:128:6e88:14ff:fe34:93bc]) by relay.sandelman.ca (Postfix) with ESMTPS id BFAA91F45B; Fri, 29 Mar 2019 07:56:17 +0000 (UTC)
Received: by dooku.sandelman.ca (Postfix, from userid 179) id 9BC2D2DA0; Fri, 29 Mar 2019 08:56:19 +0100 (CET)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Alexey Melnikov <alexey.melnikov@isode.com>
cc: secdispatch@ietf.org
In-reply-to: <44712CC3-F8FC-48BD-AB5A-8108FFBC0B5F@isode.com>
References: <359EC4B99E040048A7131E0F4E113AFC01B3311A9F@marchand> <002701d4e55a$8e886db0$ab994910$@augustcellars.com> <7565.1553790307@dooku.sandelman.ca> <44712CC3-F8FC-48BD-AB5A-8108FFBC0B5F@isode.com>
Comments: In-reply-to Alexey Melnikov <alexey.melnikov@isode.com> message dated "Thu, 28 Mar 2019 18:40:14 +0100."
X-Mailer: MH-E 8.6; nmh 1.6; GNU Emacs 24.5.1
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="=-=-="; micalg="pgp-sha256"; protocol="application/pgp-signature"
Date: Fri, 29 Mar 2019 08:56:19 +0100
Message-ID: <8697.1553846179@dooku.sandelman.ca>
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/dzSAOV59_5R1d-EKnSVkssjyoTk>
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: Fri, 29 Mar 2019 07:56:23 -0000

    >>>> 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.

That's very good to hear.
I've never heard of IMAPMOVE, which means it ran short enough that I didn't
notice it :-)
How do we repeat that kind of success?

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [

v2.23.0 | Report a Bug | By Email