IETF Logo Mail Archive

Re: [nvo3] WG Review: Network Virtualization Overlays (nvo3) - 23-Apr-2012 update

Thomas Narten <narten@us.ibm.com> Mon, 23 April 2012 17:07 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F15221F8703 for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 10:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.322
X-Spam-Level:
X-Spam-Status: No, score=-110.322 tagged_above=-999 required=5 tests=[AWL=0.277, BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bQfOsCqTem5V for <ietf@ietfa.amsl.com>; Mon, 23 Apr 2012 10:07:56 -0700 (PDT)
Received: from e39.co.us.ibm.com (e39.co.us.ibm.com [32.97.110.160]) by ietfa.amsl.com (Postfix) with ESMTP id D0FDB21F8700 for <ietf@ietf.org>; Mon, 23 Apr 2012 10:07:51 -0700 (PDT)
Received: from /spool/local by e39.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <ietf@ietf.org> from <narten@us.ibm.com>; Mon, 23 Apr 2012 11:07:46 -0600
Received: from d03dlp02.boulder.ibm.com (9.17.202.178) by e39.co.us.ibm.com (192.168.1.139) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 23 Apr 2012 11:07:40 -0600
Received: from d03relay05.boulder.ibm.com (d03relay05.boulder.ibm.com [9.17.195.107]) by d03dlp02.boulder.ibm.com (Postfix) with ESMTP id 2A68C3E40047; Mon, 23 Apr 2012 11:07:39 -0600 (MDT)
Received: from d03av04.boulder.ibm.com (d03av04.boulder.ibm.com [9.17.195.170]) by d03relay05.boulder.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q3NH7NwY030918; Mon, 23 Apr 2012 11:07:28 -0600
Received: from d03av04.boulder.ibm.com (loopback [127.0.0.1]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q3NH7LJB015186; Mon, 23 Apr 2012 11:07:21 -0600
Received: from cichlid.raleigh.ibm.com (sig-9-65-240-231.mts.ibm.com [9.65.240.231]) by d03av04.boulder.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q3NH7GlT014574 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 23 Apr 2012 11:07:17 -0600
Received: from cichlid.raleigh.ibm.com (localhost [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id q3NH7DNd007563; Mon, 23 Apr 2012 13:07:13 -0400
Message-Id: <201204231707.q3NH7DNd007563@cichlid.raleigh.ibm.com>
To: stbryant@cisco.com
Subject: Re: [nvo3] WG Review: Network Virtualization Overlays (nvo3) - 23-Apr-2012 update
In-reply-to: <4F957C03.5020108@cisco.com>
References: <20120417164749.21952.99664.idtracker@ietfa.amsl.com> <4F957C03.5020108@cisco.com>
Comments: In-reply-to Stewart Bryant <stbryant@cisco.com> message dated "Mon, 23 Apr 2012 16:57:55 +0100."
Date: Mon, 23 Apr 2012 13:07:12 -0400
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12042317-4242-0000-0000-0000016DC496
Cc: nvo3@ietf.org, "iesg@ietf.org" <iesg@ietf.org>, IETF Discussion <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 23 Apr 2012 17:07:57 -0000

Hi Stewart.

Charter generally looks good to me. On the milestones, however:

> Milestones:

> Dec 2012 Problem Statement submitted for IESG review
> Dec 2012 Framework document submitted for IESG review
> Dec 2012 Data plane requirements submitted for IESG review
> Dec 2012 Operational Requirements submitted for IESG review
> Mar 2012 Control plane requirements submitted for IESG review
> Mar 2012 Gap Analysis submitted for IESG review
> Apr 2012 Recharter or close Working Group

You presumably mean 2013 for the last 3.

That said, I really hope the WG can get all of its documents to the
IESG by December. That gives the WG 7-8 months and 2 IETF
meetings. Not an easy task, but if it takes the WG a full year before
it gets to doing anything beyond requirements, etc., that does not
paint a very encouraging picture.  I recall during the BOF someone
(Jon Hudson?) stating that industry is already well ahead of the IETF
in this space...

Thomas

v2.23.0 | Report a Bug | By Email