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

[Zongning <[e-mail]>]

Hi, Namgon,

Please see inline.

From: vnfpool [mailto:[e-mail]] On Behalf Of ???(Cloud Application Project)
Sent: Thursday, January 16, 2014 8:56 AM
To: [e-mail]
Cc: 이광국(Network Innovation Projec); 김남곤(Cloud Application Project)
Subject: Re: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt

Hi,

This new problem statement looks changed a lot from previous version.

Here’s my questions about the draft.

First, how about adding the definition of network service to the terminology section?

[Ning] Sure.

As this draft uses the term “service” without definition, it was not easy for me to understand how VNFs are related to a network service.

[Ning] VNFs are building blocks of a network service. A simple example is a web browsing service that may include NAT/packet filter, parental control, server load balancer, etc.

For example, in Section 3, there are two states.
One in “3.  State notification across VNF set.” and the other in “4. Service state synchronization”.
I just guess the former one means state of a VNF and latter one means service itself.

[Ning] The latter one is the state maintained by a VNF, but related to the specific function it performs, such as NAT translation table, TCP connection states. The former one is the state of VNF itself, such as overload status. Sorry for the confusion. I will give more explanation in next revision.

Second, is the interaction between VNF pool manager and VNF pool user out of scope?
It could be possible that a VNF user receive information from VNF pool manager and update/control policy based on the state.
And this can be applied to service function chaining, like choosing another service function chain, if we think of a VNF pool user as an entity controlling service function chaining.

[Ning] We don’t exclude the interface between pool manager and user (please see item#4 in Section 4). What you have pointed is a good case to add, especially complementary to SFC.

Lastly, could anyone let me know the relation between service function chaining (sfc) and vnfpool?
The scope of vnfpool compared to sfc and how the two can interface with each other.
If it was discussed before, simply tell me the link.

[Ning] We believe VNF pool and SFC are independent but complementary. Please see item#3 in Section 5. Also we have previous list discussions, e.g., http://www.ietf.org/mail-archive/web/vnfpool/current/msg00091.html

Thank you.

Yours,
- Namgon

---------- Forwarded message ----------
From: Zongning <[e-mail]<mailto:[e-mail]>>
Date: 2014/1/14
Subject: [vnfpool] FW: New Version Notification for draft-zong-vnfpool-problem-statement-02.txt
To: "[e-mail]<mailto:[e-mail]>" <[e-mail]<mailto:[e-mail]>>


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: [e-mail]<mailto:[e-mail]> [mailto:[e-mail]<mailto:[e-mail]>]
> 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<http://tools.ietf.org>.
>
> The IETF Secretariat

_______________________________________________
vnfpool mailing list
[e-mail]<mailto:[e-mail]>
https://www.ietf.org/mailman/listinfo/vnfpool



이 메일은 지정된 수취인만을 위해 작성되었으며, 중요한 정보나 저작권을 포함하고 있을 수 있습니다. 어떠한 권한 없이, 본 문서에 포함된 정보의 전부 또는 일부를 무단으로 제3자에게 공개, 배포, 복사 또는 사용하는 것을 엄격히 금지합니다. 만약, 본 메일이 잘못 전송된 경우, 발신인 또는 당사에 알려주시고, 본 메일을 즉시 삭제하여 주시기 바랍니다.
This E-mail may contain confidential information and/or copyright material. This email is intended for the use of the addressee only. If you receive this email by mistake, please either delete it without reproducing, distributing or retaining copies thereof or notify the sender immediately.