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

Lori Jakab <lojakab@cisco.com> Fri, 31 March 2017 08:12 UTC

Return-Path: <lojakab@cisco.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 ED247129504 for <idnet@ietfa.amsl.com>; Fri, 31 Mar 2017 01:12:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 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_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.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 L_AtszgSUED1 for <idnet@ietfa.amsl.com>; Fri, 31 Mar 2017 01:12:42 -0700 (PDT)
Received: from aer-iport-4.cisco.com (aer-iport-4.cisco.com [173.38.203.54]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5544B129536 for <idnet@ietf.org>; Fri, 31 Mar 2017 01:12:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3268; q=dns/txt; s=iport; t=1490947962; x=1492157562; h=subject:to:references:from:message-id:date:mime-version: in-reply-to:content-transfer-encoding; bh=opdoCGIl2MLikHrZcAlb/p9sLlBprcnioRL0+qU2B0Y=; b=mRMPADvb5zbiDGBXRFr5SHtle3FT90ybtn+8pbcjdI9IKY9x83YOJZCs GHB/zdA9tkLGIrgxxsOlvTpaLNHaNYxSLhaDwSm/l4Gi+wtjP5knupvB+ uRy/hSaKOHHpu583W16C+bRW24EuJVmIsa50PsucGMj6G3NOjyNDeIL8R 0=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AGAQDrDt5Y/xbLJq1dGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1RhgQuNdHOQY5VQgg4fC4JCgzYChAEYAQIBAQEBAQEBayiFFQE?= =?us-ascii?q?BAQECAQEBChEKCwE7GwsSBi4nIg4GARIbiWkIDq8NOopcAQEBAQEBAQMBAQEBA?= =?us-ascii?q?QEBAQEBHoZOggWCaoQchh0BBJBijAiGfYtTgXxUhFaKEZNtHziBBSUWCBgVQYZ?= =?us-ascii?q?cPTWHYYIuAQEB?=
X-IronPort-AV: E=Sophos;i="5.36,251,1486425600"; d="scan'208";a="653651693"
Received: from aer-iport-nat.cisco.com (HELO aer-core-1.cisco.com) ([173.38.203.22]) by aer-iport-4.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Mar 2017 08:12:40 +0000
Received: from lojakab-mac.cisco.com (dhcp-10-61-100-82.cisco.com [10.61.100.82]) by aer-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v2V8Cdfx003429; Fri, 31 Mar 2017 08:12:39 GMT
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: Lori Jakab <lojakab@cisco.com>
Organization: cisco Systems, Inc.
Message-ID: <4cbf93ce-24a1-9f70-28e0-bf15f35b7e5b@cisco.com>
Date: Fri, 31 Mar 2017 11:12:39 +0300
MIME-Version: 1.0
In-Reply-To: <b6b93efd-9d78-f4f7-80db-411a39a745a6@inria.fr>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/7Qcq2bFPsu9aYXxX76iiSFd98_s>
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 08:12:45 -0000

On 3/31/17 7:57 AM, 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 !)

I think 3) is probably the most viable way forward for now. Lack of
public data sets is not a new challenge for networking research, and I
doubt saying that we're going to use traffic traces for ML applications
is going to change that. Creating an open source platform, either pure
software or software + hardware (like RIPE Atlas probes) that runs the
algorithms on the data sending back only the results may have a better
chance of success.

-Lori

>
> 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