From nobody Mon Apr 4 11:31:08 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B796B12D14E for ; Mon, 4 Apr 2016 11:30:53 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.619 X-Spam-Level: X-Spam-Status: No, score=-2.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-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 YZhe0T9l_5os for ; Mon, 4 Apr 2016 11:30:49 -0700 (PDT) Received: from COL004-OMC2S15.hotmail.com (col004-omc2s15.hotmail.com [65.55.34.89]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 128A012D61F for ; Mon, 4 Apr 2016 11:30:49 -0700 (PDT) Received: from APC01-HK2-obe.outbound.protection.outlook.com ([65.55.34.71]) by COL004-OMC2S15.hotmail.com over TLS secured channel with Microsoft SMTPSVC(7.5.7601.23008); Mon, 4 Apr 2016 11:30:48 -0700 Received: from PU1APC01FT055.eop-APC01.prod.protection.outlook.com (10.152.252.58) by PU1APC01HT086.eop-APC01.prod.protection.outlook.com (10.152.253.131) with Microsoft SMTP Server (TLS) id 15.1.443.6; Mon, 4 Apr 2016 18:30:46 +0000 Received: from SG2PR02MB1101.apcprd02.prod.outlook.com (10.152.252.60) by PU1APC01FT055.mail.protection.outlook.com (10.152.253.106) with Microsoft SMTP Server (TLS) id 15.1.443.6 via Frontend Transport; Mon, 4 Apr 2016 18:30:45 +0000 Received: from SG2PR02MB1101.apcprd02.prod.outlook.com ([10.169.53.11]) by SG2PR02MB1101.apcprd02.prod.outlook.com ([10.169.53.11]) with mapi id 15.01.0447.027; Mon, 4 Apr 2016 18:30:44 +0000 From: =?gb2312?B?ucsgyNY=?= To: "sdn@irtf.org" Thread-Topic: Seeking for comments and suggestions about two drafts related with the SDN/NFV co-deployment in cloud datacenters presented in the morning. I summerized my ideas in the mail. Hope it's better for understanding. Thread-Index: AQHRjqAXAzmHsvTcck6gUhVW86xL4A== Date: Mon, 4 Apr 2016 18:30:44 +0000 Message-ID: Accept-Language: zh-CN, en-US Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=softfail (sender IP is 25.152.252.60) smtp.mailfrom=outlook.com; irtf.org; dkim=none (message not signed) header.d=none;irtf.org; dmarc=fail action=none header.from=outlook.com; received-spf: SoftFail (protection.outlook.com: domain of transitioning outlook.com discourages use of 25.152.252.60 as permitted sender) x-tmn: [IcNSgva0sdslRLtXttE+JE7mnwdbBWf/] x-eopattributedmessage: 0 x-forefront-antispam-report: CIP:25.152.252.60; IPV:NLI; CTRY:GB; EFV:NLI; SFV:NSPM; SFS:(10019020)(98900003); DIR:OUT; SFP:1102; SCL:1; SRVR:PU1APC01HT086; H:SG2PR02MB1101.apcprd02.prod.outlook.com; FPR:; SPF:SoftFail; MLV:ovrnspm; MX:1; A:1; LANG:en; x-ms-office365-filtering-correlation-id: 56cfe077-0f9c-4dcd-16a9-08d35cb73bf1 x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(5061506196)(5061507196); SRVR:PU1APC01HT086; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(432015012)(82015046); SRVR:PU1APC01HT086; BCL:0; PCL:0; RULEID:; SRVR:PU1APC01HT086; x-forefront-prvs: 0902222726 Content-Type: multipart/alternative; boundary="_000_SG2PR02MB1101E72883AD9D46C9705C968B9D0SG2PR02MB1101apcp_" MIME-Version: 1.0 X-OriginatorOrg: outlook.com X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2016 18:30:44.3016 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Internet X-MS-Exchange-CrossTenant-id: 84df9e7f-e9f6-40af-b435-aaaaaaaaaaaa X-MS-Exchange-Transport-CrossTenantHeadersStamped: PU1APC01HT086 X-OriginalArrivalTime: 04 Apr 2016 18:30:48.0309 (UTC) FILETIME=[1BD1A250:01D18EA0] Archived-At: Subject: [Sdn] Seeking for comments and suggestions about two drafts related with the SDN/NFV co-deployment in cloud datacenters presented in the morning. I summerized my ideas in the mail. Hope it's better for understanding. X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Apr 2016 18:30:54 -0000 --_000_SG2PR02MB1101E72883AD9D46C9705C968B9D0SG2PR02MB1101apcp_ Content-Type: text/plain; charset="gb2312" Content-Transfer-Encoding: base64 SGksIGRlYXIgYWxsLg0KDQpJIGhhdmUgbWFkZSB0aGUgcHJlc2VudGF0aW9uIGluIGEgcnVzaCB0 aGlzIG1vcm5pbmcuIFNvIEkgYWNjZXB0IHRoZSBhZHZpY2UgZnJvbSBjaGFpcnMgdG8gZXhwcmVz cyBteSBpZGVhcyBpbiB0aGUgbWFpbC1saXN0LiBIb3BlIHRoYXQgaXQncyBiZXR0ZXIgZm9yIHVu ZGVyc3RhbmRpbmcuDQoNCkFzIHRoZXJlIGFyZSB0d28gZHJhZnRzIHJlbGF0ZWQgaW4gbXkgcHJl c2VudGF0aW9ucy4gSXQgd2lsbCBiZSBncmF0ZWZ1bCBvZiB5b3UgdG8gZ28gdGhyb3VnaCB0aGUg ZHJhZnQgYW5kIGNvbW1lbnRzIG9uIHRoYXQuDQoNCg0KT25lIGlzIHRoZSB1cGRhdGVkIHZlcnNp b24gb2YgdGhlIGRyYWZ0IG9mIHByb2JsZW0gc3RhdGVtZW50IG9mIFNETiBhbmQgTkZWIGNvLWRl cGxveW1lbnQgaW4gY2xvdWQgZGF0YWNlbnRlcnMuDQoNCmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0 Zi5vcmcvZG9jL2RyYWZ0LWd1LXNkbnJnLXByb2JsZW0tc3RhdGVtZW50LW9mLXNkbi1uZnYtaW4t ZGMvDQoNClRoZSB1cGRhdGVkIGNvbnRleHRzIGFyZToNCg0KKDEpIE5ldHdvcmsgYXJjaGl0ZWN0 dXJlIGNoYW5nZXMgd2hlbiB0aGUgYmFyZS1tZXRhbCBzZXJ2ZXJzIGFyZSBicm91Z2h0IGluLiBT RE4gVG9SIGFuZCB0aGUgb3BlbnN0YWNrIG1vZHVsZXMgc3VjaCBhcyBpcm9uaWMgYW5kIG5ldXRy b24gc2hvdWxkIGJlIGJyb3VnaHQgaW4gb3IgYmUgcGFydGljYWxseSBpbmZsdWVuY2VkLg0KDQpB cyBpbiB0aGUgYmFyZS1tZXRhbCBzZXJ2ZXIgc2NlbmFyaW8sIFNETiBUT1Igc2hvdWxkIGJlIGFj dGVkIGFzIHRoZSB2dGVwLiBBbmQgdGhlIG9wZW5zdGFjayBpcm9uaWMgbW9kdWxlIGFyZSB1c2Vk IHRvIHBvd2VyIHRoZSBzZXJ2ZXIgYW5kIGluc3RhbGwgdGhlIG9wZXJhdGluZyBzeXN0ZW1zLg0K DQooMikgSHlwZXJ2aXNvcjoNCg0KV2hlbiBvdGhlciBoeXBlcnZpc29ycyByYXRoZXIgdGhhbiBL Vk0gaXMgYWNjZXB0ZWQsIHNvbWV0aGluZyBzaG91bGQgYmUgbm90ZWQgaXMgdGhhdCB0aGUgdmly dHVhbCBzd2l0Y2ggYm9uZGluZyB3aXRoIHRoZSBoeXBlcnZpc29yIG1heSBub3QgYmUgY29udHJv bGxlZCBieSB0aGUgU0ROIGNvbnRyb2xsZXIuIFNvbHV0aW9ucyBhcmUgZWFnZXIgdG8gYmUgZm91 bmQgb3V0LiBBbmQgSSBnaXZlIG91dCB0d28gc29sdXRpb25zIGluIGFub3RoZXIgZHJhZnQgd2hp Y2ggSSB3aWxsIGludHJvZHVjZSBpbiB0aGUgYmVsb3cuDQoNCigzKSBDbG91ZCBkYXRhY2VudGVy IGVubGFyZ2VtZW50DQoNCkluIHRoZSBzaW11bGF0aW9uIHRlc3QsIHdoZW4gMzAwIHZpcnR1YWwg bWFjaGluZXMgYXJlIGNyZWF0ZWQgYXQgb25lIHRpbWUsIGl0IHRha2VzIGFib3V0IDMwIG1pbml0 ZXMgb2YgdGhlIGNvbnRyb2xsZXIgdG8gZG93bmxvYWQgdGhlIGZsb3cgdGFibGUuIFNvIHdoZW4g dGhlIGNsb3VkIGRhdGVjZW50ZXIgaXMgZW5sYXJnZWQsIHRoZSBjby1jdXJyZW50IHBlcmZvcm1h bmNlIHNob3VsZCBiZSB0YWtlbiBpbnRvIGNvbnNpZGVyYXRpb24uIEJlc2lkZXMsIHRoZSBvcGVu c3RhY2sgb3IgQ29udHJvbGxlciBvciBmb3J3YXJkaW5nIGRldmljZXMgaGF2ZSBhIGxpbWl0IG9u IHRoZSBudW1iZXIgb2YgdmlydHVhbCBtYWNoaW5lcyBjcmVhdGVkLiBTbyB3aGVuIHRha2luZyBp bnRvIGhvdyB0byBlbmxhcmdlIHRoZSBjbG91ZCBkYXRlY2VudGVycywgdGhlcmUgc2hvdWxkIGJl IGNvbnNpZGVyZWQuDQoNCig0KSBEYXRhIGNlbnRlciBpbnRlcmNvbm5lY3Rpb24NCg0KVGhlcmUg YXJlIG5vIHRyaWFsIGFuZCBzY2hlbWUgb2YgU0ROIGRhdGFjZW50ZXJzIGJlbG9uZ3MgdG8gZGlm ZmVyZW50IHZlbmRvcnMgaW50ZXJjb25uZWN0ZWQgd2l0aCBlYWNoIG90aGVyLiBCZXNpZGVzLCB3 aGVuIFNETiBkYXRhY2VudGVycyBpbnRlcmNvbm5lY3RzIHdpdGggdHJhZGl0aW9uYWwgZGF0YWNl bnRlcnMsIHNvbWUgZXh0cmEgZGV2aWNlcyBzaG91bGQgYmUgYWRkZWQgaW4gdGhlIHRyYWRpdGlv bmFsIGRhdGFjZW50ZXJzLg0KDQoNCkFub3RoZXIgbmV3IGRyYWZ0IGlzIGFib3V0IHRoZSBkZWNv dXBsaW5nIHNoY2VtZSBmb3IgaHlwZXJ2aXNvciBmcm9tIFNETiBhcmNoaXRlY3R1cmUgd2hpY2gg Z2l2ZXMgb3V0IHR3byBzb2x1dGlvbnMgYWNjb3JkaW5nIHRvIHRoZSBwcm9ibGVtcyBvZiBoeXBl cnZpc29yLg0KDQpodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1ndS1zZG5y Zy1wcm9ibGVtLXN0YXRlbWVudC1vZi1zZG4tbmZ2LWluLWRjLw0KDQo8aHR0cHM6Ly9kYXRhdHJh Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZ3Utc2RucmctcHJvYmxlbS1zdGF0ZW1lbnQtb2Ytc2Ru LW5mdi1pbi1kYy8+SW4gdGhpbmtpbmcgb3ZlciBzb21lIGNvbW1lcmNpYWwgaHlwZXJ2aXNvcnMg d2hpY2ggaXMgYm9uZGluZyB0aGUgdmlydHVhbCBzd2l0Y2ggd2l0aG91dCB0aGUgY29udHJvbCBv ZiBTRE4gY29udHJvbGxlciwgdGhlcmUgYXJlIHR3byBzb2x1dGlvbnM6DQoNCigxKSBzdWJzdGl0 dXRpbmcgdGhlIHZpcnR1YWwgc3dpdGNoIG9mIGh5cGVydmlzb3Igd2l0aCB0aGUgdmlydHVhbCBz d2l0Y2ggd2hpY2ggY2FuIGJlIGNvbnRyb2xsZWQgYnkgdGhlIFNETiBjb250cm9sbGVyLiBIb3dl dmVyLCB0aGUgbGltaXRhdGlvbiByZWxpZXMgb24gdGhhdCB0aGUgcHJpdmF0ZSBpbnRlcmZhY2Ug b2YgaHlwZXJ2aXNvciBzaG91bGQgYmUgb3Blbi4NCg0KKDIpIFVzaW5nIG9uZSB2aXJ0dWFsIG1h Y2hpbmUgYWN0aW5nIGFzIHRoZSB2aXJ0dWFsIHN3aXRjaCBieSBkaXJlY3RpbmcgYWxsIHRoZSB0 cmFmZmljIHRocm91Z2ggdGhlIHZpcnR1YWwgbWFjaGluZXMuIFRoZSBsaW1pdGF0aW9uIHJlbGll cyBvbiB0aGUgcHJpdmF0ZSBpbnRlcmZhY2UgcGFydGlhbGx5IGFuZCB0aGUgdmlydHVhbCBtYWNo aW5lIGNhbiBiZSB0aGUgYm90dGxlbmVjayBvZiBwZXJmb3JtYW5jZS4NCg0KT3RoZXIgc29sdXRp b25zIGFyZSBlYWdlciB0byBiZSBmb3VuZCBvdXQuDQoNCg0KDQoNCg0KDQo8aHR0cHM6Ly9kYXRh dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtZ3Utc2RucmctcHJvYmxlbS1zdGF0ZW1lbnQtb2Yt c2RuLW5mdi1pbi1kYy8+DQoNCg0KDQoNCg0KDQo= --_000_SG2PR02MB1101E72883AD9D46C9705C968B9D0SG2PR02MB1101apcp_ Content-Type: text/html; charset="gb2312" Content-Transfer-Encoding: quoted-printable

Hi, dear all. 

I have made the presentation in a rush this morning. So I accept the adv= ice from chairs to express my ideas in the mail-list. Hope that it's better= for understanding.

As there are two drafts related in my presentations. It will be grateful= of you to go through the draft and comments on that.


One is the updated version of the draft of problem statement of SDN and = NFV co-deployment in cloud datacenters. 

http= s://datatracker.ietf.org/doc/draft-gu-sdnrg-problem-statement-of-sdn-nfv-in= -dc/

The updated contexts are:

(1) Network architecture changes when the bare-metal servers are brought= in. SDN ToR and the openstack modules such as ironic and neutron should be= brought in or be partically influenced.

As in the bare-metal server scenario, SDN TOR should be acted as the vte= p. And the openstack ironic module are used to power the server and install= the operating systems. 

(2) Hypervisor:

When other hypervisors rather than KVM is accepted, something should be = noted is that the virtual switch bonding with the hypervisor may not be con= trolled by the SDN controller. Solutions are eager to be found out. And I g= ive out two solutions in another draft which I will introduce in the below.

(3) Cloud datacenter enlargement

In the simulation test, when 300 virtual machines are created at one tim= e, it takes about 30 minites of the controller to download the flow table. = So when the cloud datecenter is enlarged, the co-current performance should= be taken into consideration. Besides, the openstack or Controller or forwarding devices have a limit on the numb= er of virtual machines created. So when taking into how to enlarge the clou= d datecenters, there should be considered.

(4) Data center interconnection

There are no trial and scheme of SDN datacenters belongs to differe= nt vendors interconnected with each other. Besides, when SDN datacente= rs interconnects with traditional datacenters, some extra devices should be= added in the traditional datacenters.


Another new draft is about the decoupling shceme for hypervisor from SDN= architecture which gives out two solutions according to the problems of hy= pervisor.

http= s://datatracker.ietf.org/doc/draft-gu-sdnrg-problem-statement-of-sdn-nfv-in= -dc/

In thinking ov= er some commercial hypervisors= which is bonding the virtual switch without the control of SDN controller, there are two solutions:

(1) substituting the virtual switch of = hypervisor with the virtual switch which can be controlled by the SDN contr= oller. However, the limitation relies on that the private interface of hype= rvisor should be open.

(2) Using one virtual machine acting as= the virtual switch by directing all the traffic through the virtual machin= es. The limitation relies on the private interface partially and the virtua= l machine can be the bottleneck of performance.

Other solutions are eager to be found o= ut.


 






 



--_000_SG2PR02MB1101E72883AD9D46C9705C968B9D0SG2PR02MB1101apcp_-- From nobody Tue Apr 5 07:26:58 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 02CB912D186 for ; Tue, 5 Apr 2016 07:26:57 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.468 X-Spam-Level: X-Spam-Status: No, score=-1.468 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 YIEmotkHI3sS for ; Tue, 5 Apr 2016 07:26:54 -0700 (PDT) Received: from mail-ob0-x241.google.com (mail-ob0-x241.google.com [IPv6:2607:f8b0:4003:c01::241]) (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 3506B12D557 for ; Tue, 5 Apr 2016 07:21:16 -0700 (PDT) Received: by mail-ob0-x241.google.com with SMTP id c1so1083757obw.3 for ; Tue, 05 Apr 2016 07:21:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=slBe+Y7wSck+07U9dDSeRNq0VzRbRHtEJVBOHxOUO4o=; b=HD5/Wa+Z+I5UKiYrbaeMHNHa0S/sfEClb20buV/6zd/PZ045qhl9i0/pWj97nCpOzr DOfHIZawJhNTmusgi6mnhRV8sjl5Bf8ZkH+M45T1zbtenubQ3qm2Dbeja/TQlctR89OW G0kJAcdYmpff2/qjGAIQPfBQdqBUW3K86hojXOXrk4dAgi0G1JFBcGhAUaIBrMww4cN7 mpK8dw2qxyEoteicixijsTDNZJlvAU3GUoQu/QUGUkNgIiFuJpgxG1yx55E/Fdm0uvsq nee3GNwGgELwaAGJeohDMNIy2fBRBdqB9uYCA5gaE8y6iijxTN+kUMCBNKuAPtVcAjSg drNw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=slBe+Y7wSck+07U9dDSeRNq0VzRbRHtEJVBOHxOUO4o=; b=UV1cFfLiMK75cAhdwzX1RKCxk8aGv6LJ/xyoHcr9yOXGqvJ0S3mAMiM/1KBWQ/guFT mSXbonxWOWQIPlBnQxt2Ai1D4x78D6ES7mpVpiQPAcR2osb4NaYj0gnAbUFRy0PkI/nZ wi8BaxC5EybHCzH5rg/9X96n5mK4P7WJcOHEV5CTP0wusyirsTKRzVPGykwpOsBK/Fne NVjEjZRjH3kVPB30rQxSK7n9HEPRlGT5yCte5ZvZZoepuQivZLRMo1qoVmZvkzZyBfnl 5tCCMIvdfxJLuv0Rq3WKgXYFLt7vqf+DRFv6/Oc0tpRwDWxhFfKj4oXGla/qmp2y5PoN WGbg== X-Gm-Message-State: AD7BkJIkiYCu0phaAaFIy6jkMK9WkA8e5uuujYidnqj2UfLLhUmXXI3lFkiASNNtGzeNI2QowHrcmyP/L9h/mw== MIME-Version: 1.0 X-Received: by 10.182.38.199 with SMTP id i7mr14431606obk.86.1459866075498; Tue, 05 Apr 2016 07:21:15 -0700 (PDT) Received: by 10.202.235.210 with HTTP; Tue, 5 Apr 2016 07:21:15 -0700 (PDT) In-Reply-To: <20160405141525.25931.4285.idtracker@ietfa.amsl.com> References: <20160405141525.25931.4285.idtracker@ietfa.amsl.com> Date: Tue, 5 Apr 2016 22:21:15 +0800 Message-ID: From: xinjian Long To: sdn@irtf.org Content-Type: multipart/alternative; boundary=001a11c32ddcd98f96052fbd8e6d Archived-At: Subject: [Sdn] Fwd: New Version Notification for draft-long-sdnrg-pfrrmpm-openflow-00.txt X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Apr 2016 14:26:57 -0000 --001a11c32ddcd98f96052fbd8e6d Content-Type: text/plain; charset=UTF-8 Hello, we want to make you aware of a new I-D named Priority based Flow Rule Request Message Processing Mechanism in the OpenFlow Switch. The interesting part of this document for SDNRG is probably the processing order of the control messages within a transaction between the controller and the OpenFlow switch. This document proposes the combination of appending the priority attribute to the packet-in message and the PFRRMPM as one solution to this problem. On the other hand, we want to have more people to recognize and highlight the similar problem so as to extend and generalize it to the other aspects in the Control Plane Southbound Interface(or the SDN) instead of being specific to the OpenFlow. We are eager to hear your comments, criticisms, and questions. Best regards, Xinjian Long ---------- Forwarded message ---------- From: Date: 2016-04-05 22:15 GMT+08:00 Subject: New Version Notification for draft-long-sdnrg-pfrrmpm-openflow-00.txt To: Xinjian Long , Xiangyang Gong < xygong@bupt.edu.cn>, Xirong Que , Wendong Wang < wdwang@bupt.edu.cn>, Qinglei Qi A new version of I-D, draft-long-sdnrg-pfrrmpm-openflow-00.txt has been successfully submitted by Xinjian Long and posted to the IETF repository. Name: draft-long-sdnrg-pfrrmpm-openflow Revision: 00 Title: Priority based Flow Rule Request Message Processing Mechanism in the OpenFlow Switch Document date: 2016-04-04 Group: Individual Submission Pages: 13 URL: https://www.ietf.org/internet-drafts/draft-long-sdnrg-pfrrmpm-openflow-00.txt Status: https://datatracker.ietf.org/doc/draft-long-sdnrg-pfrrmpm-openflow/ Htmlized: https://tools.ietf.org/html/draft-long-sdnrg-pfrrmpm-openflow-00 Abstract: In the SDN, the controller is in charge of the maintenance and administration of variable aspects like the network topology and the network resources etc. of the whole network. Administrative strategies are made upon these work and sent to the switches from the controller so as to instruct the network devices to apply appropriate policies to the data flows. As for the data packet which reaches the ingress OpenFlow switch for the first time, the packet itself or a fraction of the packet will be encapsulated into a packet-in message and will be sent to the controller to request for a new flow rule. After the flow-mod message and the packet-out message are sent back to the switch from the controller, the determined forwarding action will be applied to the certain data flow. So far, the inbound latency caused by the creation of the packet-in message and the outbound latency caused by the receive and the execution of the flow-mod message are highlighted when it comes to the concerns about the latency and the effectiveness of the data transportation in the SDN[Mazu]. Attention to the studies on the processing order of the flow rule request message like the packet-in message and the packet-out message is comparatively low. As the SDN continually grows in scale and complexity and the packets' forwarding policies become more recursive and dynamic, the number of the switches under the administration of the same controller is elevated and unavoidably causes the network congestion problem widespread. The scale of modern networks and data-centers and the associated operational expense deteriorates the delay problem in the network with congestion. The ability to help the services with high priority be processed without delay becomes critical. This document proposes the combination of appending a priority tag to the packet-in message and the Priority based Flow Rule Request Message Processing Mechanism(PFRRMPM) as a solution to help the data flow with high priority or lantency-sensitive to acquire the forwarding rule without or with shorter waiting latency when there are excess flow rule request messages in the SDN. Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. The IETF Secretariat --001a11c32ddcd98f96052fbd8e6d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

Hello, we want to make you aware of a new= I-D named Priority based Flow Rule Request Message Processing Mechanism in the= OpenFlow Switch.

=C2=A0

The interesting part of this document for SDNRG is probably the = processing = order of the=C2=A0control messages within a transaction between the controller an= d the OpenFlow switch. This document proposes the combination of appending = the priority attribute to the packet-in message and the PFRRMPM as one solu= tion to this problem. On the other hand, we want to have more people to rec= ognize and highlight the similar problem so as to extend and generalize it = to the other aspects in the Control Plane Southbound Interface(or the SDN) = instead of being specific to the OpenFlow.

=C2=A0=

We are eager to hear your comments, criticisms, and questio= ns.<= /span>


Best regards,

Xinjian Long


-----= ----- Forwarded message ----------
From: <= /b> <inter= net-drafts@ietf.org>
Date: 2016-04-05 22:15 GMT+08:00
S= ubject: New Version Notification for draft-long-sdnrg-pfrrmpm-openflow-00.t= xt
To: Xinjian Long <xjlo= ng19921117@gmail.com>, Xiangyang Gong <xygong@bupt.edu.cn>, Xirong Que <rongqx@bupt.edu.cn>, Wendong Wang <wdwang@bupt.edu.cn>, Qinglei Qi <qiqinglei1984@126.com>


A new version of I-D, draft-long-sdnrg-pfrrmpm-openflow-00.txt
has been successfully submitted by Xinjian Long and posted to the
IETF repository.

Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-long-sdnrg-pfrrmpm-open= flow
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A000
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Priority based Flow Rule Request M= essage Processing Mechanism in the OpenFlow Switch
Document date:=C2=A0 2016-04-04
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 13
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 https://www.ietf.org/internet-drafts/draft-long-sdnr= g-pfrrmpm-openflow-00.txt
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0https://datatracker.ietf.org/doc/draft-long-sdnrg-pfrrmpm-openflow/=
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0= https://tools.ietf.org/html/draft-long-sdnrg-pfrrmpm-openflow-00


Abstract:
=C2=A0 =C2=A0In the SDN, the controller is in charge of the maintenance and=
=C2=A0 =C2=A0administration of variable aspects like the network topology a= nd the
=C2=A0 =C2=A0network resources etc. of the whole network.=C2=A0 Administrat= ive
=C2=A0 =C2=A0strategies are made upon these work and sent to the switches f= rom the
=C2=A0 =C2=A0controller so as to instruct the network devices to apply appr= opriate
=C2=A0 =C2=A0policies to the data flows.=C2=A0 As for the data packet which= reaches the
=C2=A0 =C2=A0ingress OpenFlow switch for the first time, the packet itself = or a
=C2=A0 =C2=A0fraction of the packet will be encapsulated into a packet-in m= essage
=C2=A0 =C2=A0and will be sent to the controller to request for a new flow r= ule.
=C2=A0 =C2=A0After the flow-mod message and the packet-out message are sent= back
=C2=A0 =C2=A0to the switch from the controller, the determined forwarding a= ction
=C2=A0 =C2=A0will be applied to the certain data flow.

=C2=A0 =C2=A0So far, the inbound latency caused by the creation of the pack= et-in
=C2=A0 =C2=A0message and the outbound latency caused by the receive and the=
=C2=A0 =C2=A0execution of the flow-mod message are highlighted when it come= s to
=C2=A0 =C2=A0the concerns about the latency and the effectiveness of the da= ta
=C2=A0 =C2=A0transportation in the SDN[Mazu].=C2=A0 Attention to the studie= s on the
=C2=A0 =C2=A0processing order of the flow rule request message like the pac= ket-in
=C2=A0 =C2=A0message and the packet-out message is comparatively low.=C2=A0= As the SDN
=C2=A0 =C2=A0continually grows in scale and complexity and the packets'= forwarding
=C2=A0 =C2=A0policies become more recursive and dynamic, the number of the<= br> =C2=A0 =C2=A0switches under the administration of the same controller is el= evated
=C2=A0 =C2=A0and unavoidably causes the network congestion problem widespre= ad.
=C2=A0 =C2=A0The scale of modern networks and data-centers and the associat= ed
=C2=A0 =C2=A0operational expense deteriorates the delay problem in the netw= ork
=C2=A0 =C2=A0with congestion.=C2=A0 The ability to help the services with h= igh priority
=C2=A0 =C2=A0be processed without delay becomes critical.

=C2=A0 =C2=A0This document proposes the combination of appending a priority= tag to
=C2=A0 =C2=A0the packet-in message and the Priority based Flow Rule Request=
=C2=A0 =C2=A0Message Processing Mechanism(PFRRMPM) as a solution to help th= e data
=C2=A0 =C2=A0flow with high priority or lantency-sensitive to acquire the =C2=A0 =C2=A0forwarding rule without or with shorter waiting latency when t= here
=C2=A0 =C2=A0are excess flow rule request messages in the SDN.




Please note that it may take a couple of minutes from the time of submissio= n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat


--001a11c32ddcd98f96052fbd8e6d-- From nobody Thu Apr 7 15:05:27 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9379612D72A for ; Thu, 7 Apr 2016 15:05:25 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.23 X-Spam-Level: X-Spam-Status: No, score=-4.23 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=unavailable 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 HtpoEE8DIBvZ for ; Thu, 7 Apr 2016 15:05:24 -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 7BB8112D103 for ; Thu, 7 Apr 2016 15:05:17 -0700 (PDT) Received: from 172.24.1.137 (EHLO SZXEMA414-HUB.china.huawei.com) ([172.24.1.137]) by szxrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id DIH73960; Fri, 08 Apr 2016 06:04:59 +0800 (CST) Received: from SZXEMA509-MBS.china.huawei.com ([169.254.2.235]) by SZXEMA414-HUB.china.huawei.com ([10.82.72.73]) with mapi id 14.03.0235.001; Fri, 8 Apr 2016 06:04:56 +0800 From: "Liushucheng (Will)" To: "supa@ietf.org" , "sdn@irtf.org" Thread-Topic: SUPA ECA Demo @ BnB today Thread-Index: AdGRGYFse9G4OkGMTSWmXXD7wSnTSQ== Date: Thu, 7 Apr 2016 22:04:55 +0000 Message-ID: Accept-Language: en-US, zh-CN Content-Language: zh-CN X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.212.197.234] Content-Type: multipart/alternative; boundary="_000_C9B5F12337F6F841B35C404CF0554ACB896D9F16SZXEMA509MBSchi_" MIME-Version: 1.0 X-CFilter-Loop: Reflected X-Mirapoint-Virus-RAPID-Raw: score=unknown(0), refid=str=0001.0A020201.5706D98B.026C, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0, ip=169.254.2.235, so=2013-06-18 04:22:30, dmn=2013-03-21 17:37:32 X-Mirapoint-Loop-Id: 790fff9fd3ac30c113fd543a66871138 Archived-At: Subject: [Sdn] SUPA ECA Demo @ BnB today X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 07 Apr 2016 22:05:25 -0000 --_000_C9B5F12337F6F841B35C404CF0554ACB896D9F16SZXEMA509MBSchi_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hi all, Just like what John has mentioned in SDNRG on Monday, we will have a Demo o= n SUPA ECA at BnB today. Welcome to join us. Thank you! Regards, Will ---------------------------------------------------------------------------= -------- Shucheng LIU (Will), Ph.D. Senior Researcher & Standard Representative, Project Manager Huawei Technologies Co.,Ltd Email: liushucheng@huawei.com http://www.linkedin.com/in/shucheng ---------------------------------------------------------------------------= -------- --_000_C9B5F12337F6F841B35C404CF0554ACB896D9F16SZXEMA509MBSchi_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hi all,

 

Just like what John has mention= ed in SDNRG on Monday, we will have a Demo on SUPA ECA at BnB today. Welcom= e to join us. Thank you!

 

Regards,

Will

----------------------------------------------------------------= -------------------

Shucheng LIU (Will), Ph.D.

Senior Researcher & Standard Representative, Project Manag= er

Huawei Technologies Co.,Ltd

Email: liushu= cheng@huawei.com

http://www.linkedin.com/in/shucheng

----------------------------------------------------------------= -------------------

 

--_000_C9B5F12337F6F841B35C404CF0554ACB896D9F16SZXEMA509MBSchi_-- From nobody Fri Apr 8 01:06:39 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22EBF12D51F for ; Fri, 8 Apr 2016 01:06:39 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -4.209 X-Spam-Level: X-Spam-Status: No, score=-4.209 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] 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 nTVR2hYUmZFR for ; Fri, 8 Apr 2016 01:06:37 -0700 (PDT) Received: from ees2.oulu.fi (ee.oulu.fi [130.231.61.23]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9A77212D1BA for ; Fri, 8 Apr 2016 01:06:36 -0700 (PDT) Received: from [10.100.11.209] (ee-gw5.oulu.fi [130.231.61.15]) (authenticated bits=0) by ees2.oulu.fi (8.14.7/8.14.7) with ESMTP id u3886WNh014335 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 8 Apr 2016 11:06:33 +0300 To: sdn@irtf.org From: Ijaz Ahmad Message-ID: <57076A65.7000107@ee.oulu.fi> Date: Fri, 8 Apr 2016 11:23:01 +0300 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------000509030905000804000406" Archived-At: Subject: [Sdn] SDN-based 5G Security, The Comprehensive Guide to 5G Security X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Apr 2016 08:06:39 -0000 This is a multi-part message in MIME format. --------------000509030905000804000406 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Dear All, We would like to bring your attention to the edited book on "Comprehensive Guide to 5G Security". This book would be published by WILEY Publishers and it is anticipated to be in print by August 2017 tentatively. We kindly request you to contribute chapters for the book based on your research area. There are topics related to Software-Defined Mobile Networks (SDMN) and NFV Security. For further details, please visit the website: https://sites.google.com/site/5gbook2017/ _*Call for Chapters - Important Dates *_ * Proposals Submission Deadline: *31th July 2016 * * Acceptance of Proposals: *31st August 2016* * Full Chapter Submission: *01th December 2016* * Review Results: *15th January 2017* * Final Chapters Due: *14th February 2017* For further inquiries/questions, you can contact us on E-mail: 5gbook2017@gmail.com or visit Website: https://sites.google.com/site/5gbook2017/ Thanking you, -- Ijaz Ahmad Center for Wireless Communications (CWC), University of Oulu, Oulu Finland. Phone: +358-453 301 160 Email: iahmad@ee.oulu.fi --------------000509030905000804000406 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Dear All,

We would like to bring your attention to the edited book on "Comprehensive Guide to 5G Security". This book would be published by WILEY Publishers  and it is anticipated to be in print by August 2017 tentatively. We kindly request you to contribute chapters for the book based on your research area.

There are topics related to Software-Defined Mobile Networks (SDMN) and NFV Security. For further details, please visit the website: https://sites.google.com/site/5gbook2017/

Call for Chapters - Important Dates
  • Proposals Submission Deadline: 31th July 2016
  • Acceptance of Proposals: 31st August 2016
  • Full Chapter Submission: 01th December 2016
  • Review Results: 15th January 2017
  • Final Chapters Due: 14th February 2017

For further inquiries/questions, you can contact us on
E-mail: 5gbook2017@gmail.com  or visit
Website: https://sites.google.com/site/5gbook2017/

Thanking you,

-- 
Ijaz Ahmad
Center for Wireless Communications (CWC),
University of Oulu, Oulu
Finland.
Phone: +358-453 301 160
Email: iahmad@ee.oulu.fi
--------------000509030905000804000406-- From nobody Wed Apr 13 00:50:39 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9BE7412DDDB for ; Wed, 13 Apr 2016 00:50:38 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.618 X-Spam-Level: X-Spam-Status: No, score=-3.618 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-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 F8Kf2HLTL4H9 for ; Wed, 13 Apr 2016 00:50:36 -0700 (PDT) Received: from tama500.ecl.ntt.co.jp (tama500.ecl.ntt.co.jp [129.60.39.148]) by ietfa.amsl.com (Postfix) with ESMTP id 3B4A512D8D3 for ; Wed, 13 Apr 2016 00:50:36 -0700 (PDT) Received: from vc1.ecl.ntt.co.jp (vc1.ecl.ntt.co.jp [129.60.86.153]) by tama500.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id u3D7oWFp011621 for ; Wed, 13 Apr 2016 16:50:32 +0900 Received: from vc1.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 299125F65A for ; Wed, 13 Apr 2016 16:50:32 +0900 (JST) Received: from jcms-pop11.ecl.ntt.co.jp (jcms-pop11.ecl.ntt.co.jp [129.60.87.132]) by vc1.ecl.ntt.co.jp (Postfix) with ESMTP id 1C8965F612 for ; Wed, 13 Apr 2016 16:50:32 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.21.83]) by jcms-pop11.ecl.ntt.co.jp (Postfix) with ESMTP id 14C7570C09B2 for ; Wed, 13 Apr 2016 16:50:32 +0900 (JST) From: Kohei Shiomoto Message-ID: <570DFD42.8080607@lab.ntt.co.jp> Date: Wed, 13 Apr 2016 17:03:14 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit To: sdn@irtf.org X-TM-AS-MML: disable Archived-At: Subject: [Sdn] CFP: ACM, IRTF & ISOC Applied Networking Research Workshop 2016 X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2016 07:50:38 -0000 Dear all The following workshop will be held just before the next IETF/IRTF meeting in Berlin. It might be of interest to you. Best regards, Dan & Kohei =========================================================================== ACM, IRTF & ISOC Applied Networking Research Workshop 2016 Berlin, Germany Saturday, July 16, 2016 https://irtf.org/anrw/2016/ *** CALL FOR PAPERS *** The inaugural ACM, IRTF & ISOC Applied Networking Research Workshop 2016 (ANRW’16) is an academic workshop that provides a forum for researchers, vendors, network operators, and the Internet standards community to present and discuss emerging results in applied networking research. It is sponsored by ACM SIGCOMM, the Internet Research Task Force (IRTF) and the Internet Society (ISOC). Researchers should consider submitting early/emerging results that illustrate the scientific and engineering principles underlying the Internet architecture, protocols and applications; that demonstrate new capabilities, features, or extensions to the Internet protocol layers; that enhance our understanding of how Internet protocols work in real-world deployments or realistic test-beds; or that improve Internet security and privacy, scalability, performance, and robustness. The ANRW’16 particularly encourages the submission of results that could form the basis for future engineering work in the IETF, that could change operational Internet practices, that can help better specify Internet protocols, or that could influence further research and experimentation in the IRTF. *** TOPICS OF INTEREST *** Topics of interest include, but are not limited to, applied work in the following areas: * Evolution of the Internet architecture and deployment of new Internetworking paradigms * Naming, addressing, and routing for the future Internet * Development and deployment of new and improved transport protocols * Congestion control for heterogeneous networks and novel applications * Improvements to the security and privacy of Internet protocols * Studies that characterize Internet security, privacy or censorship * Measuring and understanding the behaviour and transparency of the Internet * Internetworking and semantic interoperability for resource-constrained devices * New approaches to network management, operations, and control * Better ways of specifying protocols, including usable techniques for protocol verification * Enabling global access to the Internet * Improving the energy efficiency of the Internet * Protocols and APIs for new Internet applications * New approaches to decentralized mobility management * Application of network programmability to the Internet *** SUBMISSION TYPES *** The ANRW accepts two types of submissions: full papers and short papers. * Full papers Full paper submissions should be complete academic papers on the topics above and may contain up to six pages of technical content, including figures, tables, any appendices, etc., optionally followed by a single additional page for references and acknowledgements only. Accepted full papers will be presented and discussed in depth at the workshop, and will be published in the ACM Digital Library. * Short papers Short paper submissions are suitable for short position papers, for starting a discussion on new technical ideas, to present very early results, or to present other topics of interest to the community (software and tools, research initiatives or collaborative projects, major new funding vessels, etc.). They may contain up to two pages of content including figures, tables, any appendices, etc., optionally followed by a single additional page for references and acknowledgements only. Accepted short papers will be briefly presented during the workshop, and will be published in the ACM Digital Library. Authors of accepted short papers may also bring a poster presenting its content to the workshop, for display and more in-depth discussion with interested participants during the breaks. *** IMPORTANT DATES *** Submission deadline: May 16, 2016 Notification deadline: June 17, 2016 Camera-ready deadline: June 24, 2016 *** ORGANISING COMMITTEE *** Programme chairs: * Lars Eggert (NetApp) * Colin Perkins (University of Glasgow) Technical Programme Committee: * Aaron Falk (Akamai) * Gorry Fairhurst (University of Aberdeen) * Stephen Farrell (Trinity College Dublin) * Jana Iyengar (Google) * Dirk Kutscher (NEC Laboratories Europe) * Mirja Kühlewind (ETH Zürich) * Al Morton (AT&T) * Jörg Ott (Technische Universität München) * Arjuna Sathiaseelan (University of Cambridge) * Brian Trammell (ETH Zürich) * Lixia Zhang (UCLA) From nobody Wed Apr 13 00:57:17 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 17A8B12E117 for ; Wed, 13 Apr 2016 00:57:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -3.597 X-Spam-Level: X-Spam-Status: No, score=-3.597 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.996, SPF_HELO_PASS=-0.001, SPF_PASS=-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 Ln5mW2Dbc9eD for ; Wed, 13 Apr 2016 00:57:12 -0700 (PDT) Received: from tama50.ecl.ntt.co.jp (tama50.ecl.ntt.co.jp [129.60.39.147]) by ietfa.amsl.com (Postfix) with ESMTP id 1772612E157 for ; Wed, 13 Apr 2016 00:57:09 -0700 (PDT) Received: from vc2.ecl.ntt.co.jp (vc2.ecl.ntt.co.jp [129.60.86.154]) by tama50.ecl.ntt.co.jp (8.13.8/8.13.8) with ESMTP id u3D7v8bT021620 for ; Wed, 13 Apr 2016 16:57:08 +0900 Received: from vc2.ecl.ntt.co.jp (localhost [127.0.0.1]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id AA3745F593 for ; Wed, 13 Apr 2016 16:57:08 +0900 (JST) Received: from jcms-pop11.ecl.ntt.co.jp (jcms-pop11.ecl.ntt.co.jp [129.60.87.132]) by vc2.ecl.ntt.co.jp (Postfix) with ESMTP id 9C4035F592 for ; Wed, 13 Apr 2016 16:57:08 +0900 (JST) Received: from [IPv6:::1] (unknown [129.60.21.83]) by jcms-pop11.ecl.ntt.co.jp (Postfix) with ESMTP id 84CEC70C09B2 for ; Wed, 13 Apr 2016 16:57:08 +0900 (JST) References: <570D8292.309@alcatel-lucent.com> From: Kohei Shiomoto X-Forwarded-Message-Id: <570D8292.309@alcatel-lucent.com> Message-ID: <570DFECD.70804@lab.ntt.co.jp> Date: Wed, 13 Apr 2016 17:09:49 +0900 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.7.2 MIME-Version: 1.0 In-Reply-To: <570D8292.309@alcatel-lucent.com> Content-Type: multipart/alternative; boundary="------------050503050804000302020003" To: sdn@irtf.org X-TM-AS-MML: disable Archived-At: Subject: [Sdn] Fwd: [irsg] Fwd: Cross-RG activity coordination on Intent Based Networking (IBN) X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Apr 2016 07:57:15 -0000 This is a multi-part message in MIME format. --------------050503050804000302020003 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Dear all We will have a joint meeting with NMRG, NFVRG, and SDNRG in the next IETF/IRTF meeting. It is the first announcement. Dan and Kohei -------- Forwarded Message -------- Subject: [irsg] Fwd: Cross-RG activity coordination on Intent Based Networking (IBN) Date: Wed, 13 Apr 2016 01:19:46 +0200 From: Laurent Ciavaglia Organization: Bell Labs To: Internet Research Steering Group Dear IRSG members, This initiative might be of interest to your research groups / communities. Please feel free to forward to and involve them ;) Thanks, best regards, Laurent. -------- Forwarded Message -------- Subject: Cross-RG activity coordination on Intent Based Networking (IBN) Date: Wed, 13 Apr 2016 00:57:21 +0200 From: Laurent Ciavaglia Organization: Bell Labs To: nmrg@irtf.org CC: Kohei Shiomoto , King, Daniel , Lisandro Zambenedetti Granville , Laurent Ciavaglia Dear NMRG, Intent Based Networking aspires at rising network manageability to a higher level. As such, the various forms of IBN continue to be a compelling area of research and technology development. Yet, the IBN term may convey different meanings and refer to different concepts or approaches, e.g. as in ANIMA WG, SUPA (BoF), IBNEMO, or SDN RG... Thus, we believe some coordination among RG/WG can deliver additional value to the community. Jointly with the SDN RG, we would like to impulse an activity on IBN to discuss the objectives, scope and kick start this effort. The items listed below can help to get things started: -What are the definitions of Intent/IBN? e.g. in SUPA, ANIMA, SDN, NFV, IoT spaces... -What are the alignment/commonalities and differences among them, and the implications from technology, standard and business perspectives? -What are the functionality / components of an intent based system? -Is an end-to-end, comprehensive intent based system feasible? Does it make sense? -How can different techno-specific / heterogeneous sources of intent (definitions / blocks) inter-operate, in intra- and inter-domains? -What are the (key) areas of research? languages, semantics/ontologies, human factors/HNI, model-driven-development, policy refinement... -What are examples of application: e.g. technology specific or generic: e.g. in NFV, SDN, autonomics, IoT... -What relationships/consistency among those applications? i.e. towards a comprehensive view of a "Generalized IBN" -List of representative use cases of IBN. -Practical experiences, developments, tools on IBN. The network management community has extensive knowledge and expertise in the area (think policy based management) that can prove very useful in the foreseen investigations. Network management is also transverse to technologies (e.g. SDN, NFV, autonomics...), providing a different perspective to the problem at hand. --- The first outcome of this activity will be discussed in the joint meeting between SDN, NFV and NM research groups to be held at IETF96/Berlin (TBC). This topic is part of the NMRG meeting at NOMS 2016 (http://noms2016.ieee-noms.org, 25-29 April 2016, Istanbul). Other events are in the pipe, so stay tuned! Best regards, Lisandro and Laurent (NMRG chairs), together with Kohei and Dan (SDN RG chairs). --- -- Laurent Ciavaglia Senior Research Manager Bell Labs, Nokia +33 160 402 636 Route de Villejust | 91620 Nozay | France LinkedIn: laurentciavaglia --------------050503050804000302020003 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit Dear all

We will have a joint meeting with NMRG, NFVRG, and SDNRG in the next IETF/IRTF meeting.
It is the first announcement.

Dan and Kohei

-------- Forwarded Message --------
Subject: [irsg] Fwd: Cross-RG activity coordination on Intent Based Networking (IBN)
Date: Wed, 13 Apr 2016 01:19:46 +0200
From: Laurent Ciavaglia <laurent.ciavaglia@nokia.com>
Organization: Bell Labs
To: Internet Research Steering Group <irsg@irtf.org>


Dear IRSG members,

This initiative might be of interest to your research groups / communities.

Please feel free to forward to and involve them ;)

Thanks, best regards, Laurent.


-------- Forwarded Message --------
Subject: Cross-RG activity coordination on Intent Based Networking (IBN)
Date: Wed, 13 Apr 2016 00:57:21 +0200
From: Laurent Ciavaglia <Laurent.Ciavaglia@alcatel-lucent.com>
Organization: Bell Labs
To: nmrg@irtf.org <nmrg@irtf.org>
CC: Kohei Shiomoto <shiomoto.kohei@lab.ntt.co.jp>, King, Daniel <d.king@lancaster.ac.uk>, Lisandro Zambenedetti Granville <granville@inf.ufrgs.br>, Laurent Ciavaglia <Laurent.Ciavaglia@nokia.com>


Dear NMRG,

Intent Based Networking aspires at rising network manageability to a higher level.
As such, the various forms of IBN continue to be a compelling area of research and technology development.
Yet, the IBN term may convey different meanings and refer to different concepts or approaches, e.g. as in ANIMA WG, SUPA (BoF), IBNEMO, or SDN RG...
Thus, we believe some coordination among RG/WG can deliver additional value to the community.
Jointly with the SDN RG, we would like to impulse an activity on IBN to discuss the objectives, scope and kick start this effort.

The items listed below can help to get things started:
    -What are the definitions of Intent/IBN? e.g. in SUPA, ANIMA, SDN, NFV, IoT spaces...
    -What are the alignment/commonalities and differences among them, and the implications from technology, standard and business perspectives?
    -What are the functionality / components of an intent based system?
    -Is an end-to-end, comprehensive intent based system feasible? Does it make sense?
    -How can different techno-specific / heterogeneous sources of intent (definitions / blocks) inter-operate, in intra- and inter-domains?
    -What are the (key) areas of research? languages, semantics/ontologies, human factors/HNI, model-driven-development, policy refinement...
    -What are examples of application: e.g. technology specific or generic: e.g. in NFV, SDN, autonomics, IoT...
    -What relationships/consistency among those applications? i.e. towards a comprehensive view of a "Generalized IBN"
    -List of representative use cases of IBN.
    -Practical experiences, developments, tools on IBN.

The network management community has extensive knowledge and expertise in the area (think policy based management) that can prove very useful in the foreseen investigations.
Network management is also transverse to technologies (e.g. SDN, NFV, autonomics...), providing a different perspective to the problem at hand.

---
The first outcome of this activity will be discussed in the joint meeting between SDN, NFV and NM research groups to be held at IETF96/Berlin (TBC).

This topic is part of the NMRG meeting at NOMS 2016 (http://noms2016.ieee-noms.org, 25-29 April 2016, Istanbul).

Other events are in the pipe, so stay tuned!


Best regards,
Lisandro and Laurent (NMRG chairs), together with Kohei and Dan (SDN RG chairs).
---


--

Laurent Ciavaglia

Senior Research Manager

Bell Labs, Nokia

 

+33 160 402 636

Route de Villejust | 91620 Nozay | France

LinkedIn: laurentciavaglia

 





--------------050503050804000302020003-- From chrism.tpc@gmail.com Wed Apr 20 05:56:13 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8525D12EECC for ; Wed, 20 Apr 2016 05:56:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 izBiuafWoRQx for ; Wed, 20 Apr 2016 05:56:11 -0700 (PDT) Received: from mail-lb0-x234.google.com (mail-lb0-x234.google.com [IPv6:2a00:1450:4010:c04::234]) (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 8F4E412EECA for ; Wed, 20 Apr 2016 05:56:10 -0700 (PDT) Received: by mail-lb0-x234.google.com with SMTP id os9so8723230lbb.2 for ; Wed, 20 Apr 2016 05:56:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=rdCAY8+02w1Mg/Q5Dp4s5Haa6AFETMPjclQEut2/KhQ=; b=q7U4Am6P7SQQOg0zJmdIe+T/0K2mx+9xDD42cAOkSG8f5clZMs/ml8tAwrIMtvU0jI adTUHYV0qn5G9u5IygW8tb8bTeHgbJO2SowNg4WvcBCqlSrFftPTwsoZeZZoMBiI/X/L XbelfWOC3Dx9Wf+Rep0soKRdqVgdvQ74t39iaWQJ+oNVk4WqwrIsqxoHc73R1hU65Z+O deKNw52/0k2aRGTozkntebKYSx696WlL5ct23iiZuU1KeYHxACaPi6P1cl0UA9DFYY42 UR5YyHeHqEPyV85haEPWodxjqbRgYDz9XIoKC9uTGpsJ3jpEtngVeggB9sLM8MUFr6OT pUnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=rdCAY8+02w1Mg/Q5Dp4s5Haa6AFETMPjclQEut2/KhQ=; b=hzViXzoia1tSoxDTkoNdmLAKGbN3p+GlDtcf6bnzKTwAonI+WwzzaUdfg9ZO9PfLbV xoxB/+lCwlGmWmEk+Xtfxcxf0bF4mfqQPQH9UmhVUtzbKZxo3AVmiUA+wuU3TlDHA/6Z hfeIJ6bCAt+yridqRLYfoKJCaWvjo+1I2soEj1DpE/FaLs3fsOvQk/JIPkxALSjQ+Ont W4pN9DW8rs0LlnHs9LNLHNbHbTTUT4YF1ehBLGyEIrJ/sYOgGoEBSWRanX/n1hwv5Btz JgyuLSjJgzBpmOKIi+QkW8n0tUeD1TdOrgIuknJAa3u8VKhvM9tW/NtQLOJldj3JixCl Yz6Q== X-Gm-Message-State: AOPr4FXrRTpdg+Whh8YDEmPijVA+UdNbiDBbOdy2lQurFlFYtR+klRcw3FoOxrXYwqHLv/YhodXf7if6uUYyDA== MIME-Version: 1.0 X-Received: by 10.112.169.105 with SMTP id ad9mr3570611lbc.135.1461156968604; Wed, 20 Apr 2016 05:56:08 -0700 (PDT) Received: by 10.114.60.113 with HTTP; Wed, 20 Apr 2016 05:56:08 -0700 (PDT) Date: Wed, 20 Apr 2016 08:56:08 -0400 Message-ID: From: Christian Makaya To: sdn@irtf.org Content-Type: multipart/alternative; boundary=001a11c38c08132abd0530ea1e1e Archived-At: Subject: [Sdn] 2016 IEEE NFV-SDN -- Call for Submissions X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 12:59:40 -0000 --001a11c38c08132abd0530ea1e1e Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ------------ Apologies for Cross-posting --------------- 2016 IEEE Conference on Network Functions Virtualization & Software Defined Networks (IEEE NFV-SDN) Palo Alto, California, USA November 7-9, 2016 More information is available at: http://www.ieee-nfvsdn.org CALL FOR PAPERS Network Functions Virtualization (NFV) and Software Defined Networks (SDN) enable rapid network and service innovation for all participants in the ecosystem. Decoupling network functions from the underlying physical infrastructure using virtualization technologies enables service innovation. SDN allows programmability of the NFV infrastructure to support the deployment of new network functions in a variety of environments including campus and enterprise networks, data centers, Internet service providers (ISPs), cloud providers, and over-the-top (OTT) application and service providers. NFV enables network capacity and functionality to be decoupled, allowing network functions to be dynamically deployed whenever they are required and wherever they can be hosted. The dramatic industry transformation implied by NFV and SDN will not only impact network computing platforms and network architecture, but will also open up new avenues of research. Further, it enables the deployment of new network functions that enable smart cities/homes/cars/businesses, green infrastructures, new types of user interfaces and cyber physical system realizations. The 2016 IEEE NFV-SDN conference focuses in addition to the latest NFV concepts and mechanisms on first operational results on studies related to virtualized networks functions (VNFs) as well as new applications of VNFs, which smartens networks and their usage. IMPORTANT DATES May 15, 2016 Paper submission deadline April 10, 2016 Workshop proposal deadline June 15, 2016 Demo/tutorial/panel/ September 7, 2016 Acceptance notification October 7 2016 Camera-ready papers TOPICS The IEEE NFV-SDN conference aims at bringing researchers all around the world together to share ideas that can impact the evolution and operation of NFV and SDN technologies. We encourage submission of innovative work on NFV and SDN. The following is a non-exhaustive list of topics: - NFV and SDN architectures, protocols, application programming interfaces, and programming languages - Design of NFV and SDN-based forwarding elements (switch/router, optical, wireless, gateway) - Control plane architectures and network operating systems in NFV and SDN - New forwarding abstractions and program-mability paradigms - NFV infrastructure architectures including hardware acceleration technologies - Hardware switches for NFV - Software switches for NFV architectures - Open vSwitch (OVS)-related research - Data and control plane conformance, in-teroperability, scalability, and performance studies - Performance evaluation, optimization, isolation, tradeoffs with NFV workloads - Operational experiences for NFVs - VNFs designed around architectures for Cloud-native microservices - Use and performance of container techniques for NFVs - Design guidelines for scalable, available, composable, and modular VNF= s - Re-architecturing the VNFs to advance interoperability and increase performance - Dynamic service function chaining - OPNFV-related research & explorations - Orchestration API - Service chaining/orchestration and traffic steering in NFV and SDN - App store management for NFV and SDN - Tools for validating network services and automated deployment and management - Applying compositional patterns for parallelism, control logic, performance, and reliability of network services - Reliability, verification, resiliency, and fault management in NFV and SDN - Autonomic management technologies in NFV and SDN - Security functions and services in NFV - Application of machine learning, big data analytics to NFV and SDN - Scalable distributed and hierarchical controller architectures - Software-based integration of computing, storage, and networking - Commercial models and implications for NFV and SDN ecosystems - Applications and usage scenarios enabled by NFV and SDN - Applications of NFV/SDN in IoT, CPS, Smart Cities - Behavior of combined NFV and SDN control plane - Operational experiences - RAN for NFV & SDN architecture options - NFV & SDN on public/private clouds DEMOS, TUTORIALS AND WORKSHOPS Call for Demos: The IEEE NFV-SDN conference also invites demonstration papers in the NFV and SDN realms addressing (but not limited to) the topics above. The demonstrations should be configured to run in a cloud environment accessible via Internet and presented from the exhibition space floor on the demonstrator=E2=80=99s laptop. Also, an author of an accepted = demo is required to register for the conference at the full or limited rate and present the demo at the IEEE NFV-SDN 2016 conference. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-demos/ Call for Tutorials: The organizing committee invites proposals for tutorials to be held prior to the main conference. Tutorials should serve one or more of the following objec-tives: introducing students and newcomers to major topics of NFV and SDN research; providing instructions on established practices and methodologies; surveying a mature area of NFV and SDN research and/or practice; motivating and explaining an NFV and SDN topic of emerging importance; introducing expert non-specialists to an NFV and SDN research area. Proposals should be submitted by electronic mail to the Tutorial Program Co-Chairs. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-tutorials/ Call for Workshop Proposals: The committee solicits proposals for one full-day or two half-day workshops to be held on Nov 7, 2016 at the Start of the main technical program. The Scope of the workshops is to complement the main conference program with forums for exchange of technical expertise, development, integration and standardization efforts on par-ticularly focused areas of interest within the frame of the NFV/SDN. Proposals from industry and academia are welcome. Proposals should be submitted by electronic mail to the Workshop Program Co-Chairs. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-workshop-proposals/ Author & Submission Guidelines: Prospective authors are invited to submit origi-nal technical papers for publication in the IEEE NFV-SDN 2016 Conference Proceedings and for presentation in the technical sessions. We solicit submission of high-quality full papers reporting original and novel research results on all above topics. Papers must be written in English, unpublished and not submitted elsewhere. Full papers must be formatted as the standard IEEE double-column conference template All final submissions should have a maximum paper length of six (6) printed pages (10-point font), including figures, without incurring additional page charges (maximum 1 additional page with over length page charge of USD100 if accepted). Papers exceeding 7 pages will not be accepted at EDAS. Submissions should be uploaded on http://edas.info/N2217= 5. To be published in the IEEE NFV-SDN 2016 Conference Proceedings and to be eligible for publication in IEEE Xplore, an author of an accepted paper is required to register for the conference at the FULL (member or non-member) rate and the paper must be presented by an author of that paper at the conference. For authors with multiple accepted papers, one FULL registration is valid for up to 3 papers. Accepted and presented papers will be published in the IEEE NFV-SDN 2016 Conference Proceedings and submitted to IEEE Xplore=C2=AE. The IEEE reserves the right to exclude a paper from distribution after the conference (including its removal from IEEE Explore) if the paper is not presented at the conference. Papers are re-viewed on the basis that they do not contain plagiarized material and have not been submitted to any other conference at the same time (double submission). These matters are taken very seriously and the IEEE Communications Society will take action against any author who engages in either practice. --001a11c38c08132abd0530ea1e1e Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
------------ Apologies for Cross-posting ---------------2016 IEEE Conference on Network Functions Virtualization & Software D= efined Networks (IEEE NFV-SDN)
Palo=C2=A0 Alto, California, USA=C2=A0=C2= =A0
November 7-9, 2016

More information is available at: http://www.ieee-nfvsdn.org

CALL = FOR PAPERS
Network Functions Virtualization (NFV) and Software Defined N= etworks (SDN) enable rapid network and service innovation for all participa= nts in the ecosystem. Decoupling network functions from the underlying phys= ical infrastructure using virtualization technologies enables service innov= ation. SDN allows programmability of the NFV infrastructure to support the = deployment of new network functions in a variety of environments including = campus and enterprise networks, data centers, Internet service providers (I= SPs), cloud providers, and over-the-top (OTT) application and service provi= ders. NFV enables network capacity and functionality to be decoupled, allow= ing network functions to be dynamically deployed whenever they are required= and wherever they can be hosted. The dramatic industry transformation impl= ied by NFV and SDN will not only impact network computing platforms and net= work architecture, but will also open up new avenues of research. Further, = it enables the deployment of new network functions that enable smart cities= /homes/cars/businesses, green infrastructures, new types of user interfaces= and cyber physical system realizations. The 2016 IEEE NFV-SDN conference f= ocuses in addition to the latest NFV concepts and mechanisms on first opera= tional results on studies related to virtualized networks functions (VNFs) = as well as new applications of VNFs, which smartens networks and their usag= e.


IMPORTANT DATES
May 15, 2016=C2=A0=C2=A0=C2=A0 =C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Paper submission deadli= ne
April 10, 2016=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Workshop proposal deadline
June 15, 2016=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 D= emo/tutorial/panel/
September 7, 2016=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 Acceptance notification
October 7 2016=C2=A0=C2=A0= =C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Camera-= ready papers


TOPICS
The IEEE NFV-SDN conference aims at bring= ing researchers all around the world together to share ideas that can impac= t the evolution and operation of NFV and SDN technologies. We encourage sub= mission of innovative work on NFV and SDN. The following is a non-exhaustiv= e list of=C2=A0 topics:
-=C2=A0=C2=A0=C2=A0 NFV and SDN architectures, p= rotocols, application programming interfaces, and programming languages
= -=C2=A0=C2=A0=C2=A0 Design of NFV and SDN-based forwarding elements (switch= /router, optical, wireless, gateway)
-=C2=A0=C2=A0=C2=A0 Control plane a= rchitectures and network operating systems in NFV and SDN
-=C2=A0=C2=A0= =C2=A0 New forwarding abstractions and program-mability paradigms
-=C2= =A0=C2=A0=C2=A0 NFV infrastructure architectures including hardware acceler= ation technologies
-=C2=A0=C2=A0=C2=A0 Hardware switches for NFV
-=C2= =A0=C2=A0=C2=A0 Software switches for NFV architectures
-=C2=A0=C2=A0=C2= =A0 Open vSwitch (OVS)-related research
-=C2=A0=C2=A0=C2=A0 Data and con= trol plane conformance, in-teroperability, scalability, and performance stu= dies
-=C2=A0=C2=A0=C2=A0 Performance evaluation, optimization, isolation= , tradeoffs with NFV workloads
-=C2=A0=C2=A0=C2=A0 Operational experienc= es for NFVs
-=C2=A0=C2=A0=C2=A0 VNFs designed around architectures for C= loud-native microservices
-=C2=A0=C2=A0=C2=A0 Use and performance of con= tainer techniques for NFVs
-=C2=A0=C2=A0=C2=A0 Design guidelines for sca= lable, available, composable, and modular VNFs
-=C2=A0=C2=A0=C2=A0 Re-ar= chitecturing the VNFs to advance interoperability and increase performance<= br>-=C2=A0=C2=A0=C2=A0 Dynamic service function chaining
-=C2=A0=C2=A0= =C2=A0 OPNFV-related research & explorations=C2=A0=C2=A0=C2=A0 -=C2=A0= =C2=A0=C2=A0 Orchestration API
-=C2=A0=C2=A0=C2=A0 Service chaining/orch= estration and traffic steering in NFV and SDN
-=C2=A0=C2=A0=C2=A0 App st= ore management for NFV and SDN
-=C2=A0=C2=A0=C2=A0 Tools for validating = network services and automated deployment and management
-=C2=A0=C2=A0= =C2=A0 Applying compositional patterns for parallelism, control logic, perf= ormance, and reliability of network services
-=C2=A0=C2=A0=C2=A0 Reliabi= lity, verification, resiliency, and fault management in NFV and SDN
-=C2= =A0=C2=A0=C2=A0 Autonomic management technologies in NFV and SDN
-=C2=A0= =C2=A0=C2=A0 Security functions and services in NFV
-=C2=A0=C2=A0=C2=A0 = Application of machine learning, big data analytics to NFV and SDN
-=C2= =A0=C2=A0=C2=A0 Scalable distributed and hierarchical controller architectu= res
-=C2=A0=C2=A0=C2=A0 Software-based integration of computing, storage= , and networking
-=C2=A0=C2=A0=C2=A0 Commercial models and implications = for NFV and SDN ecosystems
-=C2=A0=C2=A0=C2=A0 Applications and usage sc= enarios enabled by NFV and SDN
-=C2=A0=C2=A0=C2=A0 Applications of NFV/S= DN in IoT, CPS, Smart Cities
-=C2=A0=C2=A0=C2=A0 Behavior of combined NF= V and SDN control plane
-=C2=A0=C2=A0=C2=A0 Operational experiences
= -=C2=A0=C2=A0=C2=A0 RAN for NFV & SDN architecture options
-=C2=A0= =C2=A0=C2=A0 NFV & SDN=C2=A0 on public/private clouds


DEMOS,= TUTORIALS AND WORKSHOPS

Call for Demos: The IEEE NFV-SDN conference= also invites demonstration papers in the NFV and SDN realms addressing (bu= t not limited to) the topics above. The demonstrations should be configured= to run in a cloud environment accessible via Internet and presented from t= he exhibition space floor on the demonstrator=E2=80=99s laptop. Also, an au= thor of an accepted demo is required to register for the conference at the = full or limited rate and present the demo at the IEEE NFV-SDN 2016 conferen= ce. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call= -for-demos/


Call for Tutorials: The organizing committee in= vites proposals for tutorials to be held prior to the main conference.=C2= =A0 Tutorials should serve one or more of the following objec-tives: introd= ucing students and newcomers to major topics of NFV and SDN research; provi= ding instructions on established practices and methodologies; surveying a m= ature area of NFV and SDN research and/or practice; motivating and explaini= ng an NFV and SDN topic of emerging importance; introducing expert non-spec= ialists to an NFV and SDN research area. Proposals should be submitted by e= lectronic mail to the Tutorial Program Co-Chairs. For information on submis= sion, please visit http://www.ieee-nfvsdn.org/authors/call-for-tutorials/
Call for Workshop Proposals: The committee solicits proposals for one ful= l-day or two half-day workshops to be held on Nov 7, 2016 at the Start of t= he main technical program.=C2=A0 The Scope of the workshops is to complemen= t the main conference program with forums for exchange of technical experti= se, development, integration and standardization efforts on par-ticularly f= ocused areas of interest within the frame of the NFV/SDN. Proposals from in= dustry and academia are welcome. Proposals should be submitted by electroni= c mail to the Workshop Program Co-Chairs. For information on submission, pl= ease visit http://www.ieee-nfvsdn.org/authors/call-for-workshop-proposals/=


Author & Submission Guidelines: Prospective authors ar= e invited to submit origi-nal technical papers for publication in the IEEE = NFV-SDN 2016 Conference Proceedings and for presentation in the technical s= essions.=C2=A0 We solicit submission of high-quality full papers reporting = original and novel research results on all above topics.

Papers mus= t be written in English, unpublished and not submitted elsewhere. Full pape= rs must be formatted as the standard IEEE double-column conference template= All final submissions should have a maximum paper length of six (6) printe= d pages (10-point font), including figures, without incurring additional pa= ge charges (maximum 1 additional page with over length page charge of USD10= 0 if accepted). Papers exceeding 7 pages will not be accepted at EDAS.=C2= =A0 Submissions should be uploaded on h= ttp://edas.info/N22175.=C2=A0

To be published in the IEEE NFV-S= DN 2016 Conference Proceedings and to be eligible for publication in IEEE X= plore, an author of an accepted paper is required to register for the confe= rence at the FULL (member or non-member) rate and the paper must be present= ed by an author of that paper at the conference.=C2=A0 For authors with mul= tiple accepted papers, one FULL registration is valid for up to 3 papers. A= ccepted and presented papers will be published in the IEEE NFV-SDN 2016 Con= ference Proceedings and submitted to IEEE Xplore=C2=AE.

The IEEE res= erves the right to exclude a paper from distribution after the conference (= including its removal from IEEE Explore) if the paper is not presented at t= he conference. Papers are re-viewed on the basis that they do not contain p= lagiarized material and have not been submitted to any other conference at = the same time (double submission). These matters are taken very seriously a= nd the IEEE Communications Society will take action against any author who = engages in either practice.


--001a11c38c08132abd0530ea1e1e-- From nobody Wed Apr 20 06:04:01 2016 Return-Path: X-Original-To: sdn@ietfa.amsl.com Delivered-To: sdn@ietfa.amsl.com Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E8CF812D13B for ; Wed, 20 Apr 2016 06:03:59 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham 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 VK2bru0VDUjG for ; Wed, 20 Apr 2016 06:03:56 -0700 (PDT) Received: from mail-lf0-x230.google.com (mail-lf0-x230.google.com [IPv6:2a00:1450:4010:c07::230]) (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 B189F12D135 for ; Wed, 20 Apr 2016 06:03:55 -0700 (PDT) Received: by mail-lf0-x230.google.com with SMTP id c126so40459083lfb.2 for ; Wed, 20 Apr 2016 06:03:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to; bh=zhMwE3ouLeYmqoA0r5chvzQynVJzHxEuuAUem1EqbJM=; b=Sts2Yi4oVwodoutuKzsSXJSmiMoVFDPoFx+/terwI/c6FxaYWwwKUoUFwpj+mkiEqo 5koJ5Na5gZzRh47TF79AmKU9h/JA+Oc9fQYhItCQbfdT6QW24LIAkcBBAYRmkZV5YmuT R0Q9bz5y8D3nwz09YQB2R9TBGt0uzZC5cXTps+YveiQ5I7UG2gY1BVvNuoSHsKIUCH35 z8XjTsBq3AzHD4ExuHaKuFepOEFfoywelDKv2c3N/Y3n6Z0nLKMrCzu2Qdlr4EgKUR7m 5SdV2MuSJkBnPWh89fUQNToW0OrdmWZNOSXQOn/uvyXFabEhB7/VxsYdtWHBWtTwHURY gjbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to; bh=zhMwE3ouLeYmqoA0r5chvzQynVJzHxEuuAUem1EqbJM=; b=RdwfLqHvQAgBpAwvSROgrAtW2XvEbtwohq1FNSNEy3U7Ek0/1ftDnV9G0O5OeBVTVR t20snUK/RuOyYxQ47F8f747kYqQZVJ8OYjWtvUZMy5l4FqMqMY1zc5yUB08z2Djj1V8d iM2f2wzYqzeQsxWC7IWzVJmFRC+bY5CVTj43Wg4X0o/+saDdVUrU1AaIARZjlu7eJJ4n WVSKDOfmHt14bmKfxEieKPBDelsrqzeYfLf0D5Zdb5zLs1z553Qegt1y/iOFz0FUxwSD 8xO+VS6ayLmHZQF+w0h7ZHF5+hMfnhthlcLwHEi1VDufCP6V67yQJf8p6dlSLtweDANv tJrg== X-Gm-Message-State: AOPr4FV1bUArtv8WCd7A2oagLz1aUHpIVEtjvwZA5zuvN87scEznPC8MzVZ+nPwNhtDBs0zEEku4pPF1KhV0VA== MIME-Version: 1.0 X-Received: by 10.25.157.79 with SMTP id g76mr3662273lfe.41.1461157433779; Wed, 20 Apr 2016 06:03:53 -0700 (PDT) Received: by 10.114.60.113 with HTTP; Wed, 20 Apr 2016 06:03:53 -0700 (PDT) Date: Wed, 20 Apr 2016 09:03:53 -0400 Message-ID: From: Christian Makaya To: sdn@irtf.org Content-Type: multipart/alternative; boundary=001a11411dd4cd2ac70530ea392c Archived-At: Subject: [Sdn] 2016 IEEE NFV-SDN -- Call for Submissions X-BeenThere: sdn@irtf.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: List to Discuss SDN Research Group in the IRTF List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 20 Apr 2016 13:04:00 -0000 --001a11411dd4cd2ac70530ea392c Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable ------------ Apologies for Cross-posting --------------- 2016 IEEE Conference on Network Functions Virtualization & Software Defined Networks (IEEE NFV-SDN) Palo Alto, California, USA November 7-9, 2016 More information is available at: http://www.ieee-nfvsdn.org CALL FOR PAPERS Network Functions Virtualization (NFV) and Software Defined Networks (SDN) enable rapid network and service innovation for all participants in the ecosystem. Decoupling network functions from the underlying physical infrastructure using virtualization technologies enables service innovation. SDN allows programmability of the NFV infrastructure to support the deployment of new network functions in a variety of environments including campus and enterprise networks, data centers, Internet service providers (ISPs), cloud providers, and over-the-top (OTT) application and service providers. NFV enables network capacity and functionality to be decoupled, allowing network functions to be dynamically deployed whenever they are required and wherever they can be hosted. The dramatic industry transformation implied by NFV and SDN will not only impact network computing platforms and network architecture, but will also open up new avenues of research. Further, it enables the deployment of new network functions that enable smart cities/homes/cars/businesses, green infrastructures, new types of user interfaces and cyber physical system realizations. The 2016 IEEE NFV-SDN conference focuses in addition to the latest NFV concepts and mechanisms on first operational results on studies related to virtualized networks functions (VNFs) as well as new applications of VNFs, which smartens networks and their usage. IMPORTANT DATES May 15, 2016 Paper submission deadline April 10, 2016 Workshop proposal deadline June 15, 2016 Demo/tutorial/panel/ September 7, 2016 Acceptance notification October 7 2016 Camera-ready papers TOPICS The IEEE NFV-SDN conference aims at bringing researchers all around the world together to share ideas that can impact the evolution and operation of NFV and SDN technologies. We encourage submission of innovative work on NFV and SDN. The following is a non-exhaustive list of topics: - NFV and SDN architectures, protocols, application programming interfaces, and programming languages - Design of NFV and SDN-based forwarding elements (switch/router, optical, wireless, gateway) - Control plane architectures and network operating systems in NFV and SDN - New forwarding abstractions and program-mability paradigms - NFV infrastructure architectures including hardware acceleration technologies - Hardware switches for NFV - Software switches for NFV architectures - Open vSwitch (OVS)-related research - Data and control plane conformance, in-teroperability, scalability, and performance studies - Performance evaluation, optimization, isolation, tradeoffs with NFV workloads - Operational experiences for NFVs - VNFs designed around architectures for Cloud-native microservices - Use and performance of container techniques for NFVs - Design guidelines for scalable, available, composable, and modular VNF= s - Re-architecturing the VNFs to advance interoperability and increase performance - Dynamic service function chaining - OPNFV-related research & explorations - Orchestration API - Service chaining/orchestration and traffic steering in NFV and SDN - App store management for NFV and SDN - Tools for validating network services and automated deployment and management - Applying compositional patterns for parallelism, control logic, performance, and reliability of network services - Reliability, verification, resiliency, and fault management in NFV and SDN - Autonomic management technologies in NFV and SDN - Security functions and services in NFV - Application of machine learning, big data analytics to NFV and SDN - Scalable distributed and hierarchical controller architectures - Software-based integration of computing, storage, and networking - Commercial models and implications for NFV and SDN ecosystems - Applications and usage scenarios enabled by NFV and SDN - Applications of NFV/SDN in IoT, CPS, Smart Cities - Behavior of combined NFV and SDN control plane - Operational experiences - RAN for NFV & SDN architecture options - NFV & SDN on public/private clouds DEMOS, TUTORIALS AND WORKSHOPS Call for Demos: The IEEE NFV-SDN conference also invites demonstration papers in the NFV and SDN realms addressing (but not limited to) the topics above. The demonstrations should be configured to run in a cloud environment accessible via Internet and presented from the exhibition space floor on the demonstrator=E2=80=99s laptop. Also, an author of an accepted = demo is required to register for the conference at the full or limited rate and present the demo at the IEEE NFV-SDN 2016 conference. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-demos/ Call for Tutorials: The organizing committee invites proposals for tutorials to be held prior to the main conference. Tutorials should serve one or more of the following objec-tives: introducing students and newcomers to major topics of NFV and SDN research; providing instructions on established practices and methodologies; surveying a mature area of NFV and SDN research and/or practice; motivating and explaining an NFV and SDN topic of emerging importance; introducing expert non-specialists to an NFV and SDN research area. Proposals should be submitted by electronic mail to the Tutorial Program Co-Chairs. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-tutorials/ Call for Workshop Proposals: The committee solicits proposals for one full-day or two half-day workshops to be held on Nov 7, 2016 at the Start of the main technical program. The Scope of the workshops is to complement the main conference program with forums for exchange of technical expertise, development, integration and standardization efforts on par-ticularly focused areas of interest within the frame of the NFV/SDN. Proposals from industry and academia are welcome. Proposals should be submitted by electronic mail to the Workshop Program Co-Chairs. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call-for-workshop-proposals/ Author & Submission Guidelines: Prospective authors are invited to submit origi-nal technical papers for publication in the IEEE NFV-SDN 2016 Conference Proceedings and for presentation in the technical sessions. We solicit submission of high-quality full papers reporting original and novel research results on all above topics. Papers must be written in English, unpublished and not submitted elsewhere. Full papers must be formatted as the standard IEEE double-column conference template All final submissions should have a maximum paper length of six (6) printed pages (10-point font), including figures, without incurring additional page charges (maximum 1 additional page with over length page charge of USD100 if accepted). Papers exceeding 7 pages will not be accepted at EDAS. Submissions should be uploaded on http://edas.info/N2217= 5. To be published in the IEEE NFV-SDN 2016 Conference Proceedings and to be eligible for publication in IEEE Xplore, an author of an accepted paper is required to register for the conference at the FULL (member or non-member) rate and the paper must be presented by an author of that paper at the conference. For authors with multiple accepted papers, one FULL registration is valid for up to 3 papers. Accepted and presented papers will be published in the IEEE NFV-SDN 2016 Conference Proceedings and submitted to IEEE Xplore=C2=AE. The IEEE reserves the right to exclude a paper from distribution after the conference (including its removal from IEEE Explore) if the paper is not presented at the conference. Papers are re-viewed on the basis that they do not contain plagiarized material and have not been submitted to any other conference at the same time (double submission). These matters are taken very seriously and the IEEE Communications Society will take action against any author who engages in either practice. --001a11411dd4cd2ac70530ea392c Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
------------ Apologies for Cross-posting ---------------2016 IEEE Conference on Network Functions Virtualization & Software D= efined Networks (IEEE NFV-SDN)
Palo=C2=A0 Alto, California, USA=C2=A0=C2= =A0
November 7-9, 2016

More information is available at: http://www.ieee-nfvsdn.org

CALL = FOR PAPERS
Network Functions Virtualization (NFV) and Software Defined N= etworks (SDN) enable rapid network and service innovation for all participa= nts in the ecosystem. Decoupling network functions from the underlying phys= ical infrastructure using virtualization technologies enables service innov= ation. SDN allows programmability of the NFV infrastructure to support the = deployment of new network functions in a variety of environments including = campus and enterprise networks, data centers, Internet service providers (I= SPs), cloud providers, and over-the-top (OTT) application and service provi= ders. NFV enables network capacity and functionality to be decoupled, allow= ing network functions to be dynamically deployed whenever they are required= and wherever they can be hosted. The dramatic industry transformation impl= ied by NFV and SDN will not only impact network computing platforms and net= work architecture, but will also open up new avenues of research. Further, = it enables the deployment of new network functions that enable smart cities= /homes/cars/businesses, green infrastructures, new types of user interfaces= and cyber physical system realizations. The 2016 IEEE NFV-SDN conference f= ocuses in addition to the latest NFV concepts and mechanisms on first opera= tional results on studies related to virtualized networks functions (VNFs) = as well as new applications of VNFs, which smartens networks and their usag= e.


IMPORTANT DATES
May 15, 2016=C2=A0=C2=A0=C2=A0 =C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Paper submission deadli= ne
April 10, 2016=C2=A0=C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0=C2=A0=C2=A0 Workshop proposal deadline
June 15, 2016=C2=A0= =C2=A0=C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 D= emo/tutorial/panel/
September 7, 2016=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2= =A0=C2=A0=C2=A0=C2=A0 Acceptance notification
October 7 2016=C2=A0=C2=A0= =C2=A0 =C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Camera-= ready papers


TOPICS
The IEEE NFV-SDN conference aims at bring= ing researchers all around the world together to share ideas that can impac= t the evolution and operation of NFV and SDN technologies. We encourage sub= mission of innovative work on NFV and SDN. The following is a non-exhaustiv= e list of=C2=A0 topics:
-=C2=A0=C2=A0=C2=A0 NFV and SDN architectures, p= rotocols, application programming interfaces, and programming languages
= -=C2=A0=C2=A0=C2=A0 Design of NFV and SDN-based forwarding elements (switch= /router, optical, wireless, gateway)
-=C2=A0=C2=A0=C2=A0 Control plane a= rchitectures and network operating systems in NFV and SDN
-=C2=A0=C2=A0= =C2=A0 New forwarding abstractions and program-mability paradigms
-=C2= =A0=C2=A0=C2=A0 NFV infrastructure architectures including hardware acceler= ation technologies
-=C2=A0=C2=A0=C2=A0 Hardware switches for NFV
-=C2= =A0=C2=A0=C2=A0 Software switches for NFV architectures
-=C2=A0=C2=A0=C2= =A0 Open vSwitch (OVS)-related research
-=C2=A0=C2=A0=C2=A0 Data and con= trol plane conformance, in-teroperability, scalability, and performance stu= dies
-=C2=A0=C2=A0=C2=A0 Performance evaluation, optimization, isolation= , tradeoffs with NFV workloads
-=C2=A0=C2=A0=C2=A0 Operational experienc= es for NFVs
-=C2=A0=C2=A0=C2=A0 VNFs designed around architectures for C= loud-native microservices
-=C2=A0=C2=A0=C2=A0 Use and performance of con= tainer techniques for NFVs
-=C2=A0=C2=A0=C2=A0 Design guidelines for sca= lable, available, composable, and modular VNFs
-=C2=A0=C2=A0=C2=A0 Re-ar= chitecturing the VNFs to advance interoperability and increase performance<= br>-=C2=A0=C2=A0=C2=A0 Dynamic service function chaining
-=C2=A0=C2=A0= =C2=A0 OPNFV-related research & explorations=C2=A0=C2=A0=C2=A0 -=C2=A0= =C2=A0=C2=A0 Orchestration API
-=C2=A0=C2=A0=C2=A0 Service chaining/orch= estration and traffic steering in NFV and SDN
-=C2=A0=C2=A0=C2=A0 App st= ore management for NFV and SDN
-=C2=A0=C2=A0=C2=A0 Tools for validating = network services and automated deployment and management
-=C2=A0=C2=A0= =C2=A0 Applying compositional patterns for parallelism, control logic, perf= ormance, and reliability of network services
-=C2=A0=C2=A0=C2=A0 Reliabi= lity, verification, resiliency, and fault management in NFV and SDN
-=C2= =A0=C2=A0=C2=A0 Autonomic management technologies in NFV and SDN
-=C2=A0= =C2=A0=C2=A0 Security functions and services in NFV
-=C2=A0=C2=A0=C2=A0 = Application of machine learning, big data analytics to NFV and SDN
-=C2= =A0=C2=A0=C2=A0 Scalable distributed and hierarchical controller architectu= res
-=C2=A0=C2=A0=C2=A0 Software-based integration of computing, storage= , and networking
-=C2=A0=C2=A0=C2=A0 Commercial models and implications = for NFV and SDN ecosystems
-=C2=A0=C2=A0=C2=A0 Applications and usage sc= enarios enabled by NFV and SDN
-=C2=A0=C2=A0=C2=A0 Applications of NFV/S= DN in IoT, CPS, Smart Cities
-=C2=A0=C2=A0=C2=A0 Behavior of combined NF= V and SDN control plane
-=C2=A0=C2=A0=C2=A0 Operational experiences
= -=C2=A0=C2=A0=C2=A0 RAN for NFV & SDN architecture options
-=C2=A0= =C2=A0=C2=A0 NFV & SDN=C2=A0 on public/private clouds


DEMOS,= TUTORIALS AND WORKSHOPS

Call for Demos: The IEEE NFV-SDN conference= also invites demonstration papers in the NFV and SDN realms addressing (bu= t not limited to) the topics above. The demonstrations should be configured= to run in a cloud environment accessible via Internet and presented from t= he exhibition space floor on the demonstrator=E2=80=99s laptop. Also, an au= thor of an accepted demo is required to register for the conference at the = full or limited rate and present the demo at the IEEE NFV-SDN 2016 conferen= ce. For information on submission, please visit http://www.ieee-nfvsdn.org/authors/call= -for-demos/


Call for Tutorials: The organizing committee in= vites proposals for tutorials to be held prior to the main conference.=C2= =A0 Tutorials should serve one or more of the following objec-tives: introd= ucing students and newcomers to major topics of NFV and SDN research; provi= ding instructions on established practices and methodologies; surveying a m= ature area of NFV and SDN research and/or practice; motivating and explaini= ng an NFV and SDN topic of emerging importance; introducing expert non-spec= ialists to an NFV and SDN research area. Proposals should be submitted by e= lectronic mail to the Tutorial Program Co-Chairs. For information on submis= sion, please visit http://www.ieee-nfvsdn.org/authors/call-for-tutorials/
Call for Workshop Proposals: The committee solicits proposals for one ful= l-day or two half-day workshops to be held on Nov 7, 2016 at the Start of t= he main technical program.=C2=A0 The Scope of the workshops is to complemen= t the main conference program with forums for exchange of technical experti= se, development, integration and standardization efforts on par-ticularly f= ocused areas of interest within the frame of the NFV/SDN. Proposals from in= dustry and academia are welcome. Proposals should be submitted by electroni= c mail to the Workshop Program Co-Chairs. For information on submission, pl= ease visit http://www.ieee-nfvsdn.org/authors/call-for-workshop-proposals/=


Author & Submission Guidelines: Prospective authors ar= e invited to submit origi-nal technical papers for publication in the IEEE = NFV-SDN 2016 Conference Proceedings and for presentation in the technical s= essions.=C2=A0 We solicit submission of high-quality full papers reporting = original and novel research results on all above topics.

Papers mus= t be written in English, unpublished and not submitted elsewhere. Full pape= rs must be formatted as the standard IEEE double-column conference template= All final submissions should have a maximum paper length of six (6) printe= d pages (10-point font), including figures, without incurring additional pa= ge charges (maximum 1 additional page with over length page charge of USD10= 0 if accepted). Papers exceeding 7 pages will not be accepted at EDAS.=C2= =A0 Submissions should be uploaded on h= ttp://edas.info/N22175.=C2=A0

To be published in the IEEE NFV-S= DN 2016 Conference Proceedings and to be eligible for publication in IEEE X= plore, an author of an accepted paper is required to register for the confe= rence at the FULL (member or non-member) rate and the paper must be present= ed by an author of that paper at the conference.=C2=A0 For authors with mul= tiple accepted papers, one FULL registration is valid for up to 3 papers. A= ccepted and presented papers will be published in the IEEE NFV-SDN 2016 Con= ference Proceedings and submitted to IEEE Xplore=C2=AE.

The IEEE res= erves the right to exclude a paper from distribution after the conference (= including its removal from IEEE Explore) if the paper is not presented at t= he conference. Papers are re-viewed on the basis that they do not contain p= lagiarized material and have not been submitted to any other conference at = the same time (double submission). These matters are taken very seriously a= nd the IEEE Communications Society will take action against any author who = engages in either practice.


--001a11411dd4cd2ac70530ea392c--