Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests

Brian E Carpenter <brian.e.carpenter@gmail.com> Fri, 31 March 2017 12:47 UTC

Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: idnet@ietfa.amsl.com
Delivered-To: idnet@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 08412129664 for <idnet@ietfa.amsl.com>; Fri, 31 Mar 2017 05:47:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
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 XkmbDx2TNcQt for <idnet@ietfa.amsl.com>; Fri, 31 Mar 2017 05:47:16 -0700 (PDT)
Received: from mail-it0-x244.google.com (mail-it0-x244.google.com [IPv6:2607:f8b0:4001:c0b::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DED68129640 for <idnet@ietf.org>; Fri, 31 Mar 2017 05:47:15 -0700 (PDT)
Received: by mail-it0-x244.google.com with SMTP id 190so1897527itm.3 for <idnet@ietf.org>; Fri, 31 Mar 2017 05:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=LaKO2AdNbK1pSYLifS38dAUwXk6JQWpceOAzUSpMf2c=; b=SzkZBOtDVTeOYmKY49+tnu6CKqlZY2tCBEXZjqrK1xU6mUZsY9Z9qApBR+hbMCMJkO UCPdOko8TUZgWp7WDRtEzwzFhojG8qoHwERwvaslaS0V34sAP3nwwQ8NvnEGOGiNPL2r zcPnTZsyl5QVCa7R8u5UM2/PKOVg6TRU6LsR9itgpXb1z51i7x8hPVC6wzVy7NMQzwr9 UHDnX9benbsch9UI+2QJhihXT9L2c1GgaVlhVWJXcjb0+wMLeaugBkQZIw0pFhJo+U1H qJ6EY1w8WPa4+wqPbyowD5Xos3M2uCp3TWHf33ar61SXCpt5tR+7Vx/PmO83C3s6Jdrb hr2w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding; bh=LaKO2AdNbK1pSYLifS38dAUwXk6JQWpceOAzUSpMf2c=; b=XbvFtpLpsGG+FawbulHFlfllr/TxJzk6rgZU8sNpsiuDodnjz9oNwfCl+freYNOX7q 5CFCFn9Efj6+/1EDT+8pfS39Fpl/pornzc3LvzHrq3exbFauj2pChNmaoY+7nkKinRdy bSzWXysd9KItFcqISwPBAJbEk7LF1buTvoRqFx9oB3fYCwruq7maKrEe9JMqvoSfO5XE x8Imj1V/JZ4i3GOcpik4R2oxgJKPtyW1oQscs9yMmnPMgxdFee+j+MgNvripvjXQlYa6 HZzZbsvnu9MeNI1fruBLZMb5AmM27GnFehPElOVodxyIjjVNFH6AW5NF21a5uDxSbhbk 2cNA==
X-Gm-Message-State: AFeK/H16hC4c8Xi/qGty9gzPBW/MqF86eIAGYQ25O0FAwqVd78NL4ACo91f6nDlP08fkTA==
X-Received: by 10.36.66.81 with SMTP id i78mr3565552itb.15.1490964435116; Fri, 31 Mar 2017 05:47:15 -0700 (PDT)
Received: from [31.133.147.88] (dhcp-9358.meeting.ietf.org. [31.133.147.88]) by smtp.gmail.com with ESMTPSA id g19sm3065762ioj.37.2017.03.31.05.47.14 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 31 Mar 2017 05:47:14 -0700 (PDT)
To: =?UTF-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>, idnet@ietf.org
References: <3B110B81B721B940871EC78F107D848CF33029@DGGEMM506-MBS.china.huawei.com> <20170331030720.GF4808@spectre> <9a761473-d188-5a1a-d31e-6ad991dfd1e5@nokia-bell-labs.com> <0e924c06-b8fb-48fa-5137-f4de120b03db@nokia-bell-labs.com> <b6b93efd-9d78-f4f7-80db-411a39a745a6@inria.fr>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <52152b22-0178-0531-c26d-bb15a5c53ec8@gmail.com>
Date: Sat, 1 Apr 2017 01:47:21 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.8.0
MIME-Version: 1.0
In-Reply-To: <b6b93efd-9d78-f4f7-80db-411a39a745a6@inria.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/6TwSfaTzlquoh2ZG8IoOo8fZ9Qg>
Subject: Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
X-BeenThere: idnet@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: "The IDNet \(Intelligence-Defined Network\) " <idnet.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/idnet>, <mailto:idnet-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/idnet/>
List-Post: <mailto:idnet@ietf.org>
List-Help: <mailto:idnet-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/idnet>, <mailto:idnet-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 31 Mar 2017 12:47:18 -0000

> 1) on anonymization: this far from being simple...

Yes, and another issue is that it may even make the data useless. I hit
that problem a few years ago when evaluating stateless hash algorithms for
use in the IPv6 flow label. The problem was that anonymization would change
the addresses in a pcap trace in such a way that some regularity in the original
data would be replaced by pseudo-random bits, which would completely falsify
the results from a statistical viewpoint. I think that in the same way, ML
results from anonymized data might be meaningless - and there is no way to
know that.

Regards
   Brian

On 31/03/2017 17:57, Jérôme François wrote:
> Hi,
> 
> Data is primordial but sharing them is very difficult (I'm not an
> operator) due to privacy but also legislative issues.
> Here are few comments:
> 1) on anonymization: this far from being simple and I do not believe
> that anybody can guarentee that nothing will be leaked out as sensitive
> data (and at the end this will the responsability of the operator who
> have shared the data).
> -> That is why sharing but not in public manner (with a NDA) is still
> the most viable solution (in my opinion)
> 
> 2) charaterizing the data we would like to access is clearly a first
> step (even if many of us like to have raw data)
> 
> 3) Another possibility is to run the algorithms you want to test on a
> remote platform without accessing the data and get back the results
> (also here there might be some safguards to avoid that program tries to
> extract sensitive data as results !)
> 
> jerome
> 
> Le 31/03/2017 à 06:15, Laurent Ciavaglia a écrit :
>> Also CAIDA has multiple measurement tools to collect data.
>> Some IETFers are specialists of these tools and report findings on
>> data collected via these tools.
>>
>> Might be something to look at.
>>
>> Also, and with this I'm finished for today, documenting the
>> characteristics of the requested data set(s) might help.
>>
>> BR, Laurent.
>>
>> On 31/03/2017 06:12, Laurent Ciavaglia wrote:
>>> Hello,
>>>
>>> A couple of suggestions:
>>>     -Why not raise this point / request in various WGs (e.g. in the
>>> OPS Area) and RGs (e.g. MAPRG, NMRG).
>>>     -Why not work with the IETF meeting NOC to collect data sets?
>>>
>>> BR, Laurent.
>>>
>>> On 31/03/2017 05:07, Pedro Martinez-Julia wrote:
>>>> Hi all,
>>>>
>>>> That's it and I insist that, if anybody in the mailing list is bound to
>>>> an operator or a similar organization that manages huge amounts of data,
>>>> just the data we need, please try to provide it. We will be able to help
>>>> you to build some anonymization solution, if needed. Thank you.
>>>>
>>>> Regards,
>>>> Pedro
>>>>
>>>
>>> -- 
>>>
>>> Laurent Ciavaglia
>>>
>>> Nokia, Bell Labs
>>>
>>>  
>>>
>>> +33 160 402 636
>>>
>>> route de Villejust - Nozay, France
>>>
>>> linkedin.com/in/laurent.ciavaglia
>>>
>>
>> -- 
>>
>> Laurent Ciavaglia
>>
>> Nokia, Bell Labs
>>
>>  
>>
>> +33 160 402 636
>>
>> route de Villejust - Nozay, France
>>
>> linkedin.com/in/laurent.ciavaglia
>>
>>
>>
>> _______________________________________________
>> IDNET mailing list
>> IDNET@ietf.org
>> https://www.ietf.org/mailman/listinfo/idnet
> 
> 
> 
> 
> _______________________________________________
> IDNET mailing list
> IDNET@ietf.org
> https://www.ietf.org/mailman/listinfo/idnet
>