Re: [vnfpool] New revision of VNFPool Problem Statement posted

[Zu Qiang <[e-mail]>]

Hello, Zongning
                Thanks for updating the draft. I do see this version is much better than the previous version. I have a few clarification questions below:

-          First, there are some existing HA solutions. Can you tell me what is the extra functionalities provided by the VNF Pool? Or the VNF Pool is only another alternative solution? Or are we going to use the existing HA solutions as inputs only?

-          Second, in the early version, you have the interactions between the Pool Managers of different pools and between the Pool Functions of different pools specified, which is removed in this version. Do you see that type of interactions are still needed? And why it is needed?

-          3rd, the VNF set is a new concept. What is the linkage with the proposed VNF Pool architecture?

-          4th, RSerPool is referred by your draft. I assume that VNF Pool will not reused the RSerPool  unchanged. So which part of RSerPool can be reused by VNF Pool?
Thanks.
Have a nice day
Zu Qiang

From: vnfpool [mailto:[e-mail]] On Behalf Of Zongning
Sent: Wednesday, April 09, 2014 11:22 PM
To: [e-mail]
Subject: [vnfpool] New revision of VNFPool Problem Statement posted

Hi, folks,

The new revision (-04) of VNFPool Problem Statement I-D is available on the below page.
https://datatracker.ietf.org/doc/draft-zong-vnfpool-problem-statement/

Here are the major changes:

1)       Clarify VNFPool architecture and intended scope.

1.         Add new section of VNF Pools before the section of Problem. This new section is mainly to outline our scope based on high level description of VNF Pools architecture.

2.         Add text to clarify that we are specifically concerned with reliability (e.g. redundancy model, state sharing) that is managed inside the VNF. We are only concerned with the whole VNF set (or forwarding graph) to the extent that it involves reliability impact on adjacent instances of different VNFs.

3.         We focus on reliability mechanisms based on VNF pool. Other VNF management aspects such as scaling, load balancing are out of scope.

2)       Update terminologies to define Service Control Entity, and delete Pool User as the pool will be internal to VNF only.

3)       Re-arrange the text in section of Problems.

4)       Update text of VNF instance performance degradation in section of Problems.

5)       Update text of Reliable Transport in section of Problems.

6)       Add text to explain why service availability is not in scope in section of Problems.

7)       Re-write the section describing the relationship of VNFPool and SFC.

8)       Add text of transfer of security states in section of Security Consideration.

We hope that the changes have addressed most of the comments, and reflected most of the suggestions during London BoF.

Please review this new revision. Your further comments and suggestions are highly appreciated!

Thanks.

-Ning