[lmap] FW: Stephen Farrell's No Objection on draft-ietf-lmap-framework-12: (with COMMENT)

<philip.eardley@bt.com> Tue, 14 April 2015 14:26 UTC

Return-Path: <philip.eardley@bt.com>
X-Original-To: lmap@ietfa.amsl.com
Delivered-To: lmap@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 729431AC3B7 for <lmap@ietfa.amsl.com>; Tue, 14 Apr 2015 07:26:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level:
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 eXW0HWArShyZ for <lmap@ietfa.amsl.com>; Tue, 14 Apr 2015 07:26:33 -0700 (PDT)
Received: from smtpb1.bt.com (smtpb1.bt.com [62.7.242.137]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 72A661A0115 for <lmap@ietf.org>; Tue, 14 Apr 2015 07:26:20 -0700 (PDT)
Received: from EPDAG01C-UKBR.domain1.systemhost.net (193.113.197.204) by EVMED03-UKBR.bt.com (10.216.161.33) with Microsoft SMTP Server (TLS) id 14.3.195.1; Tue, 14 Apr 2015 15:26:15 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by EPDAG01C-UKBR.domain1.systemhost.net (193.113.197.204) with Microsoft SMTP Server (TLS) id 15.0.995.29; Tue, 14 Apr 2015 15:26:17 +0100
Received: from rew09926dag03b.domain1.systemhost.net (10.55.202.22) by rew09926dag03b.domain1.systemhost.net (10.55.202.22) with Microsoft SMTP Server (TLS) id 15.0.995.29; Tue, 14 Apr 2015 15:26:16 +0100
Received: from rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e]) by rew09926dag03b.domain1.systemhost.net ([fe80::d514:fe50:560c:401e%12]) with mapi id 15.00.0995.031; Tue, 14 Apr 2015 15:26:16 +0100
From: philip.eardley@bt.com
To: lmap@ietf.org
Thread-Topic: [lmap] Stephen Farrell's No Objection on draft-ietf-lmap-framework-12: (with COMMENT)
Thread-Index: AQHQcs1QFHQfXbYs/EqvK85lRGF6GJ1J7vsAgAKnXlA=
Date: Tue, 14 Apr 2015 14:26:15 +0000
Message-ID: <aee7dfc3e2df4775a356bc9564c8b19b@rew09926dag03b.domain1.systemhost.net>
References: <20150409135845.13211.89354.idtracker@ietfa.amsl.com> <4AF73AA205019A4C8A1DDD32C034631D01608849F7@NJFPSRVEXG0.research.att.com>
In-Reply-To: <4AF73AA205019A4C8A1DDD32C034631D01608849F7@NJFPSRVEXG0.research.att.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.55.202.233]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/lmap/xs0nuyLevx_VptCN13z4QRpnjJQ>
Subject: [lmap] FW: Stephen Farrell's No Objection on draft-ietf-lmap-framework-12: (with COMMENT)
X-BeenThere: lmap@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Large Scale Measurement of Access network Performance <lmap.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/lmap>, <mailto:lmap-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/lmap/>
List-Post: <mailto:lmap@ietf.org>
List-Help: <mailto:lmap-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/lmap>, <mailto:lmap-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Apr 2015 14:26:35 -0000

Hi,

Just wanted to highlight the IESG's assumption that LMAP protocols will describe how to meet the privacy goals, ie not just say 'read Section 8 of the framework'.
Just making sure that the protocol people are ok with this!

Privacy is mentioned in http://tools.ietf.org/html/draft-starkcarey-lmap-protocol-criteria-01 in the context of security 

---
Stephen Farrell's IESG comment:

> - general: Thanks for the significant consideration of privacy, the 
> draft has a quite good analysis. I want to check though that the plan 
> is that other lmap drafts, esp protocol drafts, will in fact describe 
> (and maybe mandate) ways to meet privacy goals, and will not simply 
> refer to section 8 of this and tell developers to go figure it out. If 
> that latter was the plan/expectation, then we'd be better off 
> discussing that now, rather than as a late surprise for the WG. I 
> assume though that the plan is rather to try make the lmap protocol 
> something that can really be used in a privacy sensitive manner and 
> that defaults to that where possible, in which case we'll not have that problem.

Al's reply:
I think it's expected that the protocol design(s) will embrace the relevant mitigations described in section 8, just as they should take-on all relevant specifications of the framework. So, the answer is yes, IMO.