Re: [vnrg] Some definitions and way forward

Andreas Fischer <andreas.fischer@uni-passau.de> Thu, 04 August 2011 08:56 UTC

Return-Path: <andreas.fischer@uni-passau.de>
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 424DE21F8B83 for <vnrg@ietfa.amsl.com>; Thu, 4 Aug 2011 01:56:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.249
X-Spam-Level:
X-Spam-Status: No, score=-2.249 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HELO_EQ_DE=0.35]
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 EQTInUfMrfSu for <vnrg@ietfa.amsl.com>; Thu, 4 Aug 2011 01:56:50 -0700 (PDT)
Received: from tom.rz.uni-passau.de (tom.rz.uni-passau.de [132.231.51.4]) by ietfa.amsl.com (Postfix) with ESMTP id F3F9721F8AD2 for <vnrg@irtf.org>; Thu, 4 Aug 2011 01:56:49 -0700 (PDT)
Received: from tom.rz.uni-passau.de (puremessage.rz.uni-passau.de [132.231.51.54]) by tom.rz.uni-passau.de (Postfix) with SMTP id 3C4422E0936 for <vnrg@irtf.org>; Thu, 4 Aug 2011 10:57:03 +0200 (CEST)
Received: from mail.uni-passau.de (localhost [127.0.0.1]) by tom.rz.uni-passau.de (Postfix) with ESMTP id E54A52E07DD for <vnrg@irtf.org>; Thu, 4 Aug 2011 10:57:02 +0200 (CEST)
Received: from [132.231.13.115] (helo=[132.231.13.115]) by mail.uni-passau.de with ESMTP (eXpurgate 3.2.5) (envelope-from <andreas.fischer@uni-passau.de>) id 4e3a5ede-104a-84e70d730842-1 for <vnrg@irtf.org>; Thu, 04 Aug 2011 10:57:02 +0200
Message-ID: <4E3A5EDE.2060208@uni-passau.de>
Date: Thu, 04 Aug 2011 10:57:02 +0200
From: Andreas Fischer <andreas.fischer@uni-passau.de>
User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110624 Thunderbird/5.0
MIME-Version: 1.0
To: vnrg@irtf.org
References: <4E3936FF.1090006@kit.edu> <4E39750A.2080302@isi.edu> <4E39A9E8.5070307@kit.edu>
In-Reply-To: <4E39A9E8.5070307@kit.edu>
X-Enigmail-Version: 1.2
Content-Type: multipart/mixed; boundary="------------010107010505060108090203"
X-purgate-ID: 151291::1312448222-0000104A-179091EC/0-0/0-0
X-purgate-type: clean
X-purgate-size: 2196
X-purgate-Ad: Categorized by eleven eXpurgate (R) http://www.eleven.de
X-purgate: This mail is considered clean (visit http://www.eleven.de for further information)
X-purgate: clean
X-PerlMx-Spam: Gauge=X, Probability=10%, Report=' TO_IN_SUBJECT 0.5, MIME_TEXT_ONLY_MP_MIXED 0.05, BODYTEXTP_SIZE_3000_LESS 0, BODY_SIZE_2000_2999 0, BODY_SIZE_5000_LESS 0, BODY_SIZE_7000_LESS 0, RDNS_NXDOMAIN 0, RDNS_SUSP 0, RDNS_SUSP_GENERIC 0, __ANY_URI 0, __BAT_BOUNDARY 0, __BOUNCE_CHALLENGE_SUBJ 0, __BOUNCE_NDR_SUBJ_EXEMPT 0, __CP_URI_IN_BODY 0, __CT 0, __CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_MIXED 0, __HAS_MSGID 0, __LINES_OF_YELLING 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __MOZILLA_MSGID 0, __SANE_MSGID 0, __SUBJ_ALPHA_END 0, __TO_MALFORMED_2 0, __TO_NO_NAME 0, __URI_NO_MAILTO 0, __URI_NO_WWW 0, __URI_NS , __USER_AGENT 0'
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: Thu, 04 Aug 2011 08:56:51 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Roland, Joe,

>> 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.

Aren't VPNs just one kind of link virtualization? VPNs are basically
tunnels with added encryption, no? Tunnels, on the other hand, just
create a "virtual link" between two arbitrary nodes in a network.

As such, I would also disagree to consider them as kind of an overlay
network, as
a) They don't build a network, only a link (the 'N' in 'VPN' is
misleading, IMHO)
b) They are not necessarily between end hosts (which conflicts your
earlier statement, that overlay nodes are always sitting at the edge of
the network)

Regards,
Andreas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iD8DBQFOOl7eAjz9S4YPAw8RAm6VAJ4vKG+OBDXMIe9novs0Pk4bWMtlBgCePEKc
OMCz/O7q0UmUPB9X5nKcX2g=
=8z6n
-----END PGP SIGNATURE-----