[vnfpool] 答复: New version of draft-xia-vnfpool-use-cases

Zongning <zongning@huawei.com> Mon, 19 May 2014 09:31 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 F1D621A032F for <vnfpool@ietfa.amsl.com>; Mon, 19 May 2014 02:31:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -98.901
X-Spam-Level:
X-Spam-Status: No, score=-98.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, CHARSET_FARAWAY_HEADER=3.2, HTML_MESSAGE=0.001, 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 UFuFO9VuJdRI for <vnfpool@ietfa.amsl.com>; Mon, 19 May 2014 02:31:37 -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 E1E9E1A02BE for <vnfpool@ietf.org>; Mon, 19 May 2014 02:31:36 -0700 (PDT)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg02-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BEH28665; Mon, 19 May 2014 09:31:35 +0000 (GMT)
Received: from LHREML403-HUB.china.huawei.com (10.201.5.217) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 19 May 2014 10:31:14 +0100
Received: from nkgeml407-hub.china.huawei.com (10.98.56.38) by lhreml403-hub.china.huawei.com (10.201.5.217) with Microsoft SMTP Server (TLS) id 14.3.158.1; Mon, 19 May 2014 10:31:17 +0100
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.193]) by nkgeml407-hub.china.huawei.com ([10.98.56.38]) with mapi id 14.03.0158.001; Mon, 19 May 2014 17:31:11 +0800
From: Zongning <zongning@huawei.com>
To: "King, Daniel" <d.king@lancaster.ac.uk>, "vnfpool@ietf.org" <vnfpool@ietf.org>
Thread-Topic: New version of draft-xia-vnfpool-use-cases
Thread-Index: Ac9wc2CPy3UHIpkYSk2Qt78Kr/HT+gCzzgtQ
Date: Mon, 19 May 2014 09:31:10 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC6667796612992C@nkgeml501-mbs.china.huawei.com>
References: <65174429B5AF4C45BD0798810EC48E0A32347741@EX-0-MB2.lancs.local>
In-Reply-To: <65174429B5AF4C45BD0798810EC48E0A32347741@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: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC6667796612992Cnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: http://mailarchive.ietf.org/arch/msg/vnfpool/xP4eyg1L0mTS4F9FOJMGlEDsqAk
Subject: [vnfpool] =?gb2312?b?tPC4tDogTmV3IHZlcnNpb24gb2YgZHJhZnQteGlhLXZu?= =?gb2312?b?ZnBvb2wtdXNlLWNhc2Vz?=
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, 19 May 2014 09:31:40 -0000

Hi, Dan, and other co-authors,

Thank you for the update. I see a lot of improvement since the last version, e.g. alignment with PS I-D on terminologies, more focused use cases.

I have some minor comments as below:

1)       In Terminology Section, ¡°STB¡± and ¡°Virtual Application¡± are defined by NOT used in the draft.

2)       In Figure 1 ¡°VNF Pool Network Architecture¡±, different pools seem to have same ¡°VNF instance¡±. Is this depicted by purpose? Or we could use ¡°VNF#1 instance¡± in one pool, ¡°VNF#2 instance¡± in another pool, and so on?

3)       In Section 3.1, I am not sure I understand the term ¡°VNF-based nodes¡±.

Other general suggestions (but surely these can be done in the near future/longer term, rather than in this version :))

1)       We may have separated sections - one for a variety of use cases, another for a list of requirements.

2)       We still need more use cases for ¨C 1) VNF pool combining both virtual and non-virtual functional instances; 2) VNF pool using different VNF components;

3)       We need more details about service state synchronization, in order to identify clear requirements on protocols, if supported by multi-vendors.

Thanks.

-Ning

·¢¼þÈË: vnfpool [mailto:vnfpool-bounces@ietf.org] ´ú±í King, Daniel
·¢ËÍʱ¼ä: 2014Äê5ÔÂ16ÈÕ 3:28
ÊÕ¼þÈË: vnfpool@ietf.org
Ö÷Ìâ: [vnfpool] New version of draft-xia-vnfpool-use-cases

Hi All,

As recently mentioned we planned to issue a new version of the general requirements and use case document. This may now be found in various flavours via:

URL: http://www.ietf.org/internet-drafts/draft-xia-vnfpool-use-cases-01.txt
Status: https://datatracker.ietf.org/doc/draft-xia-vnfpool-use-cases
Htmlized: http://tools.ietf.org/html/draft-xia-vnfpool-use-cases-01
Diff: http://www.ietf.org/rfcdiff?url2=draft-xia-vnfpool-use-cases-01

Please review and comment on the list, or if you are shy, the authors (myself included) directly.

We are just collating the final comments for the Mobile Use Case I-D and will submit a new version shortly(TM).

Br, Dan (and the other authors).