IETF Logo Mail Archive

Re: [nvo3] Draft NVO3 WG Charter

Robert Raszuk <robert@raszuk.net> Fri, 17 February 2012 18:35 UTC

Return-Path: <robert@raszuk.net>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AC7B021E8028 for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:35:57 -0800 (PST)
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=[AWL=-0.250, BAYES_00=-2.599, J_CHICKENPOX_13=0.6]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RlMz4OkhIXNR for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:35:57 -0800 (PST)
Received: from mail1310.opentransfer.com (mail1310.opentransfer.com [76.162.254.103]) by ietfa.amsl.com (Postfix) with ESMTP id 108E021E8015 for <nvo3@ietf.org>; Fri, 17 Feb 2012 10:35:57 -0800 (PST)
Received: (qmail 14309 invoked by uid 399); 17 Feb 2012 18:35:56 -0000
Received: from unknown (HELO ?192.168.1.57?) (pbs:m42@mojaklasa.info@83.28.249.110) by mail1310.opentransfer.com with ESMTPM; 17 Feb 2012 18:35:56 -0000
X-Originating-IP: 83.28.249.110
Message-ID: <4F3E9E0C.7030106@raszuk.net>
Date: Fri, 17 Feb 2012 19:35:56 +0100
From: Robert Raszuk <robert@raszuk.net>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1
MIME-Version: 1.0
To: david.black@emc.com
References: <201202171451.q1HEptR3027370@cichlid.raleigh.ibm.com>, <5E893DB832F57341992548CDBB333163A55C70661A@EMBX01-HQ.jnpr.net> <5E613872-0E27-46D2-8097-B31E7F0F37C5@mimectl>, <5E893DB832F57341992548CDBB333163A55C70669D@EMBX01-HQ.jnpr.net> <B56CFB4A-2393-42C7-9A89-0AA397512F12@mimectl> <5E893DB832F57341992548CDBB333163A55C9148ED@EMBX01-HQ.jnpr.net>, <4F3E8C9C.8070705@raszuk.net> <B3482790-2DA7-4E62-A531-D2E977F812EB@mimectl>
In-Reply-To: <B3482790-2DA7-4E62-A531-D2E977F812EB@mimectl>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Cc: narten@us.ibm.com, jdrake@juniper.net, rbonica@juniper.net, nvo3@ietf.org, afarrel@juniper.net, nitinb@juniper.net
Subject: Re: [nvo3] Draft NVO3 WG Charter
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
Reply-To: robert@raszuk.net
List-Id: "L2 \"Network Virtualization Over l3\" overlay discussion list \(nvo3\)" <nvo3.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/nvo3>, <mailto:nvo3-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/nvo3>
List-Post: <mailto:nvo3@ietf.org>
List-Help: <mailto:nvo3-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/nvo3>, <mailto:nvo3-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 17 Feb 2012 18:35:57 -0000

Hi,

<Apologies for past and future spelling mistakes>

> Both drafts are -00 versions that will need more work to fill in details.  The reason to look at those drafts now
> is that they provide additional insight into the problem space, which may
> help illuminate why a "just use a VPN" approach doesn't solve all the problems
> of interest.

Actually maybe nvo3 could even sign under "just use a VPN" .. however I 
think that the term VPN has a very broad definition. And as said before 
I am with you that there is area to be covered where current L2VPN and 
L3VPN WG documents do not well cover it.

The comment about nvgre is not to dismiss the need for new WG. It is 
solely to point out that we should reuse as much as possible in anything 
we do. That said I think multiplexing and demultiplexing with GRE 
encapsulation and some tag or label behind it IMHO is a solved problem 
which we may not need to reinvent again.

Many thx,
R.

v2.23.0 | Report a Bug | By Email