Re: Clarifying Russ's hums

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 06 November 2013 21:47 UTC

Return-Path: <brian.e.carpenter@gmail.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 2D6A421E8185 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 13:47:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.541
X-Spam-Level:
X-Spam-Status: No, score=-102.541 tagged_above=-999 required=5 tests=[AWL=0.058, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 Ru8rLgHRWmV4 for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 13:47:47 -0800 (PST)
Received: from mail-ie0-x230.google.com (mail-ie0-x230.google.com [IPv6:2607:f8b0:4001:c03::230]) by ietfa.amsl.com (Postfix) with ESMTP id C7A1C11E815F for <ietf@ietf.org>; Wed, 6 Nov 2013 13:47:47 -0800 (PST)
Received: by mail-ie0-f176.google.com with SMTP id u16so204577iet.35 for <ietf@ietf.org>; Wed, 06 Nov 2013 13:47:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=RZzU8OZMmbcj38oh6f3blq1ggn8pRWLywtqCO6+CPFE=; b=JqGDCpwc68ytbLUtaEhOZk0D9MrgLP3K1isaU/l3m4/pjA2BuU8nzqXq9rWHcRey1b K0812hFWP7SRDn/WfK9VLQHXtIEM757/cWowX9IrnTT8jODFmmYgE+Db3iWkZc2BdywJ 3xDiHVTqUA58/otB2U7XCLiHwn90NFCvQ3hDvMCgpL7g/WjnTPUYvjT++E5XdrPONoi/ PANLC/wTGGmsEselMdelmZZNC7dByjtXz2hyoo7ZkTEdNJZ6Kw8GB36ybfSnd4lfMFRE 1MlOcygCI+k/E7EAhsu8bTXARHewMZtC6zo2Vis5CLIMrNLF8JXZkOhB080N6/+dwNdr k0NQ==
X-Received: by 10.43.154.18 with SMTP id lc18mr3425722icc.41.1383774467421; Wed, 06 Nov 2013 13:47:47 -0800 (PST)
Received: from [31.133.165.38] (dhcp-a526.meeting.ietf.org. [31.133.165.38]) by mx.google.com with ESMTPSA id m1sm16216389igj.10.2013.11.06.13.47.46 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 06 Nov 2013 13:47:47 -0800 (PST)
Message-ID: <527AB909.4040108@gmail.com>
Date: Thu, 07 Nov 2013 10:47:53 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Scott Brim <scott.brim@gmail.com>
Subject: Re: Clarifying Russ's hums
References: <CAPv4CP_UiuDTshnz-vzb7aTQEV-UrdyXiYb70iR72YQSi_3H1w@mail.gmail.com>
In-Reply-To: <CAPv4CP_UiuDTshnz-vzb7aTQEV-UrdyXiYb70iR72YQSi_3H1w@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: IETF discussion list <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: Wed, 06 Nov 2013 21:47:52 -0000

Hi Scott,

On 07/11/2013 10:03, Scott Brim wrote:
> In Russ's hums this morning, some had words that were not well defined.
>  Here are three that were not clear to me, and what I hummed about:
> 
> "Is the IETF willing to respond to pervasive surveillance as an attack?" ->
> "respond" is not clear.  Certainly we have to do something in response to
> what we now know. Sam is right, whatever we can imagine is probably already
> going on. However, what the response is is not agreed on.
> 
> "IETF should include encryption even outside of authentication where
> practical" -> "where practical" is not defined. I think each WG will know
> what to do with this as long as no one tries to claim that the IETF decided
> that we MUST have encryption in all cases.
> 
> "The IETF should strive for e2e encryption even when there are middleboxes
> in the path" -> "middleboxes" is a full spectrum of devices and functions.
> Some of them are quite useful. Until it's clear what the scope is, I hummed
> no.

It seems to me that all three are perfecly clear as aspirational goals,
and that they all include some room for interpretation. It's also true that
some of them may be in immediate conflict with other goals (for example,
a web proxy that is blind to the content might be rather bad at content
filtering). But all that will come out in the detailed analysis of each
issue. Guiding principles really have to skate over many details.

   Brian