Re: [vnrg] way forward on VNRG definitions

[Sangjin Jeong <[e-mail]>]

This is the fourth trial to send a response message because I got an error
when sending the previous trials and the message was not archived in the vnrg
mail archive.

I apologize if you have received multiple copies of this mail.

-----------------------------------
Dear Joe,

I hope it is not too late.

On Wed, Jun 9, 2010 at 1:57 AM, Joe Touch <[e-mail]> wrote:
> Hi, all,
>
> (speaking as co-chair)
>
> One of the challenges with starting with full text ("prose") is a tendency
> to
> edit the text, to focus on what to change, rather than on either what's
> missing,
> or shifts in perspective that would require substantial revision.
>
> To avoid that, Martin and I propose that we begin by each providing
> definitions
> and perspectives, rather than all try to wordsmith any single suggestion.
>
> As a starting point, we would like to have everyone on the list answer the
> following questions. We would prefer short text rather than full paragraphs
> extracted from any I-D or other document.
>
> Please DO NOT merely edit the posts of others. Once we see where people
> stand in
> their own voice, we can decide how best to move forward.
>
> Please send your responses by Jun 30 if possible.
>
> Joe (as VNRG co-chair)
>
> -----------------------------------------------------
>
> Starting questions:
>
> 1. how do you define VNs?

A VN is a logical partition of a (physical/logical) network and its
capability is the same as or subset of the network. Also, the VN may expand
its capability by aggregating the capabilities of multiple networks. From the
user's point of view, the VN can be seen as a non-virtualized network.

>
>         1.a. what are the key components?

The key components of VNs include traditional network elements, such as hosts,
routers, links, etc. In addition to them, methods for creating and managing
the VNs are also included.

>
>         1.b. what is the relationship between these components?

The VN management methods create logical partitions in the components and
connect those partitions in order to construct a VN. The VN can be
connected with non-virtualized components.

>
>         1.c. what is the characteristic behavior/capability of the
>         resulting system?

Basically, users can see the VN as a non-virtualized dedicated network, so
they can perform any actions such as deploy new services, network
architectures, etc. as if they own the dedicated network.

>
> 2. what are VNs used for?

VNs can be used for the same purposes as non-virtualized networks without
interfering other VNs' operation while sharing the key components among VNs.
Therefore, the coexistence of multiple VNs is possible.

>
> 3. what are they key challenges?
>
> for each challenge:
>         - define the challenge
>         - explain why it is hard
>         - provide some references to those working on solutions

- Performance: virtualization layer would be necessary for creating and
managing the VNs, so the performance of the VNs is not as good as the
non-virtualized network. So, how to reduce the performance degradation is a
challenge.

- Scalability: how many VNs can be simultaneously exist? how many key
components can be connected?

- Isolation: multiple VNs coexist over the key components, so isolation among
the VNs is the challenge. The isolation includes various aspects such as
security isolation, performance isolation, etc.

- Flexibility: after creating a VN based on user's requirements, the
requirements can be changed. In that case, it will be necessary to modify the
capability of the VN. The update of VN's capability may be done dynamically
and without interrupting the operation of the current VN.

- Management: how to provide independent management functions for each
VNs

Regards,
Sangjin