Re: [Patient] Slides from the PATIENT meeting in Singapore

Paul Wouters <paul@nohats.ca> Thu, 16 November 2017 03:41 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: patient@ietfa.amsl.com
Delivered-To: patient@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5A43124BE8 for <patient@ietfa.amsl.com>; Wed, 15 Nov 2017 19:41:47 -0800 (PST)
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] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 ItAKApMoY0I1 for <patient@ietfa.amsl.com>; Wed, 15 Nov 2017 19:41:46 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 41F0B1270A7 for <patient@ietf.org>; Wed, 15 Nov 2017 19:41:46 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3ycn9N1XQ1z27F; Thu, 16 Nov 2017 04:41:44 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1510803704; bh=MxEm63QDBwI0a6e1WkPEvpJHMm8zKtc8RgreimD3g1Q=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=i3XKIDlIE5EVXeW4CBbL41fscle+FiHFMoUPz2nS9BZzce+zGJ+xHKKz4y8xbLJQE EasrpvARpaMZN0EU9+KmscGCfRmU98qoKF+ZinzKscOYNaBbLY4FB4NsSTShLuAanJ usXf+385LjiUXVQ7bz8b/nLSROqnkCY+K5d8BbwQ=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id i-vNFFndybhc; Thu, 16 Nov 2017 04:41:42 +0100 (CET)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Thu, 16 Nov 2017 04:41:41 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id EBD6E62D29; Wed, 15 Nov 2017 22:41:40 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.11.0 bofh.nohats.ca EBD6E62D29
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id D68E840D35AF; Wed, 15 Nov 2017 22:41:40 -0500 (EST)
Date: Wed, 15 Nov 2017 22:41:37 -0500
From: Paul Wouters <paul@nohats.ca>
To: Brian Witten <brian_witten@symantec.com>
cc: "patient@ietf.org" <patient@ietf.org>
In-Reply-To: <MWHPR16MB1488343E419A6EC03325F78C932E0@MWHPR16MB1488.namprd16.prod.outlook.com>
Message-ID: <alpine.LRH.2.21.1711152236080.18091@bofh.nohats.ca>
References: <MWHPR16MB148817B4DA4B82B793D44DB493510@MWHPR16MB1488.namprd16.prod.outlook.com>, <MWHPR16MB14882E7612CB8A1EEDEF73C593560@MWHPR16MB1488.namprd16.prod.outlook.com> <MWHPR16MB1488343E419A6EC03325F78C932E0@MWHPR16MB1488.namprd16.prod.outlook.com>
User-Agent: Alpine 2.21 (LRH 202 2017-01-01)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/patient/_a4yol2Sln7GLxw8z0xrfdRM9JY>
Subject: Re: [Patient] Slides from the PATIENT meeting in Singapore
X-BeenThere: patient@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Protecting against Attacks Tunneling In Encrypted Network Tunnels <patient.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/patient>, <mailto:patient-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/patient/>
List-Post: <mailto:patient@ietf.org>
List-Help: <mailto:patient-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/patient>, <mailto:patient-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Nov 2017 03:41:48 -0000

On Thu, 16 Nov 2017, Brian Witten wrote:

> I'll also very shortly post the slides to this list as promised.

A URL would be better, we can share more easilly (as the archive will
likely mangle the attachment or create a very strange link for it)

> Unless anyone objects on this list, we're working on a more detailed set of notes, Chatham house rules

You can privately do what you want, but Chatham house rules is not
compatible with the IETF Note Well, so anything on this list should
not fall under those rules (and temporarilly working under different
rules for a subset of people seems a bit odd to me). So I am confused
about the "we".

> (a) Helps each endpoint control which parties and network devices are empowered to decrypt traffic to help protect them,
> (b) Helps each endpoint see when one of those parties or devices modifies content coming from the other endpoint, such as removing attacks, and see that with a cryptographic audit trail of who changed what where when and why, such as removing attacks,
> (c) And does all of the above without breaking or weakening any of the cryptography or cryptographic protocols in any way, including not breaking or changing TLS.

I still do not see why I cannot selectively use either a SOCKS proxy or
regular proxy, over regular TLS, to the middleware box / protection
service, on a per-domain basis. That is, you have not convinced me there
is any need for a protocol change. Without a clear need, the exitsing
protocols should not be further complicated.

Paul