Re: [vnrg] Some definitions and way forward

Roland Bless <roland.bless@kit.edu> Fri, 05 August 2011 11:04 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 0ECE821F8B76 for <vnrg@ietfa.amsl.com>; Fri, 5 Aug 2011 04:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.048
X-Spam-Level:
X-Spam-Status: No, score=-6.048 tagged_above=-999 required=5 tests=[AWL=0.201, 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 Z4Lf-t0jEUNG for <vnrg@ietfa.amsl.com>; Fri, 5 Aug 2011 04:04:33 -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 4354E21F8B54 for <vnrg@irtf.org>; Fri, 5 Aug 2011 04:04:32 -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 1QpICo-0001Aw-KS; Fri, 05 Aug 2011 13:04:47 +0200
Received: from [IPv6:::1] (localhost [127.0.0.1]) by vorta.tm.kit.edu (Postfix) with ESMTPS id A00A5A80067; Fri, 5 Aug 2011 13:04:41 +0200 (CEST)
Message-ID: <4E3BCE47.2000805@kit.edu>
Date: Fri, 05 Aug 2011 13:04:39 +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: "Flinck, Hannu (NSN - FI/Espoo)" <hannu.flinck@nsn.com>
References: <4E3936FF.1090006@kit.edu><EFDB2B5417263843B5077E12666D8C10187C646B@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com><4E39A744.8010508@kit.edu><EFDB2B5417263843B5077E12666D8C10187C6490@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com><4E3A59FE.1090809@kit.edu><EFDB2B5417263843B5077E12666D8C1018FD26C8@FRMRSSXCHMBSB1.dc-m.alcatel-lucent.com> <4E3B09D2.70202@kit.edu> <26E5D1C5D5365D47B147E5E62FC73585036D307A@FIESEXC035.nsn-intra.net> <4E3BA5DE.6010204@kit.edu> <26E5D1C5D5365D47B147E5E62FC73585036D31C7@FIESEXC035.nsn-intra.net>
In-Reply-To: <26E5D1C5D5365D47B147E5E62FC73585036D31C7@FIESEXC035.nsn-intra.net>
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 1312542287.914099000
Cc: 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: Fri, 05 Aug 2011 11:04:34 -0000

Hi Hannu,

On 05.08.2011 10:31, Flinck, Hannu (NSN - FI/Espoo) wrote:
> Can you please elaborate what do you mean by "As soon as you
> areconsidering control plane issues, different roles matter a lot." For
> me the InP and VNP doesn't seem to be that useful other than explaining
> a certain, somewhat limited business model.

As already mentioned, it's really not about discussing a business
model, but about controlling virtual and real resources. In order to
do that you need different control interfaces for the various
stakeholders. Let's assume you (as VNO) need to reboot your virtual
router, because it crashed. Then your InP needs to provide access to the
virtual router in order to do that, no matter where it is currently
hosted in the substrate, but probably without exposing the current
mapping of virtual to substrate resources.
As InP you have the mapping information and can easily do this, maybe
using a different control interface. If you have a VNet spanning several
InP domains, you even need to find out first at which InP the virtual
router is currently hosted. This has implications for addressing
virtual resources in the control plane and so on. These are important
control plane aspects, not business model aspects.

Regards,
 Roland