Re: [vnrg] Status of the VNRG: Dormant or dead?

Joe Touch <touch@isi.edu> Wed, 06 July 2011 23:55 UTC

Return-Path: <touch@isi.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 4766F21F8BA2 for <vnrg@ietfa.amsl.com>; Wed, 6 Jul 2011 16:55:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.499
X-Spam-Level:
X-Spam-Status: No, score=-105.499 tagged_above=-999 required=5 tests=[AWL=1.100, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 AifmBGufXXw2 for <vnrg@ietfa.amsl.com>; Wed, 6 Jul 2011 16:55:52 -0700 (PDT)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) by ietfa.amsl.com (Postfix) with ESMTP id C320D21F8B87 for <vnrg@irtf.org>; Wed, 6 Jul 2011 16:55:52 -0700 (PDT)
Received: from [128.9.160.252] (pen.isi.edu [128.9.160.252]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id p66Nt8CF029834 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=NOT); Wed, 6 Jul 2011 16:55:08 -0700 (PDT)
Message-ID: <4E14F5DC.9080406@isi.edu>
Date: Wed, 06 Jul 2011 16:55:08 -0700
From: Joe Touch <touch@isi.edu>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.18) Gecko/20110616 Thunderbird/3.1.11
MIME-Version: 1.0
To: Roland Bless <roland.bless@kit.edu>
References: <E84E7B8FF3F2314DA16E48EC89AB49F01CED6E4D@DAPHNIS.office.hd> <4E142E69.5040606@kit.edu> <4E148490.8000006@isi.edu> <4E149F7E.9080706@kit.edu>
In-Reply-To: <4E149F7E.9080706@kit.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Cc: "vnrg@irtf.org" <vnrg@irtf.org>
Subject: Re: [vnrg] Status of the VNRG: Dormant or dead?
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, 06 Jul 2011 23:55:53 -0000

Hi Roland,

To wrap up our exchange (I think)...

On 7/6/2011 10:46 AM, Roland Bless wrote:
> Hi Joe and all,
...
>> IMO, a VPN extends an existing network to add a new node, or ties two
>> existing networks together, i.e., it's a way to add a single private
>> link to a new node.
>
>> Further, VPN nodes are always a member of exactly one VPN.
>
> Usually, yes, though one can think of VPN concentrators providing
> access to several different VPNs

Oh - yes. But hosts are generally attached to only one VPN at a time. 
VPN concentrators are a lot like virtual machine devices that emulate 
separate VPN "attachment" points. Ultimately, though, every end system 
is a member of only one VPN, which differentiates it from a VN, IMO.

>>>> What do you see is important for the RG right now or what is missing?
>>>
>>> See above, but maybe we should also consider questions such as
>>> what interfaces and protocols are needed for creating inter-provider
>>> virtual networks.
>>
>> That seems to presume we know what an intra-provider VN is, and I'm not
>> sure we're all on a single page there... ;-)
>
> Ok, I meant a VN spanning several substrate providers (or to use
> 4WARD terminology: Infrastructure Providers - InPs) in
> contrast to a VN inside a single InP, which can be provided
> by using proprietary protocols.

Oh - certainly. A given VPN can be homogeneous or include hereogeneous 
components, and can either be internetworked (as IP goes over multiple 
link layers) or use gateways to translate between clouds (as the old 
Catenet did).

Joe