Re: Clarifying Russ's hums

Roberto Peon <grmocg@gmail.com> Wed, 06 November 2013 22:26 UTC

Return-Path: <grmocg@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 F1F4421F9CEA for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 14:26:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
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 bybzU9xe6Awz for <ietf@ietfa.amsl.com>; Wed, 6 Nov 2013 14:26:59 -0800 (PST)
Received: from mail-oa0-x232.google.com (mail-oa0-x232.google.com [IPv6:2607:f8b0:4003:c02::232]) by ietfa.amsl.com (Postfix) with ESMTP id 17CAF21F9A40 for <ietf@ietf.org>; Wed, 6 Nov 2013 14:26:58 -0800 (PST)
Received: by mail-oa0-f50.google.com with SMTP id j17so184409oag.9 for <ietf@ietf.org>; Wed, 06 Nov 2013 14:26:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=WYUn1YIYKZZzndzgENgpILMW8a7M6FToOh8X328Yoh0=; b=zSFammXTsun237BYQh0Ky0A25ShEafe54Qv1i4oqeTlr0PSTfMwMsQsXAw7CCGnOzO CW/mnbBgrUh/+NC58z/QP/UJ/ha9Gu2llU84H75v8xllaRxYchCE1pYmZttC0Mg7wRkX GzCq4SqLpvw1XMCKm57+7Ve6sDrPIDkWb6qaTuZtu+lKm/OCmLEs9s3AvaNGiUR4JqSA 8D4ZDexZCpBN6XKpogGBhPaIfyljl7dUsJnMOXLwGdkbJ6O6LLmQiCmkBj5HhEKlSarX jSi4P8Pk0OfNp4t41UJYAuzH72Ag2YXtDcboq5OytEC9/sNLRGEjsMI5YSbQNkWUoXQB X4YQ==
MIME-Version: 1.0
X-Received: by 10.60.51.196 with SMTP id m4mr4406346oeo.1.1383776818423; Wed, 06 Nov 2013 14:26:58 -0800 (PST)
Received: by 10.76.105.114 with HTTP; Wed, 6 Nov 2013 14:26:58 -0800 (PST)
In-Reply-To: <CAP+FsNdOLOJPjCRAN-40_FbZx9yQZqFR1maeCKwnoum9+YbvqA@mail.gmail.com>
References: <CAPv4CP_UiuDTshnz-vzb7aTQEV-UrdyXiYb70iR72YQSi_3H1w@mail.gmail.com> <527AB909.4040108@gmail.com> <CAPv4CP-BjyD8DFytZtcike3tHufGJJrDEjyTbJsroANbBeqLpg@mail.gmail.com> <CAP+FsNdOLOJPjCRAN-40_FbZx9yQZqFR1maeCKwnoum9+YbvqA@mail.gmail.com>
Date: Wed, 06 Nov 2013 14:26:58 -0800
Message-ID: <CAP+FsNcPuhqb2s-rEjBvzDA9ReBWPSqWvDhYC8Rth=oeobTqZw@mail.gmail.com>
Subject: Re: Clarifying Russ's hums
From: Roberto Peon <grmocg@gmail.com>
To: Scott Brim <scott.brim@gmail.com>
Content-Type: multipart/alternative; boundary="001a11c30920b5f51904ea89a5af"
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 22:27:00 -0000

And I realize that encryption without privacy is silly, but...
-=R


On Wed, Nov 6, 2013 at 2:12 PM, Roberto Peon <grmocg@gmail.com> wrote:

> At least one of the questions (and probably two of 'em) for which we
> hummed was unclear enough that I couldn't interpret it as a policy
> statement.
>
> In particular: "The IETF should strive for e2e encryption even when there
> are middleboxes in the path":
>  - encryption with/without privacy?
>  - encryption with/without authentication?
>  - do authorized/explicit middleboxes count?
>
> This is too ambiguous for me to interpret in any meaningful way :/
> -=R
>
>
> On Wed, Nov 6, 2013 at 1:55 PM, Scott Brim <scott.brim@gmail.com> wrote:
>
>> On Wednesday, November 6, 2013, Brian E Carpenter wrote:
>>
>>> 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.
>>>
>>
>> Yes but as presented these could be taken as clear policy statements, not
>> just guiding principles. I thought embarking on clarifying them asap would
>> be a good idea.
>>
>
>