Re: [vnrg] Some definitions and way forward
Roland Bless <roland.bless@kit.edu> Wed, 03 August 2011 19:53 UTC
Return-Path: <roland.bless@kit.edu>
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 623C611E8092 for <vnrg@ietfa.amsl.com>; Wed, 3 Aug 2011 12:53:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.941
X-Spam-Level:
X-Spam-Status: No, score=-5.941 tagged_above=-999 required=5 tests=[AWL=0.308, BAYES_00=-2.599, HELO_EQ_DE=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 lVbiLph695yw for <vnrg@ietfa.amsl.com>; Wed, 3 Aug 2011 12:53:38 -0700 (PDT)
Received: from iramx2.ira.uni-karlsruhe.de (iramx2.ira.uni-karlsruhe.de [141.3.10.81]) by ietfa.amsl.com (Postfix) with ESMTP id 509B811E8091 for <vnrg@irtf.org>; Wed, 3 Aug 2011 12:53:37 -0700 (PDT)
Received: from i72vorta.tm.uni-karlsruhe.de ([141.3.71.26] helo=vorta.tm.kit.edu) by iramx2.ira.uni-karlsruhe.de with esmtp port 25 id 1QohVe-0004Ou-Rj; Wed, 03 Aug 2011 21:53:49 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id 0A0A1A806B5; Wed, 3 Aug 2011 21:53:41 +0200 (CEST)
Message-ID: <4E39A744.8010508@kit.edu>
Date: Wed, 03 Aug 2011 21:53:40 +0200
From: Roland Bless <roland.bless@kit.edu>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.0.1) Gecko/20060111 Thunderbird/1.5 Mnenhy/0.7.3.0
MIME-Version: 1.0
To: "Papadimitriou, Dimitri (Dimitri)" <dimitri.papadimitriou@alcatel-lucent.com>
References: <4E3936FF.1090006@kit.edu> <EFDB2B5417263843B5077E12666D8C10187C646B@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
In-Reply-To: <EFDB2B5417263843B5077E12666D8C10187C646B@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
X-ATIS-AV: ClamAV (iramx2.ira.uni-karlsruhe.de)
X-ATIS-AV: Kaspersky (iramx2.ira.uni-karlsruhe.de)
X-ATIS-Timestamp: iramx2.ira.uni-karlsruhe.de 1312401229.195784000
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 19:53:39 -0000
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. > - 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. How you map virtual nodes and virtual links onto the substrate resources may vary a lot. 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. > - 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. 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, 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. 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? > 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? I don't think that any client-server based demarcation is implied by the proposed architecture, actually we also considered P2P-based self-organized access structures for controlling the virtual resources... > Thanks, -dimitri. Thanks for your input, that was exactly what I was looking for, i.e., collecting different viewpoints in order to complete the big picture. Regards, Roland
- [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Bhumip Khasnabish
- Re: [vnrg] Some definitions and way forward Papadimitriou, Dimitri (Dimitri)
- Re: [vnrg] Some definitions and way forward Joe Touch
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Papadimitriou, Dimitri (Dimitri)
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Andreas Fischer
- Re: [vnrg] Some definitions and way forward SCHARF, Michael
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Papadimitriou, Dimitri (Dimitri)
- Re: [vnrg] Some definitions and way forward Andreas Fischer
- Re: [vnrg] Some definitions and way forward Joe Touch
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Flinck, Hannu (NSN - FI/Espoo)
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Flinck, Hannu (NSN - FI/Espoo)
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward Papadimitriou, Dimitri (Dimitri)
- Re: [vnrg] Some definitions and way forward Flinck, Hannu (NSN - FI/Espoo)
- Re: [vnrg] Some definitions and way forward Papadimitriou, Dimitri (Dimitri)
- Re: [vnrg] Some definitions and way forward Roland Bless
- Re: [vnrg] Some definitions and way forward JFC Morfin