[vnfpool] 答复: draft-zong-vnfpool-problem-statement
Zongning <zongning@huawei.com> Fri, 30 May 2014 00:24 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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D5F61A06D5 for <vnfpool@ietfa.amsl.com>; Thu, 29 May 2014 17:24:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.902
X-Spam-Level:
X-Spam-Status: No, score=-98.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, MIME_8BIT_HEADER=0.3, MIME_CHARSET_FARAWAY=2.45, 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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id VsPZAisVlYZR for <vnfpool@ietfa.amsl.com>; Thu, 29 May 2014 17:24:46 -0700 (PDT)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 51DF11A02B5 for <vnfpool@ietf.org>; Thu, 29 May 2014 17:24:45 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml203-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BER54276; Fri, 30 May 2014 00:24:40 +0000 (GMT)
Received: from LHREML406-HUB.china.huawei.com (10.201.5.243) by lhreml203-edg.huawei.com (172.18.7.221) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 30 May 2014 01:24:04 +0100
Received: from NKGEML404-HUB.china.huawei.com (10.98.56.35) by lhreml406-hub.china.huawei.com (10.201.5.243) with Microsoft SMTP Server (TLS) id 14.3.158.1; Fri, 30 May 2014 01:24:39 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml404-hub.china.huawei.com ([10.98.56.35]) with mapi id 14.03.0158.001; Fri, 30 May 2014 08:24:33 +0800
From: Zongning <zongning@huawei.com>
To: "King, Daniel" <d.king@lancaster.ac.uk>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: [vnfpool] draft-zong-vnfpool-problem-statement
Thread-Index: Ac97bdRZMy1+5H4SSfyXjz1DZV0vswALuTFg
Date: Fri, 30 May 2014 00:24:31 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC6667796613ECC8@nkgeml501-mbs.china.huawei.com>
References: <65174429B5AF4C45BD0798810EC48E0A3234CB1C@EX-0-MB2.lancs.local>
In-Reply-To: <65174429B5AF4C45BD0798810EC48E0A3234CB1C@EX-0-MB2.lancs.local>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.54]
Content-Type: text/plain; charset="gb2312"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/6z-PI-_M910gQUSXB8WYAFFTEvk
Subject: [vnfpool] 答复: draft-zong-vnfpool-problem-statement
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: Fri, 30 May 2014 00:24:47 -0000
Hi, Dan, Thanks for reading through the draft. See inline. Just have a few comments/questions/observations: Terminology - Where did you derive the term "Service Control Entity", is this an ETSI NFV term? Also once it's used/expanded, suggest using the acronym instead of full term (there are 18 instances). [Ning] I don't think it is ETSI NFV term. But I believe it is a general term with some well-known examples such as orchestrator, SFC control element, etc. Introduction - It might be worth breaking the questions into bullets, rather than the current (forth) paragraph. Perhaps it has been a long day but I had to read twice to parse all the discussion points. [Ning] Good suggestion. Will do in next revision. VNF Set - Figure 2 and Figure 3 show "data conn", is this user data or signal/control data? [Ning] they are user data. Management Considerations - The document discusses security considerations, it might also benefit from discussion management and operational aspects as well. [Ning] Yes, we will document (VNF Pool) management considerations. References - The I-D refers to the first version of the ETSI NFV White Paper, maybe update to reference the second (2013) version? [Ning] Will do. Br, Dan. -Ning