Re: [Secdispatch] Materials for Virtual Interim Meeting on March-05-2019

"Martin Thomson" <mt@lowentropy.net> Mon, 04 March 2019 22:59 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 8A2011311F0 for <secdispatch@ietfa.amsl.com>; Mon, 4 Mar 2019 14:59:33 -0800 (PST)
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=I8/OCT0E; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=z1Jk5s5L
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 DxJlWucDyOpE for <secdispatch@ietfa.amsl.com>; Mon, 4 Mar 2019 14:59:30 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E971C1311EC for <secdispatch@ietf.org>; Mon, 4 Mar 2019 14:59:29 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D65AB231D6 for <secdispatch@ietf.org>; Mon, 4 Mar 2019 17:59:28 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 04 Mar 2019 17:59:28 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=message-id:in-reply-to:references:date:from:to:subject :content-type; s=fm1; bh=DFHfqfqOfw0oDVZj19z/RGbMGCTtM28Flq65n6Y x07g=; b=I8/OCT0EKopkasHRyCLHcGxEAa1QlMPv8pkZqqg6F122vaIiVW1Inwq J2kZudxlF8a4cEPpmylbasBvuBRdQknRKjiJned5wwQMAxE8GC4H9tyhbhQwuQ3+ Z8NhXGZacy6Ser7Ay1fvH05rVhc1MEpoaAwMbPzcuQxamtc4cQ7rSbcRPyMeGwSX O3E3CiiFnB9afTOKzfCok0EKBV9/dK5XJmlnLODTDWP/f5XruG8UDoHZOXvWZ53e 2/aMSlQ8vq86Zz6PZ5mteA59Y540boqSbHuWFQzPvwNL10lUJmkzikTjUfsI+3We dRN4me7PFaLYki7pL2go8vHtL26XTlQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:references:subject:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=DFHfqfqOfw0oDVZj1 9z/RGbMGCTtM28Flq65n6Yx07g=; b=z1Jk5s5LtBJm7Vh4QdAJYy4Oc8WDQqCTQ g22zk19wbIykbdMsbrglTQXsGFindPOdYjctP5U2qhNscKKuYf8/Z3WiEerR2Lev oKgRkuuFKIZHWlgtN62d25UOMmetc7RbDXDXr/dU9DFfbcBuB3/LoXyY7W/4Vnhi lAW5N4HM819gaNzvdxWKo3wHTu6W3llbDHa7SQilGXz5q1SpbZPLdhiIyRBxSYBG HCPbyUI15SmleyLEnu+rSmHvEpIWeV2YY6E7aGB4kNuS4sDOIoogSxoCty714uy0 KwbZOyi4uIzevsWzFojfEGvhHxJmaSVS3f+Ta42+MLQzAMgEHnWKA==
X-ME-Sender: <xms:0K19XNk-_2LiaU-BKJTt4HReXzof2j_a1hIhJJ1QDcwBSBTmsDXOFA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedutddrfedvgddtgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfkfgjfhffhffvufgtsehttdertd erreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigv nhhtrhhophihrdhnvghtqeenucffohhmrghinhepfigvsggvgidrtghomhdpihgvthhfrd horhhgnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhn vghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:0K19XDVg7EE-UsepKP0J-6XCUfD_-QgHvBuQJzjac84J8DLaw0t8XA> <xmx:0K19XAkyFl3KXV7R7L-LZR7TPcJdLA-olzTC3DY0613Gm_I61CB0Gw> <xmx:0K19XAQrIJ3i4dVTu2uUAzoP9D4p2jwb0xSIS9ZV_UTzuX9EEWfpDA> <xmx:0K19XCR5y_Om-JWuJ7w10IFphn67A7F0U2DzWJPtLmdJ23masxIxbw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 7885C7C1EB; Mon, 4 Mar 2019 17:59:28 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.5-925-g644bf8c-fmstable-20190228v5
X-Me-Personality: 92534000
Message-Id: <48cbf2db-883a-4828-9670-62fc00816ca9@www.fastmail.com>
In-Reply-To: <359EC4B99E040048A7131E0F4E113AFC01857DD810@marathon>
References: <359EC4B99E040048A7131E0F4E113AFC01857DD810@marathon>
Date: Mon, 04 Mar 2019 17:59:29 -0500
From: Martin Thomson <mt@lowentropy.net>
To: secdispatch@ietf.org
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/secdispatch/7G3vjVvoYyWXUB3qtqhLqd90AXs>
Subject: Re: [Secdispatch] Materials for Virtual Interim Meeting on March-05-2019
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: Mon, 04 Mar 2019 22:59:34 -0000

Hi Roman, Richard,

In reviewing the agenda for this, I realized that this might not be the ideal structure for this particular topic.

This structure is a fairly typical BoF structure for a topic that has a clear path forward, with a reasonably well-understood problem, what appears to be general agreement about how to approach the solution, and one clear candidate for a solution.  We go through that sort of process because it gives us the best chance of ending the meeting with a decision to form a working group around the proposed solution.  It effectively skips a bunch of the wrangling, which I'm sure we would all appreciate.

Going back to the usual set of questions:

1. What is the problem we are faced with?
2. Is the problem understood and narrowly scoped?
3. Do we believe it is possible to engineer a solution?
4. (stretch objective) Is this particular proposal a good basis for working on?

I don't see a whole lot of agreement about even the first question here.  The overwhelming impression you get from mail on the subject is that the primary concern here is the size of messages.  Recent mail from Hannes suggests that there might be a computation cost dimension as well.

The structure of the agenda is such that I don't feel like we'll get very far.  A lot of the time is spent in presentation (something I'm sure will keep me from falling asleep at 3am) of topics that don't directly bear on this particular problem.  In particular, the discussion of formal analysis of EDHOC is not going to help us reach any sort of consensus on the earlier questions as it relates directly to the third question.

Now, I'm sure that at least some of Goran's time will be spent addressing these important topics, I would like to see more time devoted to discussion of the hard questions and less on the "how do we get a working group chartered" end.  It seems like the agenda is specifically structured to presume an outcome on those foundational topics, and it is clear that no such presumption is safe.

Recent discussion leads me to conclude also that the final question might be contentious also, but that's probably a moot point.  I don't think that a mere 1.5 hour call will allow us to get into discussing solutions.

--Martin


On Fri, Mar 1, 2019, at 02:58, Roman Danyliw wrote:
> Hello!
> 
> As a reminder, SECDISPATCH will be meeting for a virtual interim 
> meeting on Tuesday, March 5, 2019.
> 
> ==[ Agenda ]==
> https://datatracker.ietf.org/meeting/interim-2019-secdispatch-01/materials/agenda-interim-2019-secdispatch-01-secdispatch-01.txt
> 
> ==[ Materials ]==
> https://datatracker.ietf.org/meeting/interim-2019-secdispatch-01/session/secdispatch
> 
> ==[ Dial-in Information ]==
> Meeting Link: 
> https://ietf.webex.com/ietf/j.php?MTID=m9c46ced5a864cc7a44ca4960e4fd6f0a
> 
> Meeting Number: 640 410 560
> Meeting Password: NMESeM7y 
> 
> Audio connection:
> ** 1-650-479-3208 Call-in toll number (US/Canada)
> ** Access code: 640 410 560
> 
> Regards,
> Roman and Richard
> 
> _______________________________________________
> Secdispatch mailing list
> Secdispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/secdispatch
>