Re: Hum theatre

Yoav Nir <ynir@checkpoint.com> Thu, 07 November 2013 02:48 UTC

Return-Path: <ynir@checkpoint.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 1C8D511E81C7 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 18:48:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.519
X-Spam-Level:
X-Spam-Status: No, score=-10.519 tagged_above=-999 required=5 tests=[AWL=0.080, 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 Ttq1WyaIjyOc for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 18:48:32 -0800 (PST)
Received: from smtp.checkpoint.com (smtp.checkpoint.com [194.29.34.68]) by ietfa.amsl.com (Postfix) with ESMTP id C75F911E814C for <ietf@ietf.org>; Wed, 6 Nov 2013 18:48:22 -0800 (PST)
Received: from DAG-EX10.ad.checkpoint.com ([194.29.34.150]) by smtp.checkpoint.com (8.13.8/8.13.8) with ESMTP id rA72m1rk026026; Thu, 7 Nov 2013 04:48:02 +0200
X-CheckPoint: {527AFDE8-0-1B221DC2-1FFFF}
Received: from IL-EX10.ad.checkpoint.com ([169.254.2.106]) by DAG-EX10.ad.checkpoint.com ([169.254.3.213]) with mapi id 14.03.0123.003; Thu, 7 Nov 2013 04:48:01 +0200
From: Yoav Nir <ynir@checkpoint.com>
To: "<dcrocker@bbiw.net>" <dcrocker@bbiw.net>
Subject: Re: Hum theatre
Thread-Topic: Hum theatre
Thread-Index: AQHO22BmfKAqarPt50eLuUKla/2Qz5oY70SA
Date: Thu, 07 Nov 2013 02:48:01 +0000
Message-ID: <706F6432-DD2E-44EE-9CD7-57274DA1D8A3@checkpoint.com>
References: <527AF986.4090504@dcrocker.net>
In-Reply-To: <527AF986.4090504@dcrocker.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [172.31.21.18]
x-kse-antivirus-interceptor-info: scan successful
x-kse-antivirus-info: Clean
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <B9FA24D6D6303147BA3553CD551FE338@ad.checkpoint.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 02:48:38 -0000

On Nov 6, 2013, at 6:23 PM, Dave Crocker <dhc@dcrocker.net>
 wrote:

> 
> Here's what I suggest:  A single, simple, conceptual question that supplies all of the 'guidance' we can legitimately offer, at this stage:
> 
>     The IETF needs to press for careful attention to privacy
>     concerns in its work, including protection against surveillance.
> 
>          [ ]  No
>          [ ]  Yes
>          [ ]  Don't Yet Know
>          [ ]  Don't Care
> 

Worded like that?  I choose "Yes".

But this has a similar issue to the questions asked in the plenary. It's similar to the questions "do you want to eliminate crime?", "should your government have a balanced budget?", "are NATs bad?". Unless you're in the "get over it" camp on privacy, of course you're going to vote "Yes". 

When such attention comes to specific work items, we get tradeoffs against performance and against ease of deployment. Saying that HTTP/2 will only work with server authentication (as has been suggested) means that you won't be able to just turn on a switch and get the better page-load times of HTTP/2. You would need to get a certificate first, and if your site required a 3-server cluster, you would need to either add several more nodes to the cluster or buy an SSL accelerator box. That's the kind of of trade-off we have to think about when we advocate mandatory-to-use. 

Yoav