Re: [Idnet] Intelligence-Defined Network Architecture and Call for Interests
Shamik Mishra <shamik.mishra@aricent.com> Tue, 28 March 2017 16:52 UTC
Return-Path: <shamik.mishra@aricent.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 32752129569 for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 09:52:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.402
X-Spam-Level:
X-Spam-Status: No, score=-0.402 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_SORBS_WEB=1.5, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=aricent.onmicrosoft.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 TBuWBwEQLy9t for <idnet@ietfa.amsl.com>; Tue, 28 Mar 2017 09:52:46 -0700 (PDT)
Received: from IND01-MA1-obe.outbound.protection.outlook.com (mail-ma1ind01on0052.outbound.protection.outlook.com [104.47.100.52]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 81A1D1294D0 for <idnet@ietf.org>; Tue, 28 Mar 2017 09:52:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aricent.onmicrosoft.com; s=selector1-Aricent-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=I2LSwFZN4x8n7eTpzgPA5wJ8Zkx3y5L81BvKXQOWuNU=; b=hepJr7mOC7+VrAIusRdbkwkOePCKZqdOLv9OukSZ/crsOk5bBptvKRlAc5Hlhx2kPGHt1k51aRrlFBk3tHhvmhM18YnXXM+sFaLN6RHUJaGuVVvSK6XLk2/Ls2N19zGJYPSDWFENXgafpd448w0sXnJ1mMZMK1Y47OyLOwQ2ni8=
Received: from MAXPR01MB0105.INDPRD01.PROD.OUTLOOK.COM (10.164.149.10) by MAXPR01MB0107.INDPRD01.PROD.OUTLOOK.COM (10.164.149.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.991.14; Tue, 28 Mar 2017 16:52:42 +0000
Received: from MAXPR01MB0105.INDPRD01.PROD.OUTLOOK.COM ([10.164.149.10]) by MAXPR01MB0105.INDPRD01.PROD.OUTLOOK.COM ([10.164.149.10]) with mapi id 15.01.0991.020; Tue, 28 Mar 2017 16:52:42 +0000
From: Shamik Mishra <shamik.mishra@aricent.com>
To: Sheng Jiang <jiangsheng@huawei.com>, "idnet@ietf.org" <idnet@ietf.org>
Thread-Topic: Intelligence-Defined Network Architecture and Call for Interests
Thread-Index: AQHSp96NotmNK6LAE0GQptHszQd4taGqd3Nw
Date: Tue, 28 Mar 2017 16:52:41 +0000
Message-ID: <MAXPR01MB01054D122B88F45AFBBD2C2EE4320@MAXPR01MB0105.INDPRD01.PROD.OUTLOOK.COM>
References: <5D36713D8A4E7348A7E10DF7437A4B927CD15A18@NKGEML515-MBS.china.huawei.com>
In-Reply-To: <5D36713D8A4E7348A7E10DF7437A4B927CD15A18@NKGEML515-MBS.china.huawei.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
authentication-results: huawei.com; dkim=none (message not signed) header.d=none;huawei.com; dmarc=none action=none header.from=aricent.com;
x-originating-ip: [122.162.224.120]
x-microsoft-exchange-diagnostics: 1; MAXPR01MB0107; 7:DOEfRgdrLEm7OmULt6px63rPQv5LUixJZ3TcbNmz4oeE+HGz3+23gRXc0xVroWsMcIIoOokm1i5lNd6vPdWIwGQ7+nJ14hw+FFQGDJjEZ5jjX9KKL8Xl2wBS4O/dVH4dQvxDcrwlJk5izGTOVFt0Gc7yLrVqSiJyM68FzFb3YZ6RjvyCREauvxVddjAcl5gH1hGgWn3rn41fgPFVxcg60y6rlChJ3h+EZpww7RLsqfUvdoioxUg6gnP7T1GTaD00L/ofPty9UKErR2Fw6nKtnomby6/U1bbjZ3I7HI0nOv3e0VEruOFSYNr3QmwPLK3JQTW7n+wMAaanmNTP4DKqKQ==
x-ms-office365-filtering-correlation-id: 7862baf1-9212-463f-700b-08d475fad9ca
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(48565401081); SRVR:MAXPR01MB0107;
x-microsoft-antispam-prvs: <MAXPR01MB0107DA74221CF7C9C1D27F40E4320@MAXPR01MB0107.INDPRD01.PROD.OUTLOOK.COM>
x-exchange-antispam-report-test: UriScan:(50582790962513);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040375)(2401047)(8121501046)(5005006)(3002001)(10201501046)(6055026)(6041248)(20161123562025)(20161123564025)(20161123560025)(20161123558025)(20161123555025)(6072148); SRVR:MAXPR01MB0107; BCL:0; PCL:0; RULEID:; SRVR:MAXPR01MB0107;
x-forefront-prvs: 0260457E99
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39850400002)(39410400002)(39860400002)(39840400002)(39450400003)(377454003)(69234005)(13464003)(38564003)(6506006)(7736002)(38730400002)(2501003)(66066001)(6246003)(74316002)(305945005)(50986999)(86362001)(76176999)(77096006)(54356999)(6436002)(53936002)(2900100001)(122556002)(7696004)(3280700002)(189998001)(3660700001)(2906002)(25786009)(53546009)(3846002)(102836003)(6116002)(55016002)(229853002)(33656002)(9686003)(6306002)(8936002)(5660300001)(2950100002)(81166006)(8676002); DIR:OUT; SFP:1101; SCL:1; SRVR:MAXPR01MB0107; H:MAXPR01MB0105.INDPRD01.PROD.OUTLOOK.COM; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: Aricent.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 28 Mar 2017 16:52:41.9847 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: dbb4cbbe-57c5-469d-b342-a9814e1d2382
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MAXPR01MB0107
Archived-At: <https://mailarchive.ietf.org/arch/msg/idnet/809Y47pxMYCBJhX0GuLD88j359A>
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: Tue, 28 Mar 2017 16:52:48 -0000
Hi Sheng, Is it possible to participate in this meeting remotely? Regards Shamik -----Original Message----- From: IDNET [mailto:idnet-bounces@ietf.org] On Behalf Of Sheng Jiang Sent: Tuesday, March 28, 2017 10:00 PM To: idnet@ietf.org Subject: [Idnet] Intelligence-Defined Network Architecture and Call for Interests Hi, all, Although there are many understanding for Intelligence-Defined Network, we are actually using this IDN as a term reference to the SDN-beyond architecture that we presented in IETF97, see the below link. A reference model is presented in page 3, while potential standardization works is presented in page 9. https://www.ietf.org/proceedings/97/slides/slides-97-nmlrg-intelligence-defined-network-01.pdf Although it might be a little bit too early for AI/ML in network giving the recent story of the concluded proposed NMLRG, we still would like to call for interests in IDN. Anybody (on site in Chicago this week) are interested in this or even wider topics regarding to AI/ML in network, please contact me on jiangsheng@huawei.com . Then we may have an informal meeting to discuss some common interests and potential future activities (not any activities in IETF, but also other STO or experimental trails, etc.) on Thursday morning. FYI, we have already working on a Work Item, called IDN in the ETSI NGP (Next Generation Protocol) ISG, links below. https://portal.etsi.org/tb.aspx?tbid=844&SubTB=844 https://portal.etsi.org/webapp/WorkProgram/Report_WorkItem.asp?WKI_ID=51011 Meanwhile, please do use this mail list as a forum to discuss any topics that may applying AI/ML into network area. Best regards, Sheng _______________________________________________ IDNET mailing list IDNET@ietf.org https://www.ietf.org/mailman/listinfo/idnet "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- [Idnet] Intelligence-Defined Network Architecture… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Shamik Mishra
- Re: [Idnet] Intelligence-Defined Network Architec… Oscar Mauricio Caicedo Rendon
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Brian Njenga
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- [Idnet] 答复: Intelligence-Defined Network Architec… dingxiaojian (A)
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Alex Galis
- Re: [Idnet] Intelligence-Defined Network Architec… Chris Hammerschmidt
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… 김민석
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… YuLing Chen (yulingch)
- Re: [Idnet] Intelligence-Defined Network Architec… Michele Zorzi
- Re: [Idnet] Intelligence-Defined Network Architec… Manav Bhatia
- Re: [Idnet] Intelligence-Defined Network Architec… Sheng Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… Wei Jiang
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Aydin Ulas
- Re: [Idnet] Intelligence-Defined Network Architec… dingxiaojian (A)
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… Laurent Ciavaglia
- Re: [Idnet] Intelligence-Defined Network Architec… Laurent Ciavaglia
- Re: [Idnet] Intelligence-Defined Network Architec… Jérôme François
- Re: [Idnet] Intelligence-Defined Network Architec… Lori Jakab
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Brian E Carpenter
- Re: [Idnet] Intelligence-Defined Network Architec… Oscar Mauricio Caicedo Rendon
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia
- Re: [Idnet] Intelligence-Defined Network Architec… David Meyer
- Re: [Idnet] Intelligence-Defined Network Architec… Juraj Giertl
- Re: [Idnet] Intelligence-Defined Network Architec… Pedro Martinez-Julia