IETF Logo Mail Archive

Re: [nvo3] Fwd: DRAFT Charter Update for Discussion

Linda Dunbar <linda.dunbar@huawei.com> Thu, 14 August 2014 18:57 UTC

Return-Path: <linda.dunbar@huawei.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2BCB1A035E for <nvo3@ietfa.amsl.com>; Thu, 14 Aug 2014 11:57:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.868
X-Spam-Level:
X-Spam-Status: No, score=-4.868 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.668, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Fb3NtuZ_SUnm for <nvo3@ietfa.amsl.com>; Thu, 14 Aug 2014 11:57:15 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9EB791A0340 for <nvo3@ietf.org>; Thu, 14 Aug 2014 11:57:14 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml402-hub.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BIG31274; Thu, 14 Aug 2014 18:57:13 +0000 (GMT)
Received: from DFWEML706-CHM.china.huawei.com (10.193.5.225) by lhreml402-hub.china.huawei.com (10.201.5.241) with Microsoft SMTP Server (TLS) id 14.3.158.1; Thu, 14 Aug 2014 19:57:12 +0100
Received: from DFWEML701-CHM.china.huawei.com ([10.193.5.50]) by dfweml706-chm ([10.193.5.225]) with mapi id 14.03.0158.001; Thu, 14 Aug 2014 11:57:00 -0700
From: Linda Dunbar <linda.dunbar@huawei.com>
To: Benson Schliesser <bensons@queuefull.net>
Thread-Topic: [nvo3] Fwd: DRAFT Charter Update for Discussion
Thread-Index: AQHPty6mssbwkisIXUKu/EAdN5EkAZvPMC3wgAGpLAD//5o38A==
Date: Thu, 14 Aug 2014 18:57:01 +0000
Message-ID: <4A95BA014132FF49AE685FAB4B9F17F645DB42C1@dfweml701-chm.china.huawei.com>
References: <186E2FAA-E5C5-4828-8199-4EE71B5A5C1A@queuefull.net> <CAP4=VcgV0RtgqAw3kwQPrU92Pqn2K=0hzg1+MCMH=XdKqNiU_w@mail.gmail.com> <4A95BA014132FF49AE685FAB4B9F17F645DB3B26@dfweml701-chm.china.huawei.com> <CAP4=VcjydPpWYUNK2y7_0StjwNn6WFtOv+a5Av3ptEqKme3wMw@mail.gmail.com>
In-Reply-To: <CAP4=VcjydPpWYUNK2y7_0StjwNn6WFtOv+a5Av3ptEqKme3wMw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.47.156.172]
Content-Type: multipart/alternative; boundary="_000_4A95BA014132FF49AE685FAB4B9F17F645DB42C1dfweml701chmchi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/nvo3/ONIZ3yvjgKaz1fSVPY1jd7kJNVg
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] Fwd: DRAFT Charter Update for Discussion
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Network Virtualization Overlays \(NVO3\) Working Group" <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: Thu, 14 Aug 2014 18:57:19 -0000

Benson,

I like your elaboration: a specific type of DCVPN: overlay-based with a logically centralized control plane.
It would be great if this explanation can be included in the Charter, something like:


“An NVO3 solution is to address a specific type of Data Center Virtual Private Network (DCVPN) that is overlay-based with a logically centralized control plane. The NVO3 WG will develop a set of protocols and/or protocol extensions that address the issues
described by draft-ietf-nvo3-overlay-problem-statement consistent with the
approach described by draft-ietf-nvo3-framework.”

Linda



From: Benson Schliesser [mailto:bensons@queuefull.net]
Sent: Thursday, August 14, 2014 12:57 PM
To: Linda Dunbar
Cc: nvo3@ietf.org
Subject: Re: [nvo3] Fwd: DRAFT Charter Update for Discussion

Hi, Linda.

On Wed, Aug 13, 2014 at 4:39 PM, Linda Dunbar <linda.dunbar@huawei.com<mailto:linda.dunbar@huawei.com>> wrote:
The proposed charter is so general that there is not much to pick on. Yes, you have done a great job drafting it.

I'm not sure if you're serious, or teasing me / being sarcastic, but either way I guess it puts a smile on my face. ;)

 So the NVO3 is now DCVPN? Since the underlay is IP, will it become another L3VPN?

Somebody else asked me a similar question privately, so I want to make sure it's clear...

The term "NVO3" refers to a working group. The term "DCVPN" refers to the category of solutions for providing multi-tenancy, etc in a DC environment. There are possibly many technical approaches to designing a DCVPN. Some of those approaches might be based on protocols like BGP, MPLS, etc, which are developed in other WGs. As proposed in the new charter, NVO3 does not own the scope / charter for all work on DCVPNs. Rather, the proposed NVO3 charter is meant to narrow our focus to a specific type of DCVPN: overlay-based with a logically centralized control plane.

That being said, is that not clear from the text that we proposed? Is there some specific way that it could be improved?

Cheers,
-Benson

v2.23.0 | Report a Bug | By Email