Re: [nvo3] Draft NVO3 WG Charter

<david.black@emc.com> Fri, 17 February 2012 18:27 UTC

Return-Path: <david.black@emc.com>
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 80AEA21F8587 for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:27:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -109.563
X-Spam-Level:
X-Spam-Status: No, score=-109.563 tagged_above=-999 required=5 tests=[AWL=1.036, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
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 Q7JFRXeGfMuD for <nvo3@ietfa.amsl.com>; Fri, 17 Feb 2012 10:27:23 -0800 (PST)
Received: from mexforward.lss.emc.com (mexforward.lss.emc.com [128.222.32.20]) by ietfa.amsl.com (Postfix) with ESMTP id F2FEF21F8539 for <nvo3@ietf.org>; Fri, 17 Feb 2012 10:27:18 -0800 (PST)
Received: from hop04-l1d11-si03.isus.emc.com (HOP04-L1D11-SI03.isus.emc.com [10.254.111.23]) by mexforward.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1HIRHof032366 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 17 Feb 2012 13:27:17 -0500
Received: from mailhub.lss.emc.com (mailhubhoprd04.lss.emc.com [10.254.222.226]) by hop04-l1d11-si03.isus.emc.com (RSA Interceptor); Fri, 17 Feb 2012 13:26:56 -0500
Received: from mxhub32.corp.emc.com (mxhub32.corp.emc.com [128.222.70.172]) by mailhub.lss.emc.com (Switch-3.4.3/Switch-3.4.3) with ESMTP id q1HIQuIL032621; Fri, 17 Feb 2012 13:26:56 -0500
Received: from mx14a.corp.emc.com ([169.254.1.157]) by mxhub32.corp.emc.com ([128.222.70.172]) with mapi; Fri, 17 Feb 2012 13:26:55 -0500
From: david.black@emc.com
To: robert@raszuk.net
Content-Class: urn:content-classes:message
Date: Fri, 17 Feb 2012 13:26:59 -0500
Thread-Topic: [nvo3] Draft NVO3 WG Charter
Thread-Index: AcztmL/M7fCISMciS7KUx1yIN/iDwAACEFmNAAAu2Ys=
Message-ID: <B3482790-2DA7-4E62-A531-D2E977F812EB@mimectl>
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>
In-Reply-To: <4F3E8C9C.8070705@raszuk.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
x-mimectl: Produced By Microsoft Exchange V8.3.105.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-EMM-MHVC: 1
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
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:27:23 -0000

Hi Robert,

> Actually to be fare on this one I have to agree with John.
I think you meant "fair" as opposed to "fare", although I'll be happy to collect
the latter from you ... or your spell-checker :-).

> 10 authors and 16 pages to define a GRE key is an amazing achievement.

I referenced both drafts for context, and I'm not going to argue with that
"major achievement" characterization.  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.

Thanks,
--David

________________________________
From: Robert Raszuk [robert@raszuk.net]
Sent: Friday, February 17, 2012 12:21 PM
To: Black, David
Cc: John E Drake; narten@us.ibm.com; nvo3@ietf.org; Ronald Bonica; Nitin Bahadur; Adrian Farrel
Subject: Re: [nvo3] Draft NVO3 WG Charter


> I suggest reading the NVGRE and VXLAN drafts for more context:
>>
>>      http://tools.ietf.org/html/draft-sridharan-virtualization-nvgre-00

Actually to be fare on this one I have to agree with John.

10 authors and 16 pages to define a GRE key is an amazing achievement.

Especially since GRE header with MPLS label behind it is used
effectively for many years now to achieve the same level of
virtualization in number of shipping applications.

Reference: RFC4023

Regards,
R.