[vpn4dc] Network Virtualization Overlay Control Plane Requirements posted

Larry Kreeger <kreeger@cisco.com> Tue, 31 January 2012 18:19 UTC

Return-Path: <kreeger@cisco.com>
X-Original-To: vpn4dc@ietfa.amsl.com
Delivered-To: vpn4dc@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id A13F111E8075 for <vpn4dc@ietfa.amsl.com>; Tue, 31 Jan 2012 10:19:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.002
X-Spam-Status: No, score=-4.002 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HTML_MESSAGE=0.001, J_CHICKENPOX_13=0.6, J_CHICKENPOX_32=0.6, MIME_QP_LONG_LINE=1.396, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id ph6+0gIeTdbC for <vpn4dc@ietfa.amsl.com>; Tue, 31 Jan 2012 10:19:32 -0800 (PST)
Received: from mtv-iport-1.cisco.com (mtv-iport-1.cisco.com []) by ietfa.amsl.com (Postfix) with ESMTP id 141F611E8073 for <vpn4dc@ietf.org>; Tue, 31 Jan 2012 10:19:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=kreeger@cisco.com; l=4391; q=dns/txt; s=iport; t=1328033971; x=1329243571; h=date:subject:from:to:message-id:in-reply-to:mime-version; bh=58DVYR6UWqooxOzWSYWIfVxh8r8gxPFrs4Zw34vm2Xg=; b=Tqd4EMnls3D/wl1ifv4LD/AcwvhGXJOvldGuVdwoPhjHsOCjmMbCAi2b sTWYVTVUKKcl/Sm+PVQEXgAjisRvBrNShCrm+ZoT5vMcW5RnMxg0w+5iv WvI3eNf/Mc1fo3juvPW99C6ix2y/VjgtZachvLG/50fpqnWfvbUaztZdp A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-AV: E=Sophos; i="4.71,597,1320624000"; d="scan'208,217"; a="26333855"
Received: from mtv-core-4.cisco.com ([]) by mtv-iport-1.cisco.com with ESMTP; 31 Jan 2012 18:19:31 +0000
Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com []) by mtv-core-4.cisco.com (8.14.3/8.14.3) with ESMTP id q0VIJVIZ007503 for <vpn4dc@ietf.org>; Tue, 31 Jan 2012 18:19:31 GMT
Received: from xmb-sjc-21e.amer.cisco.com ([]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.4675); Tue, 31 Jan 2012 10:19:31 -0800
Received: from ([]) by xmb-sjc-21e.amer.cisco.com ([]) via Exchange Front-End Server email.cisco.com ([]) with Microsoft Exchange Server HTTP-DAV ; Tue, 31 Jan 2012 18:19:31 +0000
User-Agent: Microsoft-Entourage/
Date: Tue, 31 Jan 2012 10:19:31 -0800
From: Larry Kreeger <kreeger@cisco.com>
To: vpn4dc@ietf.org
Message-ID: <CB4D70B3.53718%kreeger@cisco.com>
Thread-Topic: Network Virtualization Overlay Control Plane Requirements posted
Thread-Index: AczfhwmCNjK0MgCDPkWJDbI3krxH/AAvdakx
In-Reply-To: <CB4C3234.53546%kreeger@cisco.com>
Mime-version: 1.0
Content-type: multipart/alternative; boundary="B_3410849971_40251818"
X-OriginalArrivalTime: 31 Jan 2012 18:19:31.0754 (UTC) FILETIME=[E09AC8A0:01CCE044]
Subject: [vpn4dc] Network Virtualization Overlay Control Plane Requirements posted
X-BeenThere: vpn4dc@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: <vpn4dc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vpn4dc>, <mailto:vpn4dc-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vpn4dc>
List-Post: <mailto:vpn4dc@ietf.org>
List-Help: <mailto:vpn4dc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vpn4dc>, <mailto:vpn4dc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 31 Jan 2012 18:19:32 -0000

This needed moderator approval for Bcc...so I am posting it directly now.  -

------ Forwarded Message
From: Larry Kreeger <kreeger@cisco.com>
Date: Mon, 30 Jan 2012 11:40:36 -0800
To: <nvo3@ietf.org>
Subject: [nvo3] Network Virtualization Overlay Control Plane Requirements

To: nvo3 mailing list
Bcc: l2vpn, l3vpn, dc, armd, vpn4dc mailing lists

Hi everyone,

I have recently posted a first draft of the Control Plane requirements for
Network Virtualization Overlays.


This draft is a follow-up to draft-narten-nvo3-overlay-problem-statement-01
( http://tools.ietf.org/html/draft-narten-nvo3-overlay-problem-statement-01
) which makes the case for overlay networks in data centers (not restricted
to L2 over L3) and the need for control plane solutions.

If you have not read draft-narten-nvo3-overlay-problem-statement-01, I
highly suggest reading it first because the posted control plane reqs
document picks up where it left off.

Since the posted draft is a followup to
draft-narten-nvo3-overlay-problem-statement-01 , and there is already an
NVO3 mailing list, please join and post any discussion and/or comments to

Thank you,
Larry Kreeger

nvo3 mailing list

------ End of Forwarded Message