Re: [CDNi] Alexey Melnikov's No Objection on draft-ietf-cdni-logging-26: (with COMMENT)

[Francois Le Faucheur <[e-mail]>]

Hi Alexey,

> On 1 Jun 2016, at 20:47, Alexey Melnikov <[e-mail]> wrote:
> 
> Hi Francois,
> 
> On 1 Jun 2016, at 17:17, Francois Le Faucheur <[e-mail]> wrote:
> 
>>> In 7.1, last sentence: TLS only provides for protection from tampering
>>> when in transit, not when a log file being stored.
>> 
>> I already responded to that point and corrected the sentence so it now reads:
>> “
>> Protection against third party tampering, when the CDNI Logging File is communicated over the CDN Logging Interface, can be achieved as discussed above through the use of TLS.
>> “
>> 
>> Is it not acceptable ?
> 
> Sorry, missed that. Yes, this is an improvement.
> 
> Can anything be said about data at rest?

The document already has a specific statement wrt data at rest regarding privacy protection :

“
The algorithmic mapping and variation over time MAY allow the uCDN … to reconstruct the actual client IPv4 or IPv6 address and/or other network-level identifying information when required … .  However, these enduser addresses SHOULD only be reconstructed on-demand and the CDNI Logging File SHOULD only be stored with the anonymised c-groupid value.
"

The paragraph we were discussing, in the context of your COMMENT, relates to integrity protection. We clarified that the statement about integrity protection applies when the data is in flight. When the data is at rest, I don’t think we need to discuss integrity protection since the data exchanged via CDNI LI interface can be processed by the uCDN as it sees fit (e.g. aggregate CDNI Logging Files with its own local logging records, e.g. filter/sanitise/summarize in order to export to the Content Service Provider, etc.) so it is legitimate that the uCDN can modify the data, once properly communicated via the CDNI LI interface.

So to me, we are already covered.

Cheers

Francois