Re: [Idnet] IDN dedicated session call for case
Aydin Ulas <aydinulas@gmx.net> Wed, 02 August 2017 13:22 UTC
Return-Path: <aydinulas@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 682561320A2 for <idnet@ietfa.amsl.com>; Wed, 2 Aug 2017 06:22:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level:
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.199, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no 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 r8MMdk_pDmTn for <idnet@ietfa.amsl.com>; Wed, 2 Aug 2017 06:22:53 -0700 (PDT)
Received: from mail-wr0-x22b.google.com (mail-wr0-x22b.google.com [IPv6:2a00:1450:400c:c0c::22b]) (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 2BEB8126BF3 for <idnet@ietf.org>; Wed, 2 Aug 2017 06:22:53 -0700 (PDT)
Received: by mail-wr0-x22b.google.com with SMTP id 33so18675715wrz.4 for <idnet@ietf.org>; Wed, 02 Aug 2017 06:22:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to; bh=duI4ZLkLj3IvGDs6lwbBrolK1faVKLKmv4GgmwQ6k3k=; b=oi89GcA0UPUKwVUeqncNjI3LKHIEQyGL1laHWs4iVh2ysEaQYJDUjHBjkOcQu+X0/v ILFfv+uStF60WSCUZKKMHlaHiEb7JnJk3UZ/eV5ydOWABv+HxnovIIEZX+Huu9/I+SN0 nSpI/Q/AjK+X4bFOwKyAyA+2lV2xRJWVYdVWPItCUj/pFav+gxqL5lp/TnOxQvjucVzX aLkO4Ph578S/n5+ixpiyGvIQdDOz0dhcNtkBoC562zsab06oAjEAGmQ3Dq7y1OFB2ox+ RMCUVPHHJmEWV2hRmPS13YCuqt1NW4rjzwYDaqzpon/B705Fz4ggW3KB4p4pQUeepB7d A/6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to; bh=duI4ZLkLj3IvGDs6lwbBrolK1faVKLKmv4GgmwQ6k3k=; b=dm0KZmkj8L0CLipoYxtApjPwSi5FcJjSywVBirY3X9xjaj70I/iewddRXZ94Kb+sN3 9QxqSy/t65s16reOjdz5dP2Viv/EJrAsLe9jR9LGe7weYu/RM1VEUoWogxTr3uElXlmw MTEdj54PH6/b3sVkVpmAwe7jKMNTbC8XW7PcaOtbcIltR3Bl4hLRj/yEbAX4OhoanZDl p9LW9mGWnk6Re0URnQTciWCP5nun6JaHZIfyxgWFmHvEO6x64JYj7afDRw5Hk/FigQOO Mf7ubH191eDtm+IJxAKQ0T5MdMfRR11GVIRqTfHeDmZpefzc7gEglJ6+BbA6FP7Fiqbn 1g4g==
X-Gm-Message-State: AIVw110jnwrgACqjWlDBYPrRIo7Uw9o4rb6Uwy+m/JDrUrIpNhs8UT5b ADI7Mh+MjTZ1bpEiK8pvwXpChYIfmA==
X-Received: by 10.223.166.184 with SMTP id t53mr20532190wrc.265.1501680171270; Wed, 02 Aug 2017 06:22:51 -0700 (PDT)
MIME-Version: 1.0
Sender: aydinulas@gmail.com
Received: by 10.28.105.24 with HTTP; Wed, 2 Aug 2017 06:22:10 -0700 (PDT)
In-Reply-To: <HE1PR0701MB2203FC7F918350B07EBB65F0E8B00@HE1PR0701MB2203.eurprd07.prod.outlook.com>
References: <6AE399511121AB42A34ACEF7BF25B4D297A34A@DGGEMM505-MBS.china.huawei.com> <HE1PR0701MB2203FC7F918350B07EBB65F0E8B00@HE1PR0701MB2203.eurprd07.prod.outlook.com>
From: Aydin Ulas <aydinulas@gmx.net>
Date: Wed, 02 Aug 2017 16:22:10 +0300
X-Google-Sender-Auth: SIpmfVHF9HkgibDZgJhSYVKLvVU
Message-ID: <CA+kz0z0yysZptZaZ-6ERKbQXC+tXncOtSjEY9Y3VtTrB4YvN7g@mail.gmail.com>
To: yanshen <yanshen@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Content-Type: multipart/alternative; boundary="001a114741c82cc8dc0555c5295b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/zbndUvuz14Rdx7cvBEf0GmPz_0I>
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: Wed, 02 Aug 2017 13:22:55 -0000
Hi, Here is my suggestion. Use case N+1: Application (and/or DDoS) detection Description: Detect the application (or attack) from network packets (HTTPS or plain) Collect the history traffic data and identify a service or attack (ex: Skype, Viber, DDoS attack etc.) Process: 1. Data collection (e.g. traffic sample of application to be detected or attack dump); 2. Training Model (includes data correlation from different parts of the network); 3. Real-time data capture and input; 4. Output prediction; 5. Online or periodically updating model parameters according to changes in the application (or attack style) Data Format: Time: [Timestamp, ...] Data Packet: [Packet Header, optional: Packet Content or the first few bytes: src/dst ip, src/dst port, frame length/number, ...] Direction: IN / OUT Route : [R1, R2, ..., RN] Traffic: [T0, T1, T2, ..., TN] Message : Request: ask for the data Reply: Identification of application Notice: For notification or others Policy: Control policy Best regards, Aydin On Wed, Aug 2, 2017 at 3:35 PM, Ciavaglia, Laurent (Nokia - FR/Nozay) < laurent.ciavaglia@nokia-bell-labs.com> wrote: > Hello, > > Hint: it would be nice to contact the NMRG chairs regarding the dedicated > session you are mentioning. > Also, participants of the NMRG could/should be interested/aware and could > eventually contribute to the effort. > > Thanks, Laurent (as NMRG co-chair). > --- > > -----Original Message----- > From: IDNET [mailto:idnet-bounces@ietf.org] On Behalf Of yanshen > Sent: Wednesday, August 02, 2017 12:12 PM > To: idnet@ietf.org > Subject: [Idnet] IDN dedicated session call for case > > 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 >
- [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case Ciavaglia, Laurent (Nokia - FR/Nozay)
- Re: [Idnet] IDN dedicated session call for case Aydin Ulas
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case Pedro Martinez-Julia
- Re: [Idnet] IDN dedicated session call for case Sheng Jiang
- Re: [Idnet] IDN dedicated session call for case Albert Cabellos
- Re: [Idnet] IDN dedicated session call for case Özgü Alay
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case Jérôme François
- Re: [Idnet] IDN dedicated session call for case Jérôme François
- Re: [Idnet] IDN dedicated session call for case Diego R. Lopez
- Re: [Idnet] IDN dedicated session call for case Jérôme François
- Re: [Idnet] IDN dedicated session call for case Diego R. Lopez
- Re: [Idnet] IDN dedicated session call for case Stenio Fernandes
- Re: [Idnet] IDN dedicated session call for case Pedro Martinez-Julia
- Re: [Idnet] IDN dedicated session call for case Simone Ferlin
- Re: [Idnet] IDN dedicated session call for case Albert Cabellos
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case Yassine HADJADJ-AOUL
- Re: [Idnet] IDN dedicated session call for case Jérôme François
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case 김민석
- [Idnet] 答复: IDN dedicated session call for case dingxiaojian (A)
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] IDN dedicated session call for case Haoyu song
- Re: [Idnet] IDN dedicated session call for case dingxiaojian (A)
- Re: [Idnet] IDN dedicated session call for case 김민석
- Re: [Idnet] IDN dedicated session call for case 김민석
- Re: [Idnet] IDN dedicated session call for case Jérôme François
- [Idnet] 答复: IDN dedicated session call for case dingxiaojian (A)
- Re: [Idnet] 答复: IDN dedicated session call for ca… yanshen
- Re: [Idnet] IDN dedicated session call for case yanshen
- Re: [Idnet] 答复: IDN dedicated session call for ca… 김민석