Re: [nvo3] Consensus call and IPR check on draft-rekhter-nvo3-vm-mobility-issues-03.txt
Thomas Narten <narten@us.ibm.com> Mon, 10 December 2012 17:27 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 423E321F84CE for <nvo3@ietfa.amsl.com>; Mon, 10 Dec 2012 09:27:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -110.599
X-Spam-Level:
X-Spam-Status: No, score=-110.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_HI=-8, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id dN-jjl6Vodkh for <nvo3@ietfa.amsl.com>; Mon, 10 Dec 2012 09:27:17 -0800 (PST)
Received: from e9.ny.us.ibm.com (e9.ny.us.ibm.com [32.97.182.139]) by ietfa.amsl.com (Postfix) with ESMTP id 91EBE21F8502 for <nvo3@ietf.org>; Mon, 10 Dec 2012 09:27:17 -0800 (PST)
Received: from /spool/local by e9.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>; Mon, 10 Dec 2012 12:27:13 -0500
Received: from d01dlp01.pok.ibm.com (9.56.250.166) by e9.ny.us.ibm.com (192.168.1.109) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; Mon, 10 Dec 2012 12:27:10 -0500
Received: from d01relay07.pok.ibm.com (d01relay07.pok.ibm.com [9.56.227.147]) by d01dlp01.pok.ibm.com (Postfix) with ESMTP id 22A0738C8041 for <nvo3@ietf.org>; Mon, 10 Dec 2012 12:27:10 -0500 (EST)
Received: from d01av04.pok.ibm.com (d01av04.pok.ibm.com [9.56.224.64]) by d01relay07.pok.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id qBAHR1TE54460580 for <nvo3@ietf.org>; Mon, 10 Dec 2012 12:27:02 -0500
Received: from d01av04.pok.ibm.com (loopback [127.0.0.1]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id qBAHR1d4021387 for <nvo3@ietf.org>; Mon, 10 Dec 2012 12:27:01 -0500
Received: from cichlid.raleigh.ibm.com ([9.80.11.210]) by d01av04.pok.ibm.com (8.14.4/8.13.1/NCO v10.0 AVin) with ESMTP id qBAHQveK021137 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 10 Dec 2012 12:26:59 -0500
Received: from cichlid.raleigh.ibm.com (localhost.localdomain [127.0.0.1]) by cichlid.raleigh.ibm.com (8.14.5/8.12.5) with ESMTP id qBAHQuRq004765; Mon, 10 Dec 2012 12:26:57 -0500
Message-Id: <201212101726.qBAHQuRq004765@cichlid.raleigh.ibm.com>
To: "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com>
In-reply-to: <CCDD516B.3A1B8%matthew.bocci@alcatel-lucent.com>
References: <CCDD516B.3A1B8%matthew.bocci@alcatel-lucent.com>
Comments: In-reply-to "Bocci, Matthew (Matthew)" <matthew.bocci@alcatel-lucent.com> message dated "Thu, 29 Nov 2012 18:52:43 +0100."
Date: Mon, 10 Dec 2012 12:26:56 -0500
From: Thomas Narten <narten@us.ibm.com>
X-Content-Scanned: Fidelis XPS MAILER
x-cbid: 12121017-7182-0000-0000-000003AB90FF
Cc: "nvo3@ietf.org" <nvo3@ietf.org>
Subject: Re: [nvo3] Consensus call and IPR check on draft-rekhter-nvo3-vm-mobility-issues-03.txt
X-BeenThere: nvo3@ietf.org
X-Mailman-Version: 2.1.12
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: Mon, 10 Dec 2012 17:27:18 -0000
Chairs, WG: I would like to better understand what the "end goal" is in asking for WG adoption of vm-mobility. By adopting the document, there is a strong presumption the WG will (eventually) send it to the IESG for publication. Strictly speaking, it is not at all obvious to me which charter item deliverable vm-mobility applies to (it certainly isn't one of the 6 listed in the charter). I think it takes a pretty broad reading of the charter to say this document is "in scope". I have the concern that such a reading implies that a whole lot of other "related" documents will also then have to be taken on as WG documents. This could easily lead to a plethora of documents. Before adopting this (or other documents) I think the WG should get a little more clear about what types of documents the WG will adopt going forward and which it will not. What is the criteria? Will we take on anything the WG says we should adopt, regardless of what the charter says, and regardless of overlap among drafts? That said, I do think there is useful stuff in this document, but that is also the case for other non-WG documents. With regards to the document itself, there are other documents that relate to the same general topic, including (at least): draft-kompella-nvo3-server2nve-01.txt draft-gu-nvo3-tes-nve-mechanism-01.txt Is the intention to merge the above into vm-mobility? Or to have yet more documents that cover similar ground? And if the intention is to merge them, wouldn't it be better to start with that upfront, before adopting one document as a WG document? Generally speaking, I share Joel's concern that having more documents is not necessary a good thing, especially when a lot of them end up repeating some of the same material. Thomas
- [nvo3] Consensus call and IPR check on draft-rekh… Bocci, Matthew (Matthew)
- Re: [nvo3] Consensus call and IPR check on draft-… Henderickx, Wim (Wim)
- Re: [nvo3] Consensus call and IPR check on draft-… Ali Sajassi (sajassi)
- Re: [nvo3] Consensus call and IPR check on draft-… Luyuan Fang (lufang)
- Re: [nvo3] Consensus call and IPR check on draft-… Melinda Shore
- Re: [nvo3] Consensus call and IPR check on draft-… Lucy yong
- Re: [nvo3] Consensus call and IPR check on draft-… Joel M. Halpern
- Re: [nvo3] Consensus call and IPR check on draft-… Yakov Rekhter
- Re: [nvo3] Consensus call and IPR check on draft-… Ning So
- Re: [nvo3] Consensus call and IPR check on draft-… John E Drake
- Re: [nvo3] Consensus call and IPR check on draft-… Linda Dunbar
- Re: [nvo3] Consensus call and IPR check on draft-… LASSERRE, MARC (MARC)
- Re: [nvo3] Consensus call and IPR check on draft-… Paul Unbehagen
- [nvo3] 答复: Consensus call and IPR check on draft-… Mach Chen
- [nvo3] 答复: Consensus call and IPR check on draft-… Guyingjie (Yingjie)
- Re: [nvo3] Consensus call and IPR check on draft-… Eric Gray
- Re: [nvo3] Consensus call and IPR check on draft-… Sam Aldrin
- Re: [nvo3] Consensus call and IPR check on draft-… Doug Hanks
- Re: [nvo3] Consensus call and IPR check on draft-… Samer Salam (ssalam)
- Re: [nvo3] Consensus call and IPR check on draft-… Florin Balus
- Re: [nvo3] Consensus call and IPR check on draft-… thomas.morin
- Re: [nvo3] Consensus call and IPR check on draft-… Thomas Narten
- Re: [nvo3] Consensus call and IPR check on draft-… John E Drake
- Re: [nvo3] Consensus call and IPR check on draft-… Thomas Narten
- Re: [nvo3] Consensus call and IPR check on draft-… John E Drake
- Re: [nvo3] Consensus call and IPR check on draft-… Melinda Shore
- Re: [nvo3] Consensus call and IPR check on draft-… Henderickx, Wim (Wim)
- Re: [nvo3] Consensus call and IPR check on draft-… Linda Dunbar
- [nvo3] Closure of consensus call on draft-rekhter… Bocci, Matthew (Matthew)