Re: [Idnet] IDN dedicated session call for case

"Diego R. Lopez" <diego.r.lopez@telefonica.com> Tue, 08 August 2017 15:38 UTC

Return-Path: <diego.r.lopez@telefonica.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 52608132628 for <idnet@ietfa.amsl.com>; Tue, 8 Aug 2017 08:38:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.7
X-Spam-Level:
X-Spam-Status: No, score=-4.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 V9mTNRlxC4Ud for <idnet@ietfa.amsl.com>; Tue, 8 Aug 2017 08:38:18 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20125.outbound.protection.outlook.com [40.107.2.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7D8D6132625 for <idnet@ietf.org>; Tue, 8 Aug 2017 08:38:16 -0700 (PDT)
Received: from DB6PR0601MB2167.eurprd06.prod.outlook.com (10.168.57.26) by DB6PR0601MB2165.eurprd06.prod.outlook.com (10.168.57.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1320.16; Tue, 8 Aug 2017 15:38:14 +0000
Received: from DB6PR0601MB2167.eurprd06.prod.outlook.com ([fe80::25:7eac:7ccc:f78d]) by DB6PR0601MB2167.eurprd06.prod.outlook.com ([fe80::25:7eac:7ccc:f78d%13]) with mapi id 15.01.1304.027; Tue, 8 Aug 2017 15:38:14 +0000
From: "Diego R. Lopez" <diego.r.lopez@telefonica.com>
To: Stenio Fernandes <sflf@cin.ufpe.br>, =?utf-8?B?SsOpcsO0bWUgRnJhbsOnb2lz?= <jerome.francois@inria.fr>
CC: Albert Cabellos <albert.cabellos@gmail.com>, yanshen <yanshen@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: [Idnet] IDN dedicated session call for case
Thread-Index: AdMLcu+vuWBrdNuZQwG6l2oQPpJcKAEjy/qAABTa8AAABHMygP//3yKAgAAF84CAACZygA==
Date: Tue, 8 Aug 2017 15:38:13 +0000
Message-ID: <A6F182A1-2024-4817-BD26-90B36077615E@telefonica.com>
References: <6AE399511121AB42A34ACEF7BF25B4D297A34A@DGGEMM505-MBS.china.huawei.com> <CAGE_QeztLKUF55OjKcsxqW=MUMAX60vR+6935-n+nnKPRVX2zg@mail.gmail.com> <7e6d507a-e8bf-b334-e394-6dc08b4dc3b1@inria.fr> <051F18D1-621A-4BF7-94F6-3C2D243F39C8@telefonica.com> <02682a50-626b-bd60-bf96-14748d1783e0@inria.fr> <CAPrseCrSCh3wsa4gWnmfv8t_rVw1TW0QpvEW4UrVykrc31Antg@mail.gmail.com>
In-Reply-To: <CAPrseCrSCh3wsa4gWnmfv8t_rVw1TW0QpvEW4UrVykrc31Antg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/f.21.0.170403
authentication-results: spf=none (sender IP is ) smtp.mailfrom=diego.r.lopez@telefonica.com;
x-originating-ip: [83.49.234.105]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DB6PR0601MB2165; 6:xpssYeU3txvr93mNJKuEa7qfr6oOekqms1RjWIkinT6aNNNQ+WsMQSi82ac6wanOxDCxwIorTE9s8xK6LyhL7VMYi4XALBKRWMltRknNTTO2dszvFVxMckyQ3bf4R3iPrxWYqbI0M+fjdJie1fxOvqTrHdfHHEpuivTkv90KFEYaxUQx3bIACNxnP6hKaqYavZFFI0yeT/FP1Zz1I0EYpBHAwaTBTZn9V6gbGiU7SFaVbT1Qdjga1QHx2axgtJXTtYlls8AbdPiyITMxjAVqVHziVv8wz/zdZpdnh6dd3Me6IrZkNlPhfTUp/c8UmlsKPJ5CpZcp+AYOQg+2JVi1Kw==; 5:UPuCYaH9eyem7hA0fbaaTLvKPd3OGt2MptjiukbpDA91VA4PSOKm7gVLRn6bjHEJeejYEJKgC3LEJOfZAgjpLu2duKNILzyRU+8VqsXuukS677ohn2/sAT61ZL700BoAYtJ8NeDiv9D5Ow77H8r83w==; 24:YwokXPa77AMBFmJZJaE4M2S6DJSJZp61V5g4R4d3BE9UizNc0Jtkjg/7KyeXMER3BlzbvHKduPoDauAqv4pc51/a74XEkyZDG2ifO88zG0U=; 7:cw4XlNFwIGbLXUTgF/B6Fwtux9JcerpR2ShYpEYEPvn/urMji+WTpaxnO9DF24/2auU7d2tZI0/gMOoFqO2xoOdFrsLFK/lQBkRJ7MRzIs8Ty2bNh52IAOWGnre9BdqwR5qUK6AO/80FhDxlzRXxwbXPZehHhXUMgSGRq+z+RgGrs4lIk/+ZPXQVOh+gg8DC4/m/97KhtZ0sEKyhUxz0cEa6TjhGsgnQexoiLBIm7Is=
x-ms-office365-filtering-correlation-id: a03dcaf6-6526-4f2d-d189-08d4de737b7c
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(300000500095)(300135000095)(300000501095)(300135300095)(22001)(300000502095)(300135100095)(2017030254152)(300000503095)(300135400095)(48565401081)(2017052603031)(201703131423075)(201703031133081)(201702281549075)(300000504095)(300135200095)(300000505095)(300135600095)(300000506095)(300135500095); SRVR:DB6PR0601MB2165;
x-ms-traffictypediagnostic: DB6PR0601MB2165:
x-exchange-antispam-report-test: UriScan:(40392960112811)(209352067349851)(131327999870524)(50582790962513);
x-microsoft-antispam-prvs: <DB6PR0601MB21651DF2AB1421E5F108075CDF8A0@DB6PR0601MB2165.eurprd06.prod.outlook.com>
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(100000700101)(100105000095)(100000701101)(100105300095)(100000702101)(100105100095)(6040450)(601004)(2401047)(8121501046)(5005006)(100000703101)(100105400095)(10201501046)(93006095)(93001095)(3002001)(6055026)(6041248)(20161123555025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(20161123558100)(20161123564025)(20161123560025)(6072148)(201708071742011)(100000704101)(100105200095)(100000705101)(100105500095); SRVR:DB6PR0601MB2165; BCL:0; PCL:0; RULEID:(100000800101)(100110000095)(100000801101)(100110300095)(100000802101)(100110100095)(100000803101)(100110400095)(100000804101)(100110200095)(100000805101)(100110500095); SRVR:DB6PR0601MB2165;
x-forefront-prvs: 03932714EB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(6009001)(39410400002)(39400400002)(39850400002)(39450400003)(39860400002)(39840400002)(377454003)(25724002)(189002)(53754006)(252514010)(199003)(50944005)(40134004)(24454002)(68736007)(189998001)(3660700001)(2906002)(14454004)(106356001)(93886004)(966005)(33656002)(76176999)(105586002)(2950100002)(54356999)(229853002)(6486002)(50986999)(6506006)(101416001)(25786009)(66066001)(53546010)(2900100001)(36756003)(6436002)(4326008)(6116002)(102836003)(3846002)(8676002)(54906002)(7736002)(6512007)(6306002)(99286003)(83506001)(81166006)(81156014)(83716003)(6246003)(305945005)(5250100002)(3280700002)(53386004)(5660300001)(97736004)(478600001)(38730400002)(53936002)(86362001)(39060400002)(8936002)(82746002)(4001350100001); DIR:OUT; SFP:1102; SCL:1; SRVR:DB6PR0601MB2165; H:DB6PR0601MB2167.eurprd06.prod.outlook.com; FPR:; SPF:None; PTR:InfoNoRecords; MX:1; A:1; LANG:en;
received-spf: None (protection.outlook.com: telefonica.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <D4B31CAFCE89094182D7DE4D092A139B@eurprd06.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: telefonica.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Aug 2017 15:38:13.9059 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 9744600e-3e04-492e-baa1-25ec245c6f10
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB6PR0601MB2165
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/2lDCukFLYpWqXxv0jn77E5zV684>
Subject: Re: [Idnet] IDN dedicated session call for case
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: Tue, 08 Aug 2017 15:38:22 -0000

Hi Stenio,

Please do! Any reference would be extremely appreciated.

Be goode,

--
"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D
http://people.tid.es/diego.lopez/

e-mail: diego.r.lopez@telefonica.com
Tel:        +34 913 129 041
Mobile: +34 682 051 091
-----------------------------------

On 8/8/2017, 17:20 , "steniofernandes@gmail.com on behalf of Stenio Fernandes" <steniofernandes@gmail.com on behalf of sflf@cin.ufpe.br> wrote:

    Hi Jerome, Diego, et al,

    Those are excellent use cases. I have some published work on applied
    machine learning to computer networking problems, including flow-based
    traffic classification. I think another use case would be applying
    unsupervised learning techniques for anomaly detection. I can
    elaborate further on this.

    Stenio

    On Tue, Aug 8, 2017 at 10:59 AM, Jérôme François
    <jerome.francois@inria.fr> wrote:
    > 100% agree with you. I was far from being exhaustive as traffic features may
    > depend on types of traffic (kin of sub use cases)
    >
    > jerome
    >
    > Le 08/08/2017 à 16:56, Diego R. Lopez a écrit :
    >
    > Hi Jerome,
    >
    >
    >
    > Agreed. This is a use case we are very much interested in, and actually
    > working in it now. Just let me say we are trying to evaluate which are the
    > significant features of the flow to perform a proper classification,
    > depending on the flow nature (TLS, DTLS, QUIC, IPsec…), and that would
    > define the concrete data to be exchanged or stored.
    >
    >
    >
    > Be goode,
    >
    >
    >
    > --
    >
    > "Esta vez no fallaremos, Doctor Infierno"
    >
    >
    >
    > Dr Diego R. Lopez
    >
    > Telefonica I+D
    >
    > http://people.tid.es/diego.lopez/
    >
    >
    >
    > e-mail: diego.r.lopez@telefonica.com
    >
    > Tel:        +34 913 129 041
    >
    > Mobile: +34 682 051 091
    >
    > -----------------------------------
    >
    >
    >
    > On 8/8/2017, 16:49 , "IDNET on behalf of Jérôme François"
    > <idnet-bounces@ietf.org on behalf of jerome.francois@inria.fr> wrote:
    >
    >
    >
    > Hi all,
    >
    > Here is another use case about traffic classification.
    >
    > Use case N+3: (encrypted) traffic classification
    >
    >     Description: collect flow-level traffic metrics such as protocol
    > information but also meta metrics such as distribution of packet sizes,
    > inter-arrival times... Then use such information to label the trafic with
    > the underlying application assuming that the granularity of classification
    > may vary (type of application, exact application name, version...)
    >     Process: 1. collect packet information 2. flow reassembly (using
    > directly flow format such as IPFIX might be possible but depends on the type
    > of traffic, e.g. extracting the TLS application data is useful for encrypted
    > traffic) 3. Collect application specific information (useful when targeting
    > a single type of application) = out of network information 4. train the
    > model 5. Online or offline testing 4. Apply application level policies.
    >     Data Format:    Time : [Start, End, Unit, Number of Value, Sampling
    > Period]
    >                                 Position: [Device ID, Port ID]
    >                                 Direction: IN / OUT
    >                                 Flow level metric: packet size
    > distributions, number of packets, inter-arrival time distribution,
    >                                  (+ application specific knowledge : payload
    > parsing)
    >
    >     Message :       Request: ask for the data
    >                            Reply: Data
    >                            Notice: For notification or others
    >                            Policy: Control policy
    >
    >
    > Best regards,
    > jerome
    >
    >
    > Le 08/08/2017 à 06:52, Albert Cabellos a écrit :
    >
    > Hi all
    >
    >
    >
    > Here´s another use-case:
    >
    >
    >
    > Use case N+2: QoE
    >         Description: Collect low-level metrics (SNR, latency, jitter,
    > losses, etc) and measure QoE. Then use ML to understand what is the relation
    > between satisfactory QoE and the low-level metrics. As an example learn that
    > when delay>N then QoE is degraded, but when M<delay<N then QoE is
    > satisfactory for the customers (please note that QoE cannot be measured
    > directly over your network). This is useful to understand how the network
    > must be operated to provide satisfactory QoE.
    >         Process: 1. Low-level data collection and QoE measurement ; 2.
    > Training Model (input low-level metrics, output QoE); 3. Real-time data
    > capture and input; 4. Predict QoE; 5. Operate network to meet target QoE
    > requirement, go to 3.
    >         Data Format:    Time : [Start, End, Unit, Number of Value, Sampling
    > Period]
    >                                 Position: [Device ID, Port ID]
    >                                 Direction: IN / OUT
    >                                 Low-level metric : SNR, Delay, Jitter,
    > queue-size, etc
    >
    >
    >         Message :       Request: ask for the data
    >                                 Reply: Data
    >                                 Notice: For notification or others
    >                                 Policy: Control policy
    >
    >
    >
    > Kind regards
    >
    >
    >
    > Albert
    >
    >
    >
    > On Wed, Aug 2, 2017 at 7:12 PM, yanshen <yanshen@huawei.com> wrote:
    >
    > Dear all,
    >
    > Since we plan to organize a dedicated session in NMRG, IETF100, for applying
    > AI into network management (NM), I’d try to list some Use Cases and propose
    > a roadmap and ToC before Nov.
    >
    > These might be rough. You are welcome to refine them and propose your
    > focused use cases or ideas.
    >
    > Use case 1: Traffic Prediction
    >         Description: Collect the history traffic data and external data
    > which may influence the traffic. Predict the traffic in short/long/specific
    > term. Avoid the congestion or risk in previously.
    >         Process: 1. Data collection (e.g. traffic sample of physical/logical
    > port ); 2. Training Model; 3. Real-time data capture and input; 4.
    > Predication output; 5. Fix error and go back to 3.
    >         Data Format:    Time : [Start, End, Unit, Number of Value, Sampling
    > Period]
    >                                 Position: [Device ID, Port ID]
    >                                 Direction: IN / OUT
    >                                 Route : [R1, R2, ..., RN]  (might be useful
    > for some scenarios)
    >                                 Service : [Service ID, Priority, ...]  (Not
    > clear how to use it but seems useful)
    >                                 Traffic: [T0, T1, T2, ..., TN]
    >         Message :       Request: ask for the data
    >                                 Reply: Data
    >                                 Notice: For notification or others
    >                                 Policy: Control policy
    >
    > Use case 2: QoS Management
    >         Description: Use multiple paths to distribute the traffic flows.
    > Adjust the percentages. Avoid congestion and ensure QoS.
    >         Process: 1. Data capture (e.g. traffic sample of physical/logical
    > port ); 2. Training Model; 3. Real-time data capture and input; 4. Output
    > percentages; 5. Fix error and go back to 3.
    >         Data Format:    Time : [Timestamp, Value type (Delay/Packet
    > Loss/...), Unit, Number of Value, Sampling Period]
    >                                 Position: [Link ID, Device ID]
    >                                 Value: [V0, V1, V2, ..., VN]
    >         Message :       Request: ask for the data
    >                                 Reply: Data
    >                                 Notice: For notification or others
    >                                 Policy: Control policy
    >
    > Use case N: Waiting for your Ideas
    >
    > Also I suggest a roadmap before Nov if possible.
    >
    > ### Roadmap ###
    > Aug. : Collecting the use cases (related with NM). Rough thoughts and
    > requirements
    > Sep. : Refining the cases and abstract the common elements
    > Oct. : Deeply analysis. Especially on Data Format, control flow, or other
    > key points
    > Nov.: F2F discussions on IETF100
    > ### Roadmap End ###
    >
    > A rough ToC is listed in following. We may take it as a scope before Nov.
    > Hope that the content could become the draft of draft.
    >
    > ###Table of Content###
    > 1. Gap and Requirement Analysis
    >         1.1 Network Management requirement
    >         1.2 TBD
    > 2. Use Cases
    >         2.1 Traffic Prediction
    >         2.2 QoS Management
    >         3.3 TBD
    > 3. Data Focus
    >         3.1 Data attribute
    >         3.2 Data format
    >         3.3 TBD
    > 4. Aims
    >         4.1 Benchmarking Framework
    >         4.2 TBD
    > ###ToC End###
    >
    >
    > Yansen
    >
    > _______________________________________________
    > 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
    >
    >
    >
    >
    > ________________________________
    >
    > Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario,
    > puede contener información privilegiada o confidencial y es para uso
    > exclusivo de la persona o entidad de destino. Si no es usted. el
    > destinatario indicado, queda notificado de que la lectura, utilización,
    > divulgación y/o copia sin autorización puede estar prohibida en virtud de la
    > legislación vigente. Si ha recibido este mensaje por error, le rogamos que
    > nos lo comunique inmediatamente por esta misma vía y proceda a su
    > destrucción.
    >
    > The information contained in this transmission is privileged and
    > confidential information intended only for the use of the individual or
    > entity named above. If the reader of this message is not the intended
    > recipient, you are hereby notified that any dissemination, distribution or
    > copying of this communication is strictly prohibited. If you have received
    > this transmission in error, do not read it. Please immediately reply to the
    > sender that you have received this communication in error and then delete
    > it.
    >
    > Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário,
    > pode conter informação privilegiada ou confidencial e é para uso exclusivo
    > da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário
    > indicado, fica notificado de que a leitura, utilização, divulgação e/ou
    > cópia sem autorização pode estar proibida em virtude da legislação vigente.
    > Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique
    > imediatamente por esta mesma via e proceda a sua destruição
    >
    >
    >
    > _______________________________________________
    > IDNET mailing list
    > IDNET@ietf.org
    > https://www.ietf.org/mailman/listinfo/idnet
    >



    --
    Prof. Stenio Fernandes
    CIn/UFPE
    http://www.steniofernandes.com



________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição