NVRG Charter Revision
Joe Touch, USC/ISI
3/10/2016 6:44 PM
1
Draft charter 5/22/09
 Recent developments in networking are
aiming at better utilizing infrastructure in
terms of reusing a single physical or
logical resource for multiple other network
instances, or to aggregate multiple these
resources to obtain more "functionality".
These resource can be network
components, such as, for example,
routers, switches or hosts, and also
services, such as, for example, name
3/10/2016 6:44 PM
2
Para 2
 Important properties of Virtual Networks
are i) the level of participation of each
resource and ii) the clear separation of
any virtual network to all others. Each
resource can be sliced so that it can be
part of multiple Virtual Networks, but on
the other hand does virtualization
guarentee the clear separation of each
network, so that actions in one network
do not affect the operation of any other
3/10/2016 6:44 PM
3
Para 3
 However, in the network community,
Virtual Networks is a very broad term,
ranging from running multiple wave
lengths over a fiber, MPLS, virtual routers,
to overlay systems. This leads to
deployment of single technologies in parts
of the Internet or other IP-based
networks, but lacks a common
understanding of what virtualized
networks is causing to IP-based networks,
3/10/2016 6:44 PM
4
Para 4
 The Virtual Networks Research Group
(VNRG) provides a forum for interchange
of ideas among a group of network
researchers with an interest in network
virtualization in the context of the Interent
and also beyond the current Internet.
3/10/2016 6:44 PM
5
Para 5
 The RG works on a set of principles of
virtual networks that a single physical
resource can be re-used by multiple
entities with a clear separation between
the actions taken by the single entities.
Virtualization delivers an abstraction to
the user (i.e., not necessarily a human but
a service or whatever) referring to the
decoupling from the physical resource,
i.e., the abstraction is not bound to a
3/10/2016 6:44 PM
6
Charter Tasks
 The group will address the following research
challenges:
 Consider a whole system for virtualized networks and
not only single components or a limited set of
components
 Identifying architectural challenges resulting from
virtual networks
 Recursive network management of virtual networks
 Emerging technological and implementation issues.
3/10/2016 6:44 PM
7
Contact Info.
 Web site: http://user.informatik.unigoettingen.de/~stiemer/nvrg/
 Mailing list: Open mailing list to anybody,
just needs signing up with the list list's
address: nvrg@listserv.gwdg.de signing
up:
https://listserv.gwdg.de/mailman/listinfo/
nvrg
3/10/2016 6:44 PM
8
Items from mailing list
 Add circuit/link# (Kobayashi)
 Too fuzzy; focus on interop. control of testbeds+ (Kempf)
 Enable foreign resources, interconnecting VNs+*, questions 2nd half
Para 4 (Botero & Hesselbach)
 Prob. Statement*# and requirements# needed, more research
points needed* (Papadimitriou)
 (+Görg)
 Document current approaches (*Manner)
 Industry vs. testbed differences, vendor input, slice isolation,
repeatability, visibility (Falk)
 Separate net virt. from OS virt., no repeatability or visibility,
resource mgt. that focuses on net side, skip term ‘slice’, add other
testbeds [CoreLab, AKARI], skip testbed unification (#Touch)
3/10/2016 6:44 PM
9
Steps - Touch
 Steps 1:
 define a common virtual network framework
(what this BOF is for)
 determine how providers can offer VNFs as a
service
 determine how to provision a VNF across
providers
 integrate VNFs with slice reservation systems
3/10/2016 6:44 PM
10
Steps - Bless
 identify the virtual network resources that need
to be controlled and managed, derive some
requirements for them
 work on a network virtualization framework
(identifying the different roles/actors and their
interaction).
 identify control interfaces as well as
requirements for interoperability, especially in
the background of creating and running virtual
networks across provider domains.
3/10/2016 6:44 PM
11