Re: [Nmlrg] Uses case for ML -- automating traffic prioritisation
"Liubing (Leo)" <leo.liubing@huawei.com> Fri, 30 October 2015 02:51 UTC
Return-Path: <leo.liubing@huawei.com>
X-Original-To: nmlrg@ietfa.amsl.com
Delivered-To: nmlrg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 525F61B3518
for <nmlrg@ietfa.amsl.com>; Thu, 29 Oct 2015 19:51:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001,
T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 0PQQgWylrXgF for <nmlrg@ietfa.amsl.com>;
Thu, 29 Oct 2015 19:50:59 -0700 (PDT)
Received: from szxga01-in.huawei.com (szxga01-in.huawei.com [58.251.152.64])
(using TLSv1 with cipher RC4-SHA (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 7B0461B350C
for <nmlrg@irtf.org>; Thu, 29 Oct 2015 19:50:58 -0700 (PDT)
Received: from 172.24.1.51 (EHLO nkgeml404-hub.china.huawei.com)
([172.24.1.51])
by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued)
with ESMTP id CYD06064; Fri, 30 Oct 2015 10:50:54 +0800 (CST)
Received: from NKGEML506-MBX.china.huawei.com ([169.254.3.20]) by
nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0235.001;
Fri, 30 Oct 2015 10:50:50 +0800
From: "Liubing (Leo)" <leo.liubing@huawei.com>
To: grenville armitage <garmitage@swin.edu.au>
Thread-Topic: [Nmlrg] Uses case for ML -- automating traffic prioritisation
Thread-Index: AQHREiX2ojGPNNrU90aB7VwCeUO0hJ6DUPPA
Date: Fri, 30 Oct 2015 02:50:49 +0000
Message-ID: <8AE0F17B87264D4CAC7DE0AA6C406F45C23180F9@nkgeml506-mbx.china.huawei.com>
References: <5631DBFA.1090404@swin.edu.au>
In-Reply-To: <5631DBFA.1090404@swin.edu.au>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.111.98.117]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <http://mailarchive.ietf.org/arch/msg/nmlrg/rvR7MidG457BLwTcCH-tUGBV5ys>
Cc: "nmlrg@irtf.org" <nmlrg@irtf.org>
Subject: Re: [Nmlrg] Uses case for ML -- automating traffic prioritisation
X-BeenThere: nmlrg@irtf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Network Machine Learning Research Group <nmlrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nmlrg/>
List-Post: <mailto:nmlrg@irtf.org>
List-Help: <mailto:nmlrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nmlrg>,
<mailto:nmlrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2015 02:51:01 -0000
Hi Grenville, Thanks for sharing your use case. I think it is a valuable use case in networking. You mentioned the PoC: > A proof-of-concept implemented in OpenWRT: > http://caia.swin.edu.au/urp/diffuse/openwrt/ Does it imply that your study was specific to home networks scenarios, and the algorithms were specifically designed to adapt those low performance embedded devices? I personally expect your study was not limited in home network scenarios, because the flow classification is also an important use case in carrier networks. Best regards, Bing
- [Nmlrg] Uses case for ML -- automating traffic pr… grenville armitage
- Re: [Nmlrg] Uses case for ML -- automating traffi… Sheng Jiang
- Re: [Nmlrg] Uses case for ML -- automating traffi… grenville armitage
- Re: [Nmlrg] Uses case for ML -- automating traffi… Sheng Jiang
- Re: [Nmlrg] Uses case for ML -- automating traffi… Liubing (Leo)