unknown
1970-01-01 00:00:00 UTC
This would mean that each VNFPool provides a self-contained function, e.g. firewall, web-service, etc.
There is no functional dependency between VNFs of different Pools. Is this understanding correct?
My understanding of how a virtualized network function vNF is built is that it comprises multiple
vNF Components (vNFC) of the same (for function-internal load balancing) and of different types.
Each vNFC is instantiated in a separate virtual machine.
I am still not sure how to reflect this in VNFPool: It may be details that hide inside a VNF as e.g. depicted in
Fig. 1. In such case, the function-internal architecture made from different vNFCs is not visible to VNFPool.
In case VNFPool is concerned with the function-internal architecture made from different vNFCs, Section 3.2
may include such figure:
+---------+
| VNF-C#z |
| |
+---------+
^ |
| |
| |
| v
+---------+ +---------+
| VNF-A#x |<------| VNF-B#y |
| |------>| |
+---------+ +---------+
^
|
|
|
v
+---------+
| Client |
+---------+
Sorry that I come up with this request for clarification again.
Best regards,
marco
--_000_69756203DDDDE64E987BC4F70B71A26D6987A833PALLENEofficehd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi Ning, all,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">please find some more feedback to the 4th revision of the VNFPool PS draft below. It's more<br>
about a clarification before I can send more detailed comments on the draft. <o:p>
</o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The draft clarifies about the technical scope, which I understand is limited to redundancy management<br>
and failover handling within a group of VNFs of the same type, the VNF set.<br>
To coordinate between functions of different pools, the draft introduces the Service Control Entity.<br>
<br>
<o:p></o:p></p>
<p class="MsoPlainText">Does the Service Control Entity play a role in building a single network function, e.g. a firewall,<br>
from function instances of different pools? <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It does not play a role if the complete firewall functionality is provided by a single VNF of a single Pool.
<o:p></o:p></p>
<p class="MsoPlainText">Is this the assumption for VNFPool?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">
There is no functional dependency between VNFs of different Pools. Is this understanding correct?
My understanding of how a virtualized network function vNF is built is that it comprises multiple
vNF Components (vNFC) of the same (for function-internal load balancing) and of different types.
Each vNFC is instantiated in a separate virtual machine.
I am still not sure how to reflect this in VNFPool: It may be details that hide inside a VNF as e.g. depicted in
Fig. 1. In such case, the function-internal architecture made from different vNFCs is not visible to VNFPool.
In case VNFPool is concerned with the function-internal architecture made from different vNFCs, Section 3.2
may include such figure:
+---------+
| VNF-C#z |
| |
+---------+
^ |
| |
| |
| v
+---------+ +---------+
| VNF-A#x |<------| VNF-B#y |
| |------>| |
+---------+ +---------+
^
|
|
|
v
+---------+
| Client |
+---------+
Sorry that I come up with this request for clarification again.
Best regards,
marco
--_000_69756203DDDDE64E987BC4F70B71A26D6987A833PALLENEofficehd_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Word 14 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoPlainText">Hi Ning, all,<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">please find some more feedback to the 4th revision of the VNFPool PS draft below. It's more<br>
about a clarification before I can send more detailed comments on the draft. <o:p>
</o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">The draft clarifies about the technical scope, which I understand is limited to redundancy management<br>
and failover handling within a group of VNFs of the same type, the VNF set.<br>
To coordinate between functions of different pools, the draft introduces the Service Control Entity.<br>
<br>
<o:p></o:p></p>
<p class="MsoPlainText">Does the Service Control Entity play a role in building a single network function, e.g. a firewall,<br>
from function instances of different pools? <o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">It does not play a role if the complete firewall functionality is provided by a single VNF of a single Pool.
<o:p></o:p></p>
<p class="MsoPlainText">Is this the assumption for VNFPool?<o:p></o:p></p>
<p class="MsoPlainText"><o:p> </o:p></p>
<p class="MsoPlainText">