Re: [CDNi] Ben Campbell's Discuss on draft-ietf-cdni-logging-25: (with DISCUSS and COMMENT)

Stephen Farrell <stephen.farrell@cs.tcd.ie> Wed, 18 May 2016 23:46 UTC

Return-Path: <stephen.farrell@cs.tcd.ie>
X-Original-To: cdni@ietfa.amsl.com
Delivered-To: cdni@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1364112D541; Wed, 18 May 2016 16:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.727
X-Spam-Level:
X-Spam-Status: No, score=-5.727 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cs.tcd.ie
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 B-s8xI96ypRe; Wed, 18 May 2016 16:46:20 -0700 (PDT)
Received: from mercury.scss.tcd.ie (mercury.scss.tcd.ie [134.226.56.6]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6D82812D53C; Wed, 18 May 2016 16:46:20 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by mercury.scss.tcd.ie (Postfix) with ESMTP id 1EC76BE2D; Thu, 19 May 2016 00:46:19 +0100 (IST)
X-Virus-Scanned: Debian amavisd-new at scss.tcd.ie
Received: from mercury.scss.tcd.ie ([127.0.0.1]) by localhost (mercury.scss.tcd.ie [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id nxUpGAgSkUzI; Thu, 19 May 2016 00:46:17 +0100 (IST)
Received: from [10.87.48.75] (95-45-153-252-dynamic.agg2.phb.bdt-fng.eircom.net [95.45.153.252]) by mercury.scss.tcd.ie (Postfix) with ESMTPSA id 4CE01BDF9; Thu, 19 May 2016 00:46:17 +0100 (IST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cs.tcd.ie; s=mail; t=1463615177; bh=ZlJ8RkdDWFgyU1k79yMKOltKGJ1LFAqOds6+cjjr+3c=; h=Subject:To:References:Cc:From:Date:In-Reply-To:From; b=0AACPGPI5yU2GfyUMIGl6lkkCEshqOCiUFLLgwQNLLD580Aovdi68t1z6fTBlk4fu SfBaSe8i+n8VV5TqH3D2QTTlcCeYiI5YvFRsmGHkdT0RTyf6VaDhZdsqpwwVA+2tf0 VLJe3RV4lIs1zs8dyF9XlMhb4d0P8+lCidR2cttE=
To: Ben Niven-Jenkins <ben@niven-jenkins.co.uk>, Ben Campbell <ben@nostrum.com>
References: <20160518223257.14733.37895.idtracker@ietfa.amsl.com> <3E2786B2-9204-447C-9A53-A3CB0213E0F5@niven-jenkins.co.uk>
From: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Openpgp: id=D66EA7906F0B897FB2E97D582F3C8736805F8DA2; url=
Message-ID: <573CFEC8.8010600@cs.tcd.ie>
Date: Thu, 19 May 2016 00:46:16 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <3E2786B2-9204-447C-9A53-A3CB0213E0F5@niven-jenkins.co.uk>
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha-256"; boundary="------------ms030800060400000506060204"
Archived-At: <http://mailarchive.ietf.org/arch/msg/cdni/CWTok6YDfUt6F2Czi73dGUzqLl8>
Cc: draft-ietf-cdni-logging@ietf.org, The IESG <iesg@ietf.org>, cdni@ietf.org, cdni-chairs@ietf.org
Subject: Re: [CDNi] Ben Campbell's Discuss on draft-ietf-cdni-logging-25: (with DISCUSS and COMMENT)
X-BeenThere: cdni@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "This list is to discuss issues associated with the Interconnection of Content Delivery Networks \(CDNs\)" <cdni.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/cdni>, <mailto:cdni-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/cdni/>
List-Post: <mailto:cdni@ietf.org>
List-Help: <mailto:cdni-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/cdni>, <mailto:cdni-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 18 May 2016 23:46:22 -0000


On 19/05/16 00:38, Ben Niven-Jenkins wrote:
> Hi Ben,
> 
> I’ll let the authors respond to most of your comments but I wanted to
> respond to one of them, see below.
> 
>> On 18 May 2016, at 23:32, Ben Campbell <ben@nostrum.com> wrote: 
>> ----------------------------------------------------------------------
>>
>> 
DISCUSS:
>> ----------------------------------------------------------------------
>>
>> 
- 7.3: "Making detailed CDNI logging
>> information known to the uCDN does not represent a particular
>> privacy concern because the uCDN is already exposed at request
>> redirection time to most of the information that shows up as CDNI
>> logging information (e.g., enduser IP@, URL, HTTP headers - at
>> least when HTTP redirection is used between uCDN and dCDN)."
>> 
>> I agree this is mostly true for HTTP redirection. But as you
>> mention, the assertion seems to fall down for DNS redirection,
>> where the uCDN may have considerably less information. I think some
>> different guidance for that case may be needed.
> 
> True, but…making detailed CDNI logging information known to the uCDN
> does not expose any more information to the uCDN than if the uCDN had
> chosen to perform the content delivery itself.
> 
> Typically when entity A contracts out work to entity B, entity A is
> entitled to see all records produced by entity B on entity A’s
> behalf.

I don't accept that that applies to all of the information that
could be at issue here. For example if A is in the US and B is in
the EU then things are not that simple.

S.

> 
> Ben
>