Re: [perpass] perens-perpass-appropriate-response-01

Bruce Perens <bruce@perens.com> Wed, 04 December 2013 20:34 UTC

Return-Path: <bruce@perens.com>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 258A81AE12A for <perpass@ietfa.amsl.com>; Wed, 4 Dec 2013 12:34:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.177
X-Spam-Level:
X-Spam-Status: No, score=-1.177 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RP_MATCHES_RCVD=-0.001] autolearn=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 QbyrJiVqMsvX for <perpass@ietfa.amsl.com>; Wed, 4 Dec 2013 12:34:15 -0800 (PST)
Received: from alchemy.perens.com (alchemy.perens.com [206.221.219.26]) by ietfa.amsl.com (Postfix) with ESMTP id 969511AD945 for <perpass@ietf.org>; Wed, 4 Dec 2013 12:34:15 -0800 (PST)
Received: from [192.168.18.131] (mail.a10networks.com [12.207.16.167]) by alchemy.perens.com (Postfix) with ESMTPSA id AE78450008A; Wed, 4 Dec 2013 12:34:12 -0800 (PST)
Message-ID: <529F91C9.6060906@perens.com>
Date: Wed, 04 Dec 2013 12:34:17 -0800
From: Bruce Perens <bruce@perens.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20131103 Icedove/17.0.10
MIME-Version: 1.0
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
References: <E2DA1477-C86E-441E-A33D-D47A0D67AFF3@iab.org> <EF9BD1E4-6EF3-4035-AC4E-1A2D3CADE615@mnot.net> <529E8494.7000806@perens.com> <20131204111309.GB11727@nic.fr> <529F7B3B.5020901@gmail.com>
In-Reply-To: <529F7B3B.5020901@gmail.com>
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit
Cc: perpass@ietf.org, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Subject: Re: [perpass] perens-perpass-appropriate-response-01
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The perpass list is for IETF discussion of pervasive monitoring. " <perpass.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perpass>, <mailto:perpass-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/perpass/>
List-Post: <mailto:perpass@ietf.org>
List-Help: <mailto:perpass-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perpass>, <mailto:perpass-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 04 Dec 2013 20:34:16 -0000

So, we're just going to give the entire web all of the instructions, and we don't actually _care_ if they implement HTTP 2.0 or not. We're not responsible if they do.

Sort of like handing someone a weapon, and then disclaiming responsibility for what happens afterward because you had no idea he'd actually use it!

Sorry, this seems to me to be specious.

    Thanks

    Bruce

On 12/04/2013 10:58 AM, Brian E Carpenter wrote:
Whether
implementors and operators choose to implement the resulting counter-
measures is a separate question that does have political, legal or
societal aspects.

I think that Bruce's concerns apply to deployment, not to the
IETF's work.