Re: [vnrg] Some definitions and way forward

Roland Bless <> Wed, 03 August 2011 20:04 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 0150321F8429 for <>; Wed, 3 Aug 2011 13:04:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.977
X-Spam-Status: No, score=-5.977 tagged_above=-999 required=5 tests=[AWL=0.272, BAYES_00=-2.599, HELO_EQ_DE=0.35, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id qJMDpJ9NLJro for <>; Wed, 3 Aug 2011 13:04:52 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 6082F21F83E2 for <>; Wed, 3 Aug 2011 13:04:52 -0700 (PDT)
Received: from ([] by with esmtp port 25 id 1QohgY-0005cw-Nl; Wed, 03 Aug 2011 22:05:04 +0200
Received: from [IPv6:::1] (localhost []) by (Postfix) with ESMTPS id E50EDA806B5; Wed, 3 Aug 2011 22:04:57 +0200 (CEST)
Message-ID: <>
Date: Wed, 03 Aug 2011 22:04:56 +0200
From: Roland Bless <>
Organization: Institute of Telematics, Karlsruhe Institute of Technology (KIT)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20060111 Thunderbird/1.5 Mnenhy/
MIME-Version: 1.0
To: Joe Touch <>
References: <> <>
In-Reply-To: <>
X-Enigmail-Version: 1.1.2
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-ATIS-AV: Kaspersky (
X-ATIS-Timestamp: 1312401904.168867000
Cc: "" <>
Subject: Re: [vnrg] Some definitions and way forward
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Virtual Networks Research Group \(VNRG\) discussion list" <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 03 Aug 2011 20:04:53 -0000

Hi Joe,

On 03.08.2011 18:19, Joe Touch wrote:
> Some of the issues below go well beyond architecture - e.g., operators,
> ISPs, etc.

I don't know what you consider as architecture, but we came up with
the roles in order to define an architecture. Some of the roles
definitely imply control interfaces for access virtual resources.
I don't want to discuss any non-technical implications, esp. business
stuff, here, but IMHO one cannot leave the control plane aside.

> It might be useful to focus on the arch aspects first.

Do you consider the data plane aspects as being the architecture?
IMHO the control plane aspects belongs to the architecture as well!

> Also, it'd be useful to understand your view of the relationship of
> these definitions to PPVPNs, VPNs, etc.

I have no clear description yet, but VPNs usually are not including
the virtual node aspect. They are mainly about providing/establishing
links to connect to an existing infrastructure and are more a kind of
overlay. I think we need to come  up with a clearer distinction, but
that will need more time.