Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt

Zongning <zongning@huawei.com> Sat, 18 January 2014 01: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 DBD781ACCFD for <vnfpool@ietfa.amsl.com>; Fri, 17 Jan 2014 17:31:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -104.138
X-Spam-Level:
X-Spam-Status: No, score=-104.138 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_72=0.6, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.538, 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 e0RBpsyCuoBy for <vnfpool@ietfa.amsl.com>; Fri, 17 Jan 2014 17:31:20 -0800 (PST)
Received: from lhrrgout.huawei.com (lhrrgout.huawei.com [194.213.3.17]) by ietfa.amsl.com (Postfix) with ESMTP id 57A921ACCDF for <vnfpool@ietf.org>; Fri, 17 Jan 2014 17:31:19 -0800 (PST)
Received: from 172.18.7.190 (EHLO lhreml204-edg.china.huawei.com) ([172.18.7.190]) by lhrrg01-dlp.huawei.com (MOS 4.3.7-GA FastPath queued) with ESMTP id BCP60593; Sat, 18 Jan 2014 01:31:06 +0000 (GMT)
Received: from LHREML405-HUB.china.huawei.com (10.201.5.242) by lhreml204-edg.china.huawei.com (172.18.7.223) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:30:15 +0000
Received: from NKGEML410-HUB.china.huawei.com (10.98.56.41) by lhreml405-hub.china.huawei.com (10.201.5.242) with Microsoft SMTP Server (TLS) id 14.3.158.1; Sat, 18 Jan 2014 01:31:04 +0000
Received: from NKGEML501-MBS.china.huawei.com ([169.254.2.56]) by nkgeml410-hub.china.huawei.com ([10.98.56.41]) with mapi id 14.03.0158.001; Sat, 18 Jan 2014 09:31:02 +0800
From: Zongning <zongning@huawei.com>
To: LAC Chidung <chidung.lac@orange.com>
Thread-Topic: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt
Thread-Index: AQHPEMZ+c15+lVuknkS7yKxzUMJky5qDbBOggAU1VYCAAQ4yMA==
Date: Sat, 18 Jan 2014 01:31:01 +0000
Message-ID: <B0D29E0424F2DE47A0B36779EC66677925867CCE@nkgeml501-mbs.china.huawei.com>
References: <B0D29E0424F2DE47A0B36779EC66677925866ACB@nkgeml501-mbs.china.huawei.com> <52D95FD9.7010603@orange.com>
In-Reply-To: <52D95FD9.7010603@orange.com>
Accept-Language: en-US, zh-CN
Content-Language: zh-CN
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.138.41.28]
Content-Type: multipart/alternative; boundary="_000_B0D29E0424F2DE47A0B36779EC66677925867CCEnkgeml501mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Cc: "vnfpool@ietf.org" <vnfpool@ietf.org>
Subject: Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt
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: Sat, 18 Jan 2014 01:31:24 -0000

Hi, Chidung,

Really appreciate your inline suggestions + comments. While we will adopt most of your suggestions, I'd like to answer several of your questions at first, to make sure we are more align with each other. :)


[CL1]: Besides section 5 (Related Works), the word « availability »  is not used at all in this doc ... although it is the main objective of the pooling architecture, i.e., providing redundant VNF instances in order to maximize the network service's availability
You are right that the goal of VNF pool is to improve the service's availability, from the service(or user) perspective. IMHO, I prefer not to address the problem from service(or user) perspective, but simply from the VNF set itself. Another word, we may just focus how to use pooling mechanisms, e.g. redundancy model, stateful failover to improve the reliability of VNF set. But we could definitely mention that our work will benefit service availability. How do you think?

[CL2]: "A VNF set can introduce additional points of failure beyond those inherent in a single specialized server" - this sentence implies that a "single specialized server" currently hosts different NFs which will be virtualized in the future and  grouped in a "VNF set": is it really what we mean ?

No, we don't mean that VNF set is "released" from a single specialized server. The challenges are: 1) a single VNF may have more factors of risk than a traditional NF in single specialized server; 2) a group of VNFs need more coordination on reliability. I agree that comparing a VNF set to a single specialized server may be inappropriate. I will revise the sentence later.

[CL4]: "Load Sharing" - it is rather a performance mechanism (and not a reliability one).

I'd still think load sharing is not only for performance, but related to reliability, considering that potential overload will affect the reliability of VNF without applying efficient load sharing.

Again, thanks for your careful & kind inline editing.

-Ning

From: LAC Chidung [mailto:chidung.lac@orange.com]
Sent: Saturday, January 18, 2014 12:53 AM
To: Zongning
Cc: vnfpool@ietf.org
Subject: Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt

Hi Ning,
Some cosmetic suggestions + comments.
Best,
Chidung
Le 14/01/2014 02:24, Zongning a écrit :

Hi, folks,

Happy new year!

We made a new revision of VNF Pool Problem Statement. Please see the below abstract and links:



Abstract:

   There is a trend to implement network services by using a group of

   Virtualized Network Functions (VNFs) called a VNF set.  A VNF set can

   offer benefits like flexible service provisioning.  A VNF set also

   introduces additional points of failure, and therefore poses

   additional challenges on reliability.



   This document overviews the problems related to the reliability of a

   VNF set.  A VNF pooling architecture is also briefly introduced as

   candidate solution to address the problems.



URL:            http://www.ietf.org/internet-drafts/draft-zong-vnfpool-problem-statement-02.txt

Htmlized:       http://tools.ietf.org/html/draft-zong-vnfpool-problem-statement-02



Other related drafts including VNF Pool Use Cases, VNF Pooling Architecture are under development and will be available soon in this month...

Thanks.

-Ning



-----Original Message-----

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org> [mailto:internet-drafts@ietf.org]

Sent: Tuesday, January 14, 2014 9:18 AM

To: Zongning; Linda Dunbar; Melinda Shore; Linda Dunbar; Melinda Shore;

Diego Lopez; Diego R. Lopez; Zongning

Subject: New Version Notification for

draft-zong-vnfpool-problem-statement-02.txt



A new version of I-D, draft-zong-vnfpool-problem-statement-02.txt

has been successfully submitted by Ning Zong and posted to the

IETF repository.



Name:             draft-zong-vnfpool-problem-statement

Revision: 02

Title:            Virtualized Network Function (VNF) Pool Problem Statement

Document date:    2014-01-14

Group:            Individual Submission

Pages:            10

URL:

http://www.ietf.org/internet-drafts/draft-zong-vnfpool-problem-statement-02.

txt

Status:

https://datatracker.ietf.org/doc/draft-zong-vnfpool-problem-statement/

Htmlized:

http://tools.ietf.org/html/draft-zong-vnfpool-problem-statement-02

Diff:

http://www.ietf.org/rfcdiff?url2=draft-zong-vnfpool-problem-statement-02



Abstract:

   There is a trend to implement network services by using a group of

   Virtualized Network Functions (VNFs) called a VNF set.  A VNF set can

   offer benefits like flexible service provisioning.  A VNF set also

   introduces additional points of failure, and therefore poses

   additional challenges on reliability.



   This document overviews the problems related to the reliability of a

   VNF set.  A VNF pooling architecture is also briefly introduced as

   candidate solution to address the problems.



Please note that it may take a couple of minutes from the time of submission

until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat

_______________________________________________

vnfpool mailing list

vnfpool@ietf.org<mailto:vnfpool@ietf.org>

https://www.ietf.org/mailman/listinfo/vnfpool

________________________________