Re: [nvo3] Network Virtualization Overlay Control Plane Requirements posted

Thomas Narten <narten@us.ibm.com> Tue, 31 January 2012 21:10 UTC

Return-Path: <narten@us.ibm.com>
X-Original-To: nvo3@ietfa.amsl.com
Delivered-To: nvo3@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52A0621F868C for <nvo3@ietfa.amsl.com>; Tue, 31 Jan 2012 13:10:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -108.954
X-Spam-Level:
X-Spam-Status: No, score=-108.954 tagged_above=-999 required=5 tests=[AWL=1.645, 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 uZSJUi4v70zI for <nvo3@ietfa.amsl.com>; Tue, 31 Jan 2012 13:10:33 -0800 (PST)
Received: from e6.ny.us.ibm.com (e6.ny.us.ibm.com [32.97.182.146]) by ietfa.amsl.com (Postfix) with ESMTP id A350021F867A for <nvo3@ietf.org>; Tue, 31 Jan 2012 13:10:32 -0800 (PST)
Received: from /spool/local by e6.ny.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for <nvo3@ietf.org> from <narten@us.ibm.com>; Tue, 31 Jan 2012 16:10:30 -0500
Received: from d01dlp02.pok.ibm.com (9.56.224.85) by e6.ny.us.ibm.com (192.168.1.106) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Tue, 31 Jan 2012 16:09:52 -0500
Received: from d01relay01.pok.ibm.com (d01relay01.pok.ibm.com [9.56.227.233]) by d01dlp02.pok.ibm.com (Postfix) with ESMTP id 96F0B6E8355 for <nvo3@ietf.org>; Tue, 31 Jan 2012 16:08:49 -0500 (EST)
Received: from d01av01.pok.ibm.com (d01av01.pok.ibm.com [9.56.224.215]) by d01relay01.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id q0VL7RVQ123552 for <nvo3@ietf.org>; Tue, 31 Jan 2012 16:07:27 -0500
Received: from d01av01.pok.ibm.com (loopback [127.0.0.1]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id q0VL7Qro027964 for <nvo3@ietf.org>; Tue, 31 Jan 2012 16:07:26 -0500
Received: from cichlid.raleigh.ibm.com (sig-9-65-243-241.mts.ibm.com [9.65.243.241]) by d01av01.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id q0VL7Op4027887 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Jan 2012 16:07:25 -0500
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 q0VL7MCK020031; Tue, 31 Jan 2012 16:07:23 -0500
Message-Id: <201201312107.q0VL7MCK020031@cichlid.raleigh.ibm.com>
To: sarikaya@ieee.org
In-reply-to: <CAC8QAcfmP5h+mmfbGwka6u2Ccn52agSVuy+_S03ESSOGT-t-Og@mail.gmail.com>
References: <CB4C3234.53546%kreeger@cisco.com> <CAC8QAcfmP5h+mmfbGwka6u2Ccn52agSVuy+_S03ESSOGT-t-Og@mail.gmail.com>
Comments: In-reply-to Behcet Sarikaya <sarikaya2012@gmail.com> message dated "Tue, 31 Jan 2012 13:53:06 -0600."
Date: Tue, 31 Jan 2012 16:07:22 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12013121-1976-0000-0000-00000A011DBD
Cc: nvo3@ietf.org, Larry Kreeger <kreeger@cisco.com>
Subject: Re: [nvo3] Network Virtualization Overlay Control Plane Requirements posted
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "L2 \"Network Virtualization Over l3\" overlay discussion list \(nvo3\)" <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: Tue, 31 Jan 2012 21:10:35 -0000

> Why was not this I-D submitted to dc?

I believe that the NVO3 effort, while related to 'dc', is separate
enough and scoped out enough that it shouldn't be part of 'dc'.

To me DC is a mailing list in search of a problem. 

In the case of both SDN and NVO3, I believe the efforts have done a
reasonable first cut at trying to carve out a specific problem area
that can stand on its own. By that, I mean can try to create a WG
based on a focused charter. Yes, both efforts still have work to do
before they can become WGs (if that is what eventually happens). And
yes, both efforts *relate* to data centers. But the way of the IETF is
to carve out self-contained WGs rather than trying to boil the ocean
in a big general area. If DC is ever to be successful, it needs to
tease out some concrete problems, with those individual problems at
some point leading to a focused WG. And such a WG would not be the "DC
WG", but a WG focussed on a much narrower problem.

But outside of SDN and NVO3, the DC "area" seems to be struggling with
coming up with concrete problems that the IETF should work on.

Thomas