Re: [nvrg-bof] What is Network Virtualization?

["Mosharaf Chowdhury" <mosharafkabir at gmail.com>]

Thanks Martin for bringing up this matter. I had the following definition for network virtualization in my mind for quite a while. To my understanding most of the aspects are covered. I was looking for a one-liner, but now it seems a bit too long for one line :)
 

> Network virtualization is a networking environment that allows multiple
> service providers to dynamically compose multiple heterogeneous virtual
> networks that co-exist together in isolation from each other, and to
> deploy customized end-to-end services on-the-fly as well as manage them
> on those virtual networks for the end-users by effectively sharing and
> utilizing underlying network resources leased from multiple
> infrastructure providers.

I
have underlined the main points in the definition, and some of them
needs slight tweaking. But thats what a discussion is for, no?

Looking forward to everyone's feedback.

--
Mosharaf K Chowdhury
Graduate Student
David R. Cheriton School of Computer Science
University of Waterloo
http://www.mosharaf.com/

On Tue, Jun 17, 2008 at 8:15 AM, Martin Stiemerling <Stiemerling at nw.neclab.eu> wrote:

Hi all,

It has been quite silent on the NVRG list for a while. Sorry for that.

I have been stepping back a bit and considered what network virtualization actually might be.

So is there the first attempt to get some discussions started.

Apparently there are different camps in the area of network virtualization (at least from my recent experience):
a) network virtualization in test beds (GENI, parts of 4WARD, Akari, etc)
b) network virtualization for the Internet (parts of 4WARD, my own idea, etc)
c) existing parts, for instance, l*vpn in the IETF and virtual router support in existing devices.

For each of the above, different meanings of what network virtualization is, might apply. The least common dominator between all of them is, that they want to reuse an existing resouce (e.g., host, router, link, switch, virtual network) for multiple "usages". For a) the usage is running multiple experiements on the same infrastructure while b) envisions running multiple Internet-technologies on the same global infrastructure. c) is, at least to my understanding, not aiming at a complete set of infrastructure, but targeting specific virtualization needs (e.g., VLAN on ethernet).

Ok, I could keep on writing here, but I would like to hear other people's opinions first.

Cheers,

 Martin

Any thoughts?

Regards,

 Martin

stiemerling at nw.neclab.eu

NEC Laboratories Europe - Network Research Division
NEC Europe Limited | Registered Office: NEC House, 1 Victoria Road, London W3 6BL | Registered in England 2832014