WG Review: Network Virtualization Overlays (nvo3)

The IESG <iesg-secretary@ietf.org> Fri, 03 October 2014 20:35 UTC

Return-Path: <iesg-secretary@ietf.org>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id CA90A1A1B45; Fri, 3 Oct 2014 13:35:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id iirvQDACcYip; Fri, 3 Oct 2014 13:35:12 -0700 (PDT)
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 3AA9D1A0012; Fri, 3 Oct 2014 13:35:12 -0700 (PDT)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Subject: WG Review: Network Virtualization Overlays (nvo3)
X-Test-IDTracker: no
X-IETF-IDTracker: 5.6.3.p3
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <20141003203512.25349.91166.idtracker@ietfa.amsl.com>
Date: Fri, 03 Oct 2014 13:35:12 -0700
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-announce/rMKg5zJgHiiANulEnTbf6JfznPc
Cc: nvo3 WG <nvo3@ietf.org>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.15
Reply-To: ietf@ietf.org
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Oct 2014 20:35:16 -0000

The Network Virtualization Overlays (nvo3) working group in the Routing
Area of the IETF is undergoing rechartering. The IESG has not made any
determination yet. The following draft charter was submitted, and is
provided for informational purposes only. Please send your comments to
the IESG mailing list (iesg at ietf.org) by 2014-10-13.

Network Virtualization Overlays (nvo3)
Current Status: Active WG

  Matthew Bocci <matthew.bocci@alcatel-lucent.com>
  Benson Schliesser <bensons@queuefull.net>

  Sam Aldrin <aldrin.ietf@gmail.com>

Technical advisors:
  Ron Bonica <rbonica@juniper.net>

Assigned Area Director:
  Alia Atlas <akatlas@gmail.com>

Mailing list
  Address: nvo3@ietf.org
  To Subscribe: https://www.ietf.org/mailman/listinfo/nvo3
  Archive: http://www.ietf.org/mail-archive/web/nvo3/


The purpose of the NVO3 WG is to develop a set of protocols and/or
extensions that enable network virtualization within a data center (DC)
environment that assumes an IP-based underlay. An NVO3 solution provides
2 and/or layer 3 services for virtual networks enabling multi-tenancy and
workload mobility, addressing the issues described in the problem
(including management and security), and consistent with the framework
previously produced by the NVO3 WG.

The NVO3 WG will develop solutions for network virtualization based on
the following architectural tenets:
 - Support for an IP-based underlay data plane
 - A logically centralized authority for network virtualization
Network virtualization approaches that do not adhere to these tenets are
explicitly outside of the scope of the NVO3 WG.

In pursuit of the solutions described above, the NVO3 WG will document an
architecture for network virtualization within a data center environment.

The NVO3 WG may produce requirements for a network virtualization
control plane, and will select, extend, and/or develop one protocol
for each of the functional interfaces identified to support the
architecture. Such protocols are expected to fulfill the communication
requirements between an End Device and a Network Virtualization Edge
(NVE) in cases where the NVE is not co-resident with the End Device,
and between an NVE and the Network Virtualization Authority (NVA).
The internal mechanisms and protocols of a logically centralized NVA
are explicitly out of scope of the NVO3 WG.  Architectural issues
raised by coexistence of multiple logically centralized control planes
in the same data center may be considered by the WG. Inter-DC
mechanisms are not in scope of the NVO3 WG at this time.

The NVO3 WG may produce requirements for network virtualization data
planes based on encapsulation of virtual network traffic over an IP-based
underlay data plane. Such requirements should consider OAM and security. Based on
these requirements the WG will select, extend, and/or develop one or more data
plane encapsulation format(s).

Additionally, the WG may document common use-cases for NVO3 solutions.

The working group may choose to adopt a protocol or data encapsulation
that was previously worked on outside the IETF as the basis for the WG's work.  If
the NVO3 WG anticipates the adoption of the technologies of another SDO as
part of the selected protocols or data encapsulation, the NVO3 WG will first
liaise with that SDO to ensure the compatibility of the approach.

The NVO3 WG will not consider solutions to network virtualization
within a data center environment based on extensions to BGP or LISP