Re: [perpass] Getting started...

Dave Crocker <dhc@dcrocker.net> Sat, 17 August 2013 17:32 UTC

Return-Path: <dhc@dcrocker.net>
X-Original-To: perpass@ietfa.amsl.com
Delivered-To: perpass@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0B18211E8197 for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 10:32:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.578
X-Spam-Level:
X-Spam-Status: No, score=-6.578 tagged_above=-999 required=5 tests=[AWL=0.021, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
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 gKP2VLS6UBDa for <perpass@ietfa.amsl.com>; Sat, 17 Aug 2013 10:32:49 -0700 (PDT)
Received: from sbh17.songbird.com (sbh17.songbird.com [72.52.113.17]) by ietfa.amsl.com (Postfix) with ESMTP id 0945521F99BE for <perpass@ietf.org>; Sat, 17 Aug 2013 10:32:49 -0700 (PDT)
Received: from [192.168.1.66] (76-218-9-215.lightspeed.sntcca.sbcglobal.net [76.218.9.215]) (authenticated bits=0) by sbh17.songbird.com (8.13.8/8.13.8) with ESMTP id r7HHWbQn023238 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 17 Aug 2013 10:32:41 -0700
Message-ID: <520FB3A0.1020508@dcrocker.net>
Date: Sat, 17 Aug 2013 10:32:16 -0700
From: Dave Crocker <dhc@dcrocker.net>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8
MIME-Version: 1.0
To: SM <sm@resistor.net>
References: <520E5684.1090005@cs.tcd.ie> <6.2.5.6.2.20130816171144.0c01f738@resistor.net>
In-Reply-To: <6.2.5.6.2.20130816171144.0c01f738@resistor.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.0 (sbh17.songbird.com [72.52.113.66]); Sat, 17 Aug 2013 10:32:43 -0700 (PDT)
Cc: perpass@ietf.org
Subject: Re: [perpass] Getting started...
X-BeenThere: perpass@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: dcrocker@bbiw.net
List-Id: "The perpass list is for discussion of the privacy properties of IETF protocols and concrete ways in which those could be improved. " <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: Sat, 17 Aug 2013 17:32:54 -0000

>> The only thing to add to that for now is that since the kinds of
>> monitoring we're considering can be done at many layers, we should
>> not only be considering the web, or application layer or just
>> security protocols, but the full suite of protocols and areas in
>> which the IETF works.
>
> "Privacy by default" has, up to now, been a failure in the IETF.  As you
> pointed out things do not happen unless someone volunteers to do the
> work.  There has been a lack of volunteers.  I don't know why.  I don't
> know who is trying to fix that.


We probably should draw a bright line between basic, classic 
"confidentiality" mechanisms, versus whatever we mean by "privacy". 
(The IAB was explicit in not being willing to choose a specific 
definition for its RFC on the topic -- however we might want to settle 
on one, to assist technical guidance.)

Better confidentiality mechanisms (eg, content encryption) might 
facilitate better privacy, but keeping the two constructs clearly 
distinct will probably aid both group focus and clarity about the work 
when communicating to others.

d/

-- 
Dave Crocker
Brandenburg InternetWorking
bbiw.net