Re: [nvo3] Call for WG Adoption of draft-herbert-gue-03

Christian Kuhtz <chkuhtz@microsoft.com> Fri, 20 March 2015 17:35 UTC

Return-Path: <chkuhtz@microsoft.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 5758B1A7023 for <nvo3@ietfa.amsl.com>; Fri, 20 Mar 2015 10:35:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.902
X-Spam-Level:
X-Spam-Status: No, score=-1.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_PASS=-0.001, 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 UNy9rwk4WKuO for <nvo3@ietfa.amsl.com>; Fri, 20 Mar 2015 10:35:42 -0700 (PDT)
Received: from na01-bn1-obe.outbound.protection.outlook.com (mail-bn1on0718.outbound.protection.outlook.com [IPv6:2a01:111:f400:fc10::718]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A7561A7026 for <nvo3@ietf.org>; Fri, 20 Mar 2015 10:35:41 -0700 (PDT)
Received: from BLUPR03MB230.namprd03.prod.outlook.com (10.255.213.19) by BLUPR03MB229.namprd03.prod.outlook.com (10.255.213.11) with Microsoft SMTP Server (TLS) id 15.1.125.14; Fri, 20 Mar 2015 17:35:19 +0000
Received: from BLUPR03MB230.namprd03.prod.outlook.com ([169.254.12.217]) by BLUPR03MB230.namprd03.prod.outlook.com ([169.254.12.217]) with mapi id 15.01.0125.002; Fri, 20 Mar 2015 17:35:19 +0000
From: Christian Kuhtz <chkuhtz@microsoft.com>
To: "nvo3@ietf.org" <nvo3@ietf.org>
Thread-Topic: [nvo3] Call for WG Adoption of draft-herbert-gue-03
Thread-Index: AQHQYnMaweVx8vnXxkSJ1+GU5vRX950kQTkAgAFgMKA=
Date: Fri, 20 Mar 2015 17:35:19 +0000
Message-ID: <BLUPR03MB230C9817749184762519C1CB20E0@BLUPR03MB230.namprd03.prod.outlook.com>
References: <550B1616.6040507@queuefull.net> <CALx6S34KKfpA8rD4qwJRWSbtu6+H7Y1nVj6Xb8soZKPE4rtP_g@mail.gmail.com>
In-Reply-To: <CALx6S34KKfpA8rD4qwJRWSbtu6+H7Y1nVj6Xb8soZKPE4rtP_g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [2001:4898:80e0:ee43::3]
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;
x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:;SRVR:BLUPR03MB229;
x-microsoft-antispam-prvs: <BLUPR03MB2295C5CB277AF87E1C03E6DB20E0@BLUPR03MB229.namprd03.prod.outlook.com>
x-forefront-antispam-report: BMV:1; SFV:NSPM; SFS:(10019020)(6009001)(13464003)(377454003)(164054003)(377424004)(51704005)(110136001)(230783001)(450100001)(77156002)(2900100001)(107886001)(2950100001)(92566002)(15975445007)(102836002)(2501003)(106116001)(122556002)(40100003)(62966003)(2351001)(50986999)(76576001)(76176999)(54356999)(46102003)(33656002)(2656002)(86612001)(86362001)(19580395003)(19580405001)(87936001)(74316001)(3826002); DIR:OUT; SFP:1102; SCL:1; SRVR:BLUPR03MB229; H:BLUPR03MB230.namprd03.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(601004)(5005006)(5002010); SRVR:BLUPR03MB229; BCL:0; PCL:0; RULEID:; SRVR:BLUPR03MB229;
x-forefront-prvs: 05214FD68E
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: microsoft.onmicrosoft.com
X-MS-Exchange-CrossTenant-originalarrivaltime: 20 Mar 2015 17:35:19.3375 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR03MB229
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/etG7jdI4MK4-LS1FITeVcMqX9Ww>
Subject: Re: [nvo3] Call for WG Adoption of draft-herbert-gue-03
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: Fri, 20 Mar 2015 17:35:44 -0000

I think draft-herbert-gue-03 should reference draft-hy-nvo3-gue-4-nvo-01 (not referenced, although implied in the language) and draft-hy-gue-4-secure-transport-01 (-00 is referenced in the draft at the moment) to tie this together in the context of virtualization.

With that, I think the three components should be submitted as they are for adoption as three separate drafts making up the sum that is GUE for virtualization.

Best regards,
Christian

-----Original Message-----
From: nvo3 [mailto:nvo3-bounces@ietf.org] On Behalf Of Tom Herbert
Sent: Thursday, March 19, 2015 1:27 PM
To: Benson Schliesser
Cc: nvo3@ietf.org
Subject: Re: [nvo3] Call for WG Adoption of draft-herbert-gue-03

On Thu, Mar 19, 2015 at 11:31 AM, Benson Schliesser <bensons@queuefull.net> wrote:
> This message starts a 2-week Call for Adoption of draft-herbert-gue-03 
> as a
> NVO3 WG item.
>
Benson asked me to query the list on this...

There is a subtlety for GUE.

draft-herbert-gue-03 specifies GUE as a generic encapsulation protocol.The use of GUE for network virtualization is specified in draft-hy-nvo3-gue-4-nvo-01. We also specified the security which I believe is critical to NVO3 deployment in draft-hy-gue-4-secure-transport-01.

I personally think it's a good idea to keep the general specification somewhat decoupled from the network virtualization use case as we are already seeing deployment use cases for that. But for purposes of WG adoption in NVO3 these is a question as to how we should proceed:

Should we request WG adoption for each of these?
Is it okay to just request adoption of the primary GUE draft?
Should we consolidate these into one draft for NVO3 purposes?

Thanks,
Tom

> The chairs believe that WG consensus is in favor of adoption of this draft.
> Please reply to this email thread, to the nvo3 email list, with 
> expressions of support or opposition. If expressing opposition to 
> adoption please elaborate substantially on the issues that motivate this view.
>
> This Call for Adoption will conclude on 2015-03-15, at which times the 
> chairs will reevaluate their view of consensus based on mailing list 
> discussion.
>
> Thanks,
> -Benson & Matthew
>
>
>
> _______________________________________________
> nvo3 mailing list
> nvo3@ietf.org
> https://www.ietf.org/mailman/listinfo/nvo3

_______________________________________________
nvo3 mailing list
nvo3@ietf.org
https://www.ietf.org/mailman/listinfo/nvo3