[nvo3] NVO3 Data-Plane Adoptions
Benson Schliesser <bensons@queuefull.net> Thu, 19 March 2015 18:31 UTC
Return-Path: <bensons@queuefull.net>
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 BEBC21A8AB3 for <nvo3@ietfa.amsl.com>; Thu, 19 Mar 2015 11:31:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, 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 FrIC73VjQ9Yu for <nvo3@ietfa.amsl.com>; Thu, 19 Mar 2015 11:31:36 -0700 (PDT)
Received: from mail-qg0-f50.google.com (mail-qg0-f50.google.com [209.85.192.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D452F1A8834 for <nvo3@ietf.org>; Thu, 19 Mar 2015 11:31:33 -0700 (PDT)
Received: by qgfa8 with SMTP id a8so73134241qgf.0 for <nvo3@ietf.org>; Thu, 19 Mar 2015 11:31:33 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:content-type:content-transfer-encoding; bh=RqHBWVcSJZ3xVsLHKnrs3bOQ1KMVdvtjEYHymSZ564Y=; b=i+Tt/3NDD8jVOxcSS+l9SqAo1gmpavE5JPgNYfrdQqKLgdmeI4R38IQO0W0Tw3NwTm 4Gf5oCe2BB1dIKYxDX7WKQA2ExFMV7WFRszr52SrBgKq5Nx/pHQXHkOz+ilUb+Fd86Yt ilijxcKWlMeKEQgOTMH8KAkvnJktT/0CWFkVBHdO2u9DLaNz3bJXbM9m/PrWpmMYJd/U db91wTTC61ew5jXnnpEsYJmQe2HHxso0C55H6Y13Pg7OowsSx1ktMjZc3mdKBvIB1AJi oec0RNKaoKbUC6vGjKoEwSVyD70risRcXVRlke//S/JINa7/7teTjfcCtt+TeW+/RoyR QiUg==
X-Gm-Message-State: ALoCoQnTP9dpA8u9OD0Dcf7HNA32fZxfpo0yje8PcyiKUs0sedYDyHlE/Hw0QlmwxLYeTJj39OAj
X-Received: by 10.140.239.140 with SMTP id k134mr55091360qhc.98.1426789893107; Thu, 19 Mar 2015 11:31:33 -0700 (PDT)
Received: from desolation-9.local (68-115-154-254.static.hckr.nc.charter.com. [68.115.154.254]) by mx.google.com with ESMTPSA id b52sm1350485qgb.16.2015.03.19.11.31.31 for <nvo3@ietf.org> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 19 Mar 2015 11:31:32 -0700 (PDT)
Message-ID: <550B1602.2050000@queuefull.net>
Date: Thu, 19 Mar 2015 14:31:30 -0400
From: Benson Schliesser <bensons@queuefull.net>
User-Agent: Postbox 3.0.11 (Macintosh/20140602)
MIME-Version: 1.0
To: "nvo3@ietf.org" <nvo3@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/nvo3/KAQrl5MlxAQ6ctmvCfrcsWfDy2A>
Subject: [nvo3] NVO3 Data-Plane Adoptions
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, 19 Mar 2015 18:31:38 -0000
Dear NVO3 Contributors - Matthew and I have discussed adoption of Data Plane encapsulations for NVO3. We have concluded that the WG may adopt multiple encapsulation drafts, and possibly publish those drafts as RFCs with Experimental status. At a future date we may consider whether any of these make sense for Proposed Standard status, e.g. based on documented implementations and market acceptance. Therefore, I will shortly be sending messages to the NVO3 mailing list for each Data Plane encap draft that has been discussed recently. These will include: - draft-gross-geneve-02 - draft-quinn-vxlan-gpe-04 - draft-herbert-gue-03 Please reply to each thread independently so that Matthew and I can keep track of feedback. Keep in mind that this is a discussion of WG adoption, not a last-call, and therefore we are only looking for feedback on whether the draft provides a good starting-point for further development within the WG. We would encourage contributors to be familiar with draft-ietf-nvo3-dataplane-requirements and draft-rtg-dt-encap, and to frame any specific comments in the context of that material. Thanks, -Benson & Matthew
- [nvo3] NVO3 Data-Plane Adoptions Benson Schliesser