Re: [vnrg] Some definitions and way forward

"Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com> Wed, 03 August 2011 22:50 UTC

Return-Path: <dimitri.papadimitriou@alcatel-lucent.com>
X-Original-To: vnrg@ietfa.amsl.com
Delivered-To: vnrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9FF5F11E809B for <vnrg@ietfa.amsl.com>; Wed, 3 Aug 2011 15:50:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.249
X-Spam-Level:
X-Spam-Status: No, score=-5.249 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, HELO_EQ_FR=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vEYVb8GAR0An for <vnrg@ietfa.amsl.com>; Wed, 3 Aug 2011 15:50:32 -0700 (PDT)
Received: from smail3.alcatel.fr (smail3.alcatel.fr [64.208.49.56]) by ietfa.amsl.com (Postfix) with ESMTP id 7749721F8781 for <vnrg@irtf.org>; Wed, 3 Aug 2011 15:50:32 -0700 (PDT)
Received: from FRMRSSXCHHUB03.dc-m.alcatel-lucent.com (FRMRSSXCHHUB03.dc-m.alcatel-lucent.com [135.120.45.63]) by smail3.alcatel.fr (8.14.3/8.14.3/ICT) with ESMTP id p73MogDa004909 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NOT); Thu, 4 Aug 2011 00:50:42 +0200
Received: from FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com ([135.120.45.39]) by FRMRSSXCHHUB03.dc-m.alcatel-lucent.com ([135.120.45.63]) with mapi; Thu, 4 Aug 2011 00:50:42 +0200
From: "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>
To: Roland Bless <roland.bless@kit.edu>
Date: Thu, 4 Aug 2011 00:50:41 +0200
Thread-Topic: [vnrg] Some definitions and way forward
Thread-Index: AcxSFxOmkWOETIEKQ6OG68O3d+bc4QAAOYOA
Message-ID: <EFDB2B5417263843B5077E12666D8C10187C6490@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
References: <4E3936FF.1090006@kit.edu> <EFDB2B5417263843B5077E12666D8C10187C646B@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <4E39A744.8010508@kit.edu>
In-Reply-To: <4E39A744.8010508@kit.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Scanned-By: MIMEDefang 2.64 on 155.132.188.83
Cc: "vnrg@irtf.org" <vnrg@irtf.org>
Subject: Re: [vnrg] Some definitions and way forward
X-BeenThere: vnrg@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Virtual Networks Research Group \(VNRG\) discussion list" <vnrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/vnrg>, <mailto:vnrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/vnrg>
List-Post: <mailto:vnrg@irtf.org>
List-Help: <mailto:vnrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/vnrg>, <mailto:vnrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Aug 2011 22:50:33 -0000

Hi Roland, 

> -----Original Message-----
> From: Roland Bless [mailto:roland.bless@kit.edu] 
> Sent: Wednesday, August 03, 2011 9:54 PM
> To: Papadimitriou, Dimitri (Dimitri)
> Cc: vnrg@irtf.org
> Subject: Re: [vnrg] Some definitions and way forward
> 
> Hi Dimitri,
> 
> On 03.08.2011 18:07, Papadimitriou, Dimitri (Dimitri) wrote:
> 
> > These definitions stems from the view that physical resource owner
> > provides virtual resources of the same kind (delimits the type of
> > virtual resources it can deliver). My understanding from the scope
> > given in the Maastricht meeting was:
> 
> Not clear how you infer this view, since I don't see this kind of
> restriction in my text.

For instance: "The Infrastructure Provider (InP) is responsible for maintaining physical networking resources, such as routers, links, wireless infrastructure, etc., and enabling the virtualization of these resources. "

Hence, the question why only infrastructure providers are assumed to own physical resources that can host virtual resources composing a virtual network ? The question also can be asked in more general terms (independently of the ownership): why only physical networking resources would be capable to host virtual resources ?

> > - virtual resources can be hosted on physical resources of different
> > type i.e. virtual nodes/links don't have to be instantiated from
> > physical nodes/links; for instance, a virtual network can comprise
> > virtual nodes that are bringing together/aggregating resources from
> > multiple physical nodes AND a set of virtual nodes that are emulated
> > on a single physical machine.
> 
> Thanks for pointing this out, but the given definitions
> don't exclude that. 

The definition provided are only explicit about aggregation and partition at the substrate-level (cf. "Substrate resources can either be partitioned or aggregated in order to provide a virtual resource.") whereas allowing to run N virtual resources on a given partition of physical resources should also be considered.

A simple example: one can run today a couple of virtual routers on a single partition of a server (hosting multiple partitions) and emulate communication between these partitions, thus create a virtual network within the context of single physical resource. 

You seem to assume this is not excluded from the definitions you provided so please explain where this is the case ? 

> How you map virtual nodes and virtual
> links onto the substrate resources may vary a lot.

Indeed but definitions do not have to explain the "how" (e.g. how mapping is performed) but "what" (this mapping provides)

> We also
> consider mapping a virtual link onto a substrate node since
> both virtual nodes that are connected by the link are hosted
> on the same substrate node. I think it would be good to provide
> some examples of mappings to make this clear, maybe when discussing
> the terms virtual links and virtual nodes in more detail.

See above concerning the example. 

> > - virtual resources composing a virtual network can be of different
> > type and thus virtually operate at different layers (thus beyond
> > nodes and links operating at a given layer) including
> > wireless/wireline virtual links with different properties (with or
> > without emulated delay), hosts and intermediate nodes of different
> > kind, e.g., switches, routers, base stations, etc.). This is
> > basically what makes the difference between an "overlay network" and
> > "virtual network".
> 
> This is important, but probably not easy to grasp. I don't want to
> exclude having virtual switches or virtual wireless links and so on,
> but it's probably complicated to discuss them all together across
> different layers. If you consider virtual routers, then 
> virtual switches
> are probably "transparent" connectors just as they are for IP
> routers in physical networks.

The latter is about the actual use of the virtual network. 

The definitions have to comprise the notion of composition: the possibility to map different types of physical resources to different types of virtual resources that can operate different and be combined to provide a virtual network. 

> I think we need to work on that.
>
> The difference to overlay networks is IMHO (as also discussed in
> earlier mail
> http://www.ietf.org/mail-archive/web/vnrg/current/msg00224.html) that
> overlay nodes are always sitting at the "ends"
> of its underlying layer (the underlay).
>
> > The role definitions here below tend to reproduce (and thus somehow
> > limit) the roles we actually know from "physical networks". Taking
> > the above definitions, if the virtual network would be running on
> > physical hosts, "providers" would not maintain any physical resource
> > of the type indicated here below (routers, links, wireless
> > infrastructure, etc.) but only computing resources on
> > terminals/servers.
> 
> As already said above, I can't infer restrictions directly 
> from my text,

It is written texto in your definitions you have provided ""Out-of-VNet access" to control the virtual resources, allowing him to configure and manage them just like a traditional network operator manages physical network resources."

> but I'd suggest that we provide examples that make these aspects very
> clear. The provided definitions perfectly allow that a whole virtual
> network is embedded into a single physical substrate host.

As stated above I don't see where in the definitions. As stated above the definition constrict a virtual resource of type X to be hosted on physical resources of type X whereas is should read a virtual resource of type X could be hosted on a physical resource of type Y.

> On the other hand one can expect that also virtual networks are used
> to transport data over some physical distance in many cases. If this
> isn't the case one may probably come up with simpler structures that
> provide the same level of isolation, e.g., no need to provide a large
> virtual infrastructure using several virtual routers if you 
> merely need
> to connect virtual nodes that are *always* residing inside the same
> physical host - a single virtual switch or router may provide 
> sufficient
> connectivity or isolation between them (depending on the addressing
> scheme); this may change as soon as the virtual nodes
> may actually move to different substrate nodes...
> 
> > The role definitions provided here below tend to enforce too a
> > client-server strict demarcation between resource owner and 
> non-owner
> 
> Which resource do you mean here the virtual or the substrate resource?

Following the definitions you have provided the ownership of the substrate delimits the resource space accessible to host the virtual resources (Note: this has been the main point of discussion during the meeting in Beijing). 

> > merging thus a functional and operational role whereas demarcation
> > would be needed between an external entity to the VN (as 
> delimited by
> > the functionality that the VN delivers) and a Virtual NAP (whether
> > one owns the underlying resources or not).
> 
> Sorry, now I'm lost, I don't get your point here - can you provide
> an example? 

Here below, a simple example: 

        -------------VN---------------
       |                              |
      VNAP         ||                 |
  EE --X--> VR <---||---> VR          |
  |    |    |      ||    / | \        |
  R5   |   R4 R3---||---  R2  --- R1  |
       |           ||                 |
        -----------||-----------------
                   ||
<---- Owner 1 ---->||<--- Owner 2 --->


A functional demarcation line between EE and the VN exists because the VN provides a functionality to the EE not because the "resources" (R1,R2,R3,R4) (or what they can virtually host) are owned by the "VN provider" i.e. here R3, R4 belongs to Owner 1 and R2, R3 to Owner 2.  

In brief, the underlying architectural question is not about drawing demarcation lines between different owners of physical resources but about the functional demarcation determined by the composition of VR.

> I don't think that any client-server based demarcation
> is implied by the proposed architecture, 

Referring to the definitions you have provided "A service provider may provide services to end-users by using the protocols running inside the virtual network. Consider an IP-TV provider who delivers IP-TV inside the VNet to his customers."

> actually we also considered P2P-based
> self-organized access structures for controlling the virtual 
> resources...
>
> Thanks for your input, that was exactly what I was looking for,
> i.e., collecting different viewpoints in order to complete the
> big picture.

Thanks,
-dimitri.
 
> Regards,
>  Roland
> 
>