[vnfpool] 答复: New Charter for Toronto

Zongning <zongning@huawei.com> Mon, 07 July 2014 02:28 UTC

Return-Path: <zongning@huawei.com>
X-Original-To: vnfpool@ietfa.amsl.com
Delivered-To: vnfpool@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 70B1A1A00C3 for <vnfpool@ietfa.amsl.com>; Sun, 6 Jul 2014 19:28:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.552
X-Spam-Status: No, score=-104.552 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.651, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id W7OP4Ma0PHu7 for <vnfpool@ietfa.amsl.com>; Sun, 6 Jul 2014 19:28:27 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com []) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 58E881A00C2 for <vnfpool@ietf.org>; Sun, 6 Jul 2014 19:28:26 -0700 (PDT)
Received: from (EHLO lhreml404-hub.china.huawei.com) ([]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BJR64319; Mon, 07 Jul 2014 02:28:24 +0000 (GMT)
Received: from NKGEML406-HUB.china.huawei.com ( by lhreml404-hub.china.huawei.com ( with Microsoft SMTP Server (TLS) id; Mon, 7 Jul 2014 03:28:23 +0100
Received: from NKGEML501-MBS.china.huawei.com ([]) by nkgeml406-hub.china.huawei.com ([]) with mapi id 14.03.0158.001; Mon, 7 Jul 2014 10:26:31 +0800
From: Zongning <zongning@huawei.com>
To: Don Clarke <D.Clarke@cablelabs.com>
Thread-Topic: [vnfpool] New Charter for Toronto
Thread-Index: Ac+XKHD4e3Tyhku3QbmwqloaWSCkwwAeKS/w//+kKwCAAEMdgIAAHkeAgAFCeYCAAEQWgIABZCSA//8ms0A=
Date: Mon, 07 Jul 2014 02:26:30 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC6667796616D7EA@nkgeml501-mbs.china.huawei.com>
References: <B0D29E0424F2DE47A0B36779EC6667796616CDC0@nkgeml501-mbs.china.huawei.com> <F67D8AE3B3893148B7E3EF3977D554E5402168@EXCHANGE.cablelabs.com> <0ec801cf97b6$3a660400$af320c00$@olddog.co.uk> <E4DE949E6CE3E34993A2FF8AE79131F838E553@DEMUMBX005.nsn-intra.net> <53B744CB.9000404@nomountain.net> <E4DE949E6CE3E34993A2FF8AE79131F838EC4A@DEMUMBX005.nsn-intra.net>, <1527F33A-81DD-4672-9B57-AE2BD3D80BF9@telefonica.com> <F67D8AE3B3893148B7E3EF3977D554E5416B07@EXCHANGE.cablelabs.com>
In-Reply-To: <F67D8AE3B3893148B7E3EF3977D554E5416B07@EXCHANGE.cablelabs.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
x-originating-ip: []
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/dWnqcchPTPUHiaQONwrhScQxPYU
Cc: "vnfpool@ietf.org" <vnfpool@ietf.org>, "WRIGHT, STEVEN A" <sw3588@att.com>, Raquel Morera <raquel.morera@verizon.com>, "tetsuya.nakamura.cu@nttdocomo.com" <tetsuya.nakamura.cu@nttdocomo.com>
Subject: [vnfpool] 答复: New Charter for Toronto
X-BeenThere: vnfpool@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion list for virtual network function resource pooling." <vnfpool.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/vnfpool/>
List-Post: <mailto:vnfpool@ietf.org>
List-Help: <mailto:vnfpool-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/vnfpool>, <mailto:vnfpool-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 Jul 2014 02:28:29 -0000

Hi, Don and All,

(deleted some recipients as they are already the members of vnfpool list ...)

Firstly, thank you so much for acknowledging our work of VNFPool in IETF. :-)
I absolutely agree that VNFPool folks should properly take the excellent work done by NFV ISG into account whenever appropriate. Actually, as mentioned by Daniel, the co-authors of existing VNFPool drafts have been kindly regarding ISG as key informational resource, and will continue making appropriate references when more ISG documents are publicly available.
I am also glad to let you know that from the day one of VNFPool initiative, the active contributors are (really) active in both communities. For instance, I was leading Gap Analysis section in REL GS, and had communications with REL folks about VNFPool. On the VNFPool list, from time to time there are folks talking about the requirements from REL WG. So both communities have been in a good alignment in a nature (de facto) way. But I do agree with you that it does no harm to be explicit in VNFPool charter and through LS to formalized such coordination.
I will try to suggest some words into the charter and also help on the LS, when appropriate.



发件人: Don Clarke [mailto:D.Clarke@cablelabs.com] 
发送时间: 2014年7月7日 4:53
收件人: DIEGO LOPEZ GARCIA; ext Melinda Shore; Ersue, Mehmet (NSN - DE/Munich)
抄送: adrian@olddog.co.uk; Zongning; vnfpool@ietf.org; WRIGHT, STEVEN A; naseem.a.khan@verizon.com; tetsuya.nakamura.cu@nttdocomo.com; Raquel Morera
主题: RE: [vnfpool] New Charter for Toronto

Sorry for triggering such a big discussion. I think Mehmet captured my concern exactly. I only wanted to be sure that the IETF vnfpool folks take account of the excellent ground work already documented. I also recognize that the best way to achieve that is by active contribution.  On the other hand it does no harm to be explicit in the charter and through ongoing formal liaison to help "institutionalize" the relationship. Especially for folks in the IETF who might not understand the significance of the ISG work.

I also agree there is no rush to put in a liaison as we have high profile individuals active in both places at the moment and hopefully ongoing. 

From: DIEGO LOPEZ GARCIA [diego.r.lopez@telefonica.com]
Sent: Saturday, July 05, 2014 18:38
To: ext Melinda Shore; Ersue, Mehmet (NSN - DE/Munich)
Cc: adrian@olddog.co.uk; Don Clarke; Zongning; vnfpool@ietf.org; WRIGHT, STEVEN A; naseem.a.khan@verizon.com; tetsuya.nakamura.cu@nttdocomo.com; DIEGO LOPEZ GARCIA; Raquel Morera
Subject: Re: [vnfpool] New Charter for Toronto


On 5 Jul 2014, at 21:34 , Ersue, Mehmet (NSN - DE/Munich) <mehmet.ersue@nsn.com<mailto:mehmet.ersue@nsn.com>> wrote:

I agree about being specific about which ETSI body will be engaged.

You can express what is already happening in many ways, also e.g.
"..will exchange information with relevant WGs in ETSI NFV, e.g. REL WG.." or "..will exchange information with ETSI NFV REL, MANO and INF WGs..".

Let me know which one you prefer.

Just let me note that I think the first one, as it is more open to future evolution in the ETSI NFV.

There is one point though, which I would like to underline.
Being active in two organizations I know that compared to some other SDOs, ETSI NFV people are not trying to declare a technology as their ownership. It is just the aim to contribute and cooperate in the interest of reliable VNF pools.

Being in the same position as Mehmet is, let me support his view on this as well.

Be goode,

"Esta vez no fallaremos, Doctor Infierno"

Dr Diego R. Lopez
Telefonica I+D

e-mail: diego.r.lopez@telefonica.com
Tel:    +34 913 129 041
Mobile: +34 682 051 091


Este mensaje y sus adjuntos se dirigen exclusivamente a su destinatario, puede contener información privilegiada o confidencial y es para uso exclusivo de la persona o entidad de destino. Si no es usted. el destinatario indicado, queda notificado de que la lectura, utilización, divulgación y/o copia sin autorización puede estar prohibida en virtud de la legislación vigente. Si ha recibido este mensaje por error, le rogamos que nos lo comunique inmediatamente por esta misma vía y proceda a su destrucción.

The information contained in this transmission is privileged and confidential information intended only for the use of the individual or entity named above. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this transmission in error, do not read it. Please immediately reply to the sender that you have received this communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu destinatário, pode conter informação privilegiada ou confidencial e é para uso exclusivo da pessoa ou entidade de destino. Se não é vossa senhoria o destinatário indicado, fica notificado de que a leitura, utilização, divulgação e/ou cópia sem autorização pode estar proibida em virtude da legislação vigente. Se recebeu esta mensagem por erro, rogamos-lhe que nos o comunique imediatamente por esta mesma via e proceda a sua destruição