Re: [Nfvrg] New Version Notification for draft-natarajan-nfvrg-containers-for-nfv-03.txt

<Ramki_Krishnan@Dell.com> Fri, 05 August 2016 09:46 UTC

Return-Path: <Ramki_Krishnan@dell.com>
X-Original-To: nfvrg@ietfa.amsl.com
Delivered-To: nfvrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D97812D16F for <nfvrg@ietfa.amsl.com>; Fri, 5 Aug 2016 02:46:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.021
X-Spam-Level:
X-Spam-Status: No, score=-2.021 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); domainkeys=fail (1024-bit key) reason="fail (message has been altered)" header.from=Ramki_Krishnan@Dell.com header.d=dell.com; dkim=pass (1024-bit key) header.d=dell.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 hYlKcPYXf3pJ for <nfvrg@ietfa.amsl.com>; Fri, 5 Aug 2016 02:46:14 -0700 (PDT)
Received: from esa1.dell-outbound.iphmx.com (esa1.dell-outbound.iphmx.com [68.232.153.90]) (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 93C4812D0FF for <nfvrg@irtf.org>; Fri, 5 Aug 2016 02:46:14 -0700 (PDT)
DomainKey-Signature: s=smtpout; d=dell.com; c=simple; q=dns; h=Received:X-LoopCount0:X-IronPort-AV:From:To:CC:Subject: Thread-Topic:Thread-Index:Date:Message-ID:References: In-Reply-To:Accept-Language:Content-Language: X-MS-Has-Attach:X-MS-TNEF-Correlator: x-ms-exchange-transport-fromentityheader:x-originating-ip: Content-Type:Content-Transfer-Encoding:MIME-Version: Return-Path; b=XybFpM4D0SAtIu1VOBHOopqs/Yidzevn4Qfs9rcOsgsm2t55J9/xeGuE vX2J1xsp6K5yKzlyzx1XDLxBrGMxm8yiCiUV4bUF7vSwLiyF/dQiGvXsP /IzaRYe3RQTD4j6W02hHNfhDTWj+TUcBt4zjanFMSedX/Nxfa+dwWApw/ c=;
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=dell.com; i=@dell.com; q=dns/txt; s=smtpout; t=1470390374; x=1501926374; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=6FwAZ1q3aFEX0z4b6qy4yo8SOuPttO2hc9sNJld5KMU=; b=KbYz/i6aZd2nLarQFvSlSgMpovtm53klqbBIoT6Orloh/dSJ4Uo8buku BT1mK1iWp0FhCEJjLij8nLwsNpIxNA6zlV3i/0eeqKEl5YNtukhkWQt3C 3nql0hxIsdfP44RG20knXes5J5ijgj5wBX9On8VbFMhqq2w2g+Ckz3tD8 Y=;
Received: from ausxippc101.us.dell.com ([143.166.85.207]) by esa1.dell-outbound.iphmx.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 05 Aug 2016 14:46:12 +0500
X-LoopCount0: from 10.175.216.249
X-IronPort-AV: E=Sophos;i="5.28,473,1464670800"; d="scan'208";a="840858283"
From: Ramki_Krishnan@Dell.com
To: r.cziva.1@research.gla.ac.uk
Thread-Topic: [Nfvrg] New Version Notification for draft-natarajan-nfvrg-containers-for-nfv-03.txt
Thread-Index: AQHR2RuKMsALkaIDWUCaP4iVMSdYPaAOhPvQgBA/UYCAG4WB8A==
Date: Fri, 05 Aug 2016 09:46:11 +0000
Message-ID: <ad09f85e30ec433ea1c7f3aca4579a1c@ausx13mpc116.AMER.DELL.COM>
References: <20160708132045.32127.82910.idtracker@ietfa.amsl.com> <0d64a0b062b649f887fc1b9d53a37dfc@ausx13mpc116.AMER.DELL.COM> <8747774F-8782-4420-8C76-39B4B304BADC@research.gla.ac.uk>
In-Reply-To: <8747774F-8782-4420-8C76-39B4B304BADC@research.gla.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.133.28.241]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/nfvrg/ieScC0rbAbEAzqbPvxKakvjo2cU>
Cc: nfvrg@irtf.org
Subject: Re: [Nfvrg] New Version Notification for draft-natarajan-nfvrg-containers-for-nfv-03.txt
X-BeenThere: nfvrg@irtf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "Network Function Virtualization Research Group \(NFVRG\) discussion list" <nfvrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/nfvrg/>
List-Post: <mailto:nfvrg@irtf.org>
List-Help: <mailto:nfvrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/nfvrg>, <mailto:nfvrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Fri, 05 Aug 2016 09:46:17 -0000

Many thanks Richard for the comments. We will incorporate these in the next revision of the draft.

Thanks,
Ramki

-----Original Message-----
From: Richard Cziva [mailto:r.cziva.1@research.gla.ac.uk] 
Sent: Monday, July 18, 2016 9:28 AM
To: Krishnan, Ramki <Ramki_Krishnan@Dell.com>
Cc: nfvrg@irtf.org
Subject: Re: [Nfvrg] New Version Notification for draft-natarajan-nfvrg-containers-for-nfv-03.txt

Hello Ramki (and all),

Having read this draft on lightweight virtualisation for NFV and listening to your talk today morning at IETF 96, I would like to comment and discuss a few new ideas.

Misunderstanding:

In “3.2. Continuity, Elasticity and Portability”,  the first paragraph ends with this sentence: “Some of the requirements that need consideration are:”. Do you mean “Some of the _challenges _that need consideration are:”?

Suggestion for addition:

In “3.1.1. Challenges”, the importance of NF chaining could be described. Similarly, in “4. Benchmarking Experiments” the chaining performance could also be measured and compared between different virtualisation methods. Just as an example, in [ClickOS] the authors showed that the throughput drops significantly from around 20Gbit/s to around 4 Gbit/s using 9 chained wire NFs. However in [GNF], the authors measured that by using containers (that only perform forwarding of packets) the throughput dropped from around 30 Gbit/s to 4 Gbit/s when using ~55 chained containers. 

I believe it is also important to emphasise that containers can be used on hosts / devices that lack of virtualization support or have limited resources (such as network edge devices [GNF-EDGE], capillary IoT gateways [CAPILLARY], standard VMs in public clouds [GNFC], etc). This could be explicitly mentioned in favour of containers at “3.2. Continuity, Elasticity and Portability”, as these NFV host devices will likely to emerge in future Internet architectures..

Considerations on energy efficiency: as by using containers we do not copy packets from kernel space, we save a lot of CPU work that translates to significant energy savings. This might be interesting to measure with the same setup.

References:

[CAPILLARY] Novo, Oscar, et al. "Capillary networks-bridging the cellular and IoT worlds." Internet of Things (WF-IoT), 2015 IEEE 2nd World Forum on. IEEE, 2015.

[GNF] Cziva, Richard, et al. "Container-based network function virtualization for software-defined networks." 2015 IEEE Symposium on Computers and Communication (ISCC). IEEE, 2015. 

[GNFC] Cziva, Richard, Simon Jouet, and Dimitrios P. Pezaros. "GNFC: Towards network function cloudification." Network Function Virtualization and Software Defined Network (NFV-SDN), 2015 IEEE Conference on. IEEE, 2015. 

[GNF-EDGE]  Cziva, Richard, Simon Jouet, and Dimitrios P. Pezaros. “Roaming edge vNFs using Glasgow Network Functions.” ACM SIGCOMM, 2016. (URL to the paper: http://richard.systems/research/pdf/ACM_SIGCOMM_GNF.pdf (before publication))

Thank you for reading this.

Kind regards,
Richard Cziva

—
Richard Cziva
PhD student
Networked Systems Research Laboratory
University of Glasgow
https://netlab.dcs.gla.ac.uk


> On 8 Jul 2016, at 15:23, Ramki_Krishnan@Dell.com wrote:
> 
> The latest draft discusses the applicability of multiple light-weight virtualization technologies, beyond containers, for NFV.
> 
> Looking forward to your comments.
> 
> Thanks,
> Ramki
> 
> -----Original Message-----
> From: internet-drafts@ietf.org [mailto:internet-drafts@ietf.org] 
> Sent: Friday, July 08, 2016 6:21 AM
> To: natarajan.sriram@gmail.com; Krishnan, Ramki <Ramki_Krishnan@Dell.com>; Ashay Chaudhary <the.ashay@gmail.com>; Dilip Krishnaswamy <dilikris@in.ibm.com>; Peter Willis <peter.j.willis@bt.com>; Felipe Huici <felipe.huici@neclab.eu>; Sriram Natarajan <natarajan.sriram@gmail.com>; Anoop Ghanwani <anoop@alumni.duke.edu>; Krishnan, Ramki <Ramki_Krishnan@Dell.com>
> Subject: New Version Notification for draft-natarajan-nfvrg-containers-for-nfv-03.txt
> 
> 
> A new version of I-D, draft-natarajan-nfvrg-containers-for-nfv-03.txt
> has been successfully submitted by ram krishnan and posted to the IETF repository.
> 
> Name:		draft-natarajan-nfvrg-containers-for-nfv
> Revision:	03
> Title:		An Analysis of Lightweight Virtualization Technologies for NFV
> Document date:	2016-07-08
> Group:		Individual Submission
> Pages:		16
> URL:            https://www.ietf.org/internet-drafts/draft-natarajan-nfvrg-containers-for-nfv-03.txt
> Status:         https://datatracker.ietf.org/doc/draft-natarajan-nfvrg-containers-for-nfv/
> Htmlized:       https://tools.ietf.org/html/draft-natarajan-nfvrg-containers-for-nfv-03
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-natarajan-nfvrg-containers-for-nfv-03
> 
> Abstract:
>   Traditionally, NFV platforms were limited to using standard
>   virtualization technologies (e.g., Xen, KVM, VMWare, Hyper-V, etc.)
>   running guests based on general-purpose operating systems such as
>   Windows, Linux or FreeBSD. More recently, a number of light-weight
>   virtualization technologies including containers, unikernels
>   (specialized VMs) and minimalistic distributions of general-purpose
>   OSes have widened the spectrum of possibilities when constructing an
>   NFV platform. This draft describes the challenges in building such a
>   platform and discusses to what extent these technologies, as well as
>   traditional VMs, are able to address them.
> 
> 
> 
> 
> 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
> 
> _______________________________________________
> Nfvrg mailing list
> Nfvrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nfvrg