Re: Hum theatre

"Klaas Wierenga (kwiereng)" <kwiereng@cisco.com> Thu, 07 November 2013 18:29 UTC

Return-Path: <kwiereng@cisco.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74AB821E818A for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 10:29:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.599
X-Spam-Level:
X-Spam-Status: No, score=-10.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XGg+wJAaQJOD for <ietf@ietfa.amsl.com>; Thu, 7 Nov 2013 10:29:49 -0800 (PST)
Received: from rcdn-iport-7.cisco.com (rcdn-iport-7.cisco.com [173.37.86.78]) by ietfa.amsl.com (Postfix) with ESMTP id 9605E21E8147 for <ietf@ietf.org>; Thu, 7 Nov 2013 10:29:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2212; q=dns/txt; s=iport; t=1383848987; x=1385058587; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=W1tjGhx8fknkG/O+1Pq43ZBc+JuCvJZsrkvdaHD4yLQ=; b=Ov6Ne4vjUxdVGrDVcH2nLDiQWopHNOlWAh9oQwwJRmDSnmXSQHeMI49w DrFNHVMI5wpk1tqe7vR34bjsUASyBjvCZ/zfuFcP8T89WHoShV0YZ3TqH PepikK3Y7vCCrti4I7yc0tS5siJf3C8hxOJB8LzXOAxvVtRGHQDUQnWCD s=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AgYFAETbe1KtJV2d/2dsb2JhbABagwc4U78PgSUWdIIlAQEBAwF0BQULAgEIRjIlAgQOBYd7BrxkjyYzB4MggRADmAySCoMmgio
X-IronPort-AV: E=Sophos;i="4.93,653,1378857600"; d="scan'208";a="282060669"
Received: from rcdn-core-6.cisco.com ([173.37.93.157]) by rcdn-iport-7.cisco.com with ESMTP; 07 Nov 2013 18:29:47 +0000
Received: from xhc-rcd-x02.cisco.com (xhc-rcd-x02.cisco.com [173.37.183.76]) by rcdn-core-6.cisco.com (8.14.5/8.14.5) with ESMTP id rA7ITkmO027187 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Thu, 7 Nov 2013 18:29:47 GMT
Received: from xmb-aln-x12.cisco.com ([169.254.7.149]) by xhc-rcd-x02.cisco.com ([173.37.183.76]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 12:29:46 -0600
From: "Klaas Wierenga (kwiereng)" <kwiereng@cisco.com>
To: Jari Arkko <jari.arkko@piuha.net>
Subject: Re: Hum theatre
Thread-Topic: Hum theatre
Thread-Index: AQHO22Bfq6Hcjpak3E2ZMwRt/PaCR5oZdfcAgAACZoCAAElPAIAAJbYAgACHqYCAAAenAIAABcyA
Date: Thu, 7 Nov 2013 18:29:46 +0000
Message-ID: <4AC7B489-8B0D-486F-8DB9-69BA495997BE@cisco.com>
References: <527AF986.4090504@dcrocker.net> <CAHBU6iuDXQok_QRZe7BL__Vmkn447vUCSViDgrVkaedKAHcnfw@mail.gmail.com> <m2bo1w29zw.wl%randy@psg.com> <527B3F62.3030005@qti.qualcomm.com> <CAL02cgRNTCuQWXsZQOKKpMtPa09PYhFj5FncghOmORsZ8hb13A@mail.gmail.com> <527BD0D1.4000708@qti.qualcomm.com> <B0ACC5AB-F87B-4EF5-801F-27BBA7445E98@piuha.net>
In-Reply-To: <B0ACC5AB-F87B-4EF5-801F-27BBA7445E98@piuha.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.61.109.120]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <C6F273D7A0908242A18C334D3CBA2FEC@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 07 Nov 2013 18:29:55 -0000

Jari,

Well spoken

Klaas


On Nov 7, 2013, at 7:09 PM, Jari Arkko <jari.arkko@piuha.net> wrote:

> I wanted to provide my thoughts on this. 
> 
> First, in the interest of full disclosure, Russ and I conferred on stage about the questions, and he had my OK to go ahead. 
> 
> Now, of course the questions were at a high level, and with full hindsight they could have been more neutrally formulated. At the end of the day, they are what they are. And should be given the value they deserve.
> 
> I'd actually like to argue that the IETF position on this topic is something bigger, something where the plenary discussion and hums played a supporting role but they are not the sole determination. Here's my take-away from this week:
> 
> "The IETF considers pervasive-monitoring as a security issue and is willing to work to address it."
> 
> Nothing more, nothing less. Most working groups that I went to were addressing this topic in one way or the other, going through application by application, doing careful work to understand what options we have to improve security, and weighing the various trade-offs in different designs. The proof of the pudding is in the eating. "We need to address it" vs. "We are putting in the cycles to address it". When I look at the discussions throughout the week, it is very clear to me that we are putting in the cycles. 
> 
> As Carsten said:
> 
>> As always, hard work follows, and the devil is in the details.  But that doesn’t take away from the unanimity.
> 
> And indeed there are a lot of details and trade-offs to worry about. Opportunistic encryption, for instance, has been discussed at length this week and the variants and trade-offs are far from clear.
> 
> I think the next steps are what is important. And this is a long term effort. Here are some of the things we should be doing:
> 
> - work on the general guidance in this area ("consider it as an attack", "recommended ways to apply opportunistic encryption", "threat model changes", ...)
> 
> - work on the specific protocols and application areas (http, xmpp, etc)
> 
> Jari
>