<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=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
        {font-family:"MS Gothic";
        panose-1:2 11 6 9 7 2 5 8 2 4;}
@font-face
        {font-family:"Cambria Math";
        panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
        {font-family:Calibri;
        panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
        {font-family:"Segoe UI";
        panose-1:2 11 5 2 4 2 4 2 2 3;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
        {font-family:"\@MS Gothic";
        panose-1:2 11 6 9 7 2 5 8 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","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
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
pre
        {mso-style-priority:99;
        mso-style-link:"HTML Preformatted Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
        {mso-style-priority:34;
        margin-top:0in;
        margin-right:0in;
        margin-bottom:0in;
        margin-left:.5in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.HTMLPreformattedChar
        {mso-style-name:"HTML Preformatted Char";
        mso-style-priority:99;
        mso-style-link:"HTML Preformatted";
        font-family:Consolas;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Segoe UI","sans-serif";}
span.HTMLVorformatiertZchn
        {mso-style-name:"HTML Vorformatiert Zchn";
        mso-style-priority:99;
        mso-style-link:"HTML Vorformatiert";
        font-family:Consolas;}
p.HTMLVorformatiert, li.HTMLVorformatiert, div.HTMLVorformatiert
        {mso-style-name:"HTML Vorformatiert";
        mso-style-priority:99;
        mso-style-link:"HTML Vorformatiert Zchn";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.SprechblasentextZchn
        {mso-style-name:"Sprechblasentext Zchn";
        mso-style-priority:99;
        mso-style-link:Sprechblasentext;
        font-family:"Tahoma","sans-serif";}
p.Sprechblasentext, li.Sprechblasentext, div.Sprechblasentext
        {mso-style-name:Sprechblasentext;
        mso-style-priority:99;
        mso-style-link:"Sprechblasentext Zchn";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
span.EmailStyle27
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle28
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle29
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.EmailStyle30
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
/* List Definitions */
@list l0
        {mso-list-id:641007934;
        mso-list-type:hybrid;
        mso-list-template-ids:-365517594 292871872 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:1.0in;
        text-indent:-.25in;}
@list l0:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:1.5in;
        text-indent:-.25in;}
@list l0:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        margin-left:2.0in;
        text-indent:-9.0pt;}
@list l0:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:2.5in;
        text-indent:-.25in;}
@list l0:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:3.0in;
        text-indent:-.25in;}
@list l0:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        margin-left:3.5in;
        text-indent:-9.0pt;}
@list l0:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:4.0in;
        text-indent:-.25in;}
@list l0:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        margin-left:4.5in;
        text-indent:-.25in;}
@list l0:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        margin-left:5.0in;
        text-indent:-9.0pt;}
@list l1
        {mso-list-id:2009945564;
        mso-list-type:hybrid;
        mso-list-template-ids:1339207426 67698703 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l1:level1
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level2
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level3
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1:level4
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level5
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level6
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
@list l1:level7
        {mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level8
        {mso-level-number-format:alpha-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:left;
        text-indent:-.25in;}
@list l1:level9
        {mso-level-number-format:roman-lower;
        mso-level-tab-stop:none;
        mso-level-number-position:right;
        text-indent:-9.0pt;}
ol
        {margin-bottom:0in;}
ul
        {margin-bottom:0in;}
--></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="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Sorry,
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Meathod-2 & Meathod-3 figures  needs to be  interchanged in this description.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">keshava<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> A, Keshava
<br>
<b>Sent:</b> Friday, January 16, 2015 1:03 PM<br>
<b>To:</b> Yuriy.Babenko@telekom.de; OpenStack Development Mailing List (not for usage questions); mestery@mestery.com<br>
<b>Cc:</b> A, Keshava<br>
<b>Subject:</b> RE: [openstack-dev] [neutron][AdvancedServices] Confusion about the solution of the service chaining!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#70AD47">Hi
</span><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Yuriy Babe</span><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">nko,<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Thanks for sharing information.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">I also have similar personal thoughts with various options as mentioned below.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Ofcourse the ietf service chaning meathod have lot open question we needs to discuss further. This is percived by NFV working
 group also.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Please take a look of hybrid meathod (option-3) as mentioned below also.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><img width="531" height="246" id="_x0000_i1028" src="cid:image001.png@01D03198.25168FD0"></span><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Service-VM:-<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><span style="mso-list:Ignore">a.<span style="font:7.0pt "Times New Roman"">    
</span></span></span><![endif]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">This Service-VM will be devleoped by the individuals or it will be part of the commnity.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l0 level1 lfo2;text-autospace:none">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><span style="mso-list:Ignore">b.<span style="font:7.0pt "Times New Roman"">   
</span></span></span><![endif]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">These Service-VM needs to support, multiple Services A,B,C with in a ServiceVM (vNF1) (because of performance & business scenario)<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Then it is required to chain those Services statically, or dnamically  based on the Tennant
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-indent:.5in;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">requirement.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Since these VMs are  developed by the individuals, chainnig these Services using Neutron controller will be challenging 
 ? How can openstack know which are the Services running in that VM ? <o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:11.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><u><span lang="DE" style="font-size:11.0pt;font-family:"Arial","sans-serif";color:#70AD47">There are 3 method to solve this issues.<o:p></o:p></span></u></b></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-1:  Static Meathod.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-2 : Dynamic meathod, by adding the Service-chian header.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-3:  Hybrid. Static + Dynamic meathod.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-1: Static Meathod.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Requirement:<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Community should defind and develop the Standard Service-API-LIB (Like socket layer. Each Service-VM should attach this
 LIB.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Then using these Service API, Openstack controller (any) can program the Service’s inside the Service-VM according the service
 Chain.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><img width="584" height="551" id="_x0000_i1025" src="cid:image002.png@01D03198.25168FD0"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-2: Dynamic Meathod – using the Service Chain Header (IETF).<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4;text-autospace:none">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><span style="mso-list:Ignore">1.<span style="font:7.0pt "Times New Roman"">    
</span></span></span><![endif]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Service Layer(Archestration Layer) should provide the Service Information (Service, Next/Prev Service, Type, Priotiy, Action .. etc) to Openstack
 Neutron Controller.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4;text-autospace:none">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><span style="mso-list:Ignore">2.<span style="font:7.0pt "Times New Roman"">    
</span></span></span><![endif]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Neutron Controller to program the SFF(Compute node/OVS) to attach all the Service header and each service  IP address .. as per IETF.<o:p></o:p></span></p>
<p class="MsoListParagraph" style="text-indent:-.25in;mso-list:l1 level1 lfo4;text-autospace:none">
<![if !supportLists]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><span style="mso-list:Ignore">3.<span style="font:7.0pt "Times New Roman"">    
</span></span></span><![endif]><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Service Header processing should be handled by the Service-VM.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">When the Tennant traffic enters the OVS/Compute Nodes, based this information, Service Header needs to be attached.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><img width="565" height="507" id="_x0000_i1026" src="cid:image003.png@01D03198.25168FD0"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoListParagraph" style="margin-left:.75in;text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Meathod-3: Hybrid  Meathod.<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">In both of the above meathods, when the packet needs to traver from one Service-VM1(vNF1) to other Service-VM2 (vNF2), it
 always needs travers as vNF1->SFF1->SFF2->vFN2.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">This will be real overhead and adds lot of latency during packet processing<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Instead if SFF1 itself identify which SFF has the next service information, we can avoid the packet traversal across OVS
 .<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">For this happen each Service-VM should have the complete service information under that controller.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Service VM will get Service Information by Service-APIs: This information will be used to forward the packet to Nest SFF.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Service Header (ietf) will be attached by SFF and will be processed by Service-VM.
<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p> </o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><img width="569" height="520" id="_x0000_i1027" src="cid:image004.png@01D03198.25168FD0"><b><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47"><o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">These are my intial thoughts . Please let me know all other thoughts.<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">Regards,<o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#70AD47">keshava<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">
<a href="mailto:Yuriy.Babenko@telekom.de">Yuriy.Babenko@telekom.de</a> [<a href="mailto:Yuriy.Babenko@telekom.de">mailto:Yuriy.Babenko@telekom.de</a>]
<br>
<b>Sent:</b> Wednesday, January 14, 2015 9:33 PM<br>
<b>To:</b> <a href="mailto:openstack-dev@lists.openstack.org">openstack-dev@lists.openstack.org</a>;
<a href="mailto:mestery@mestery.com">mestery@mestery.com</a><br>
<b>Subject:</b> Re: [openstack-dev] [neutron][AdvancedServices] Confusion about the solution of the service chaining!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Hi,
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">we really like the idea to address the SFC use-case in Neutron working group.
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">We would be happy to work with the community to work out the way to consume service-chains via standardized neutron-api and provide use-cases and
 blueprints. <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Some initial ideas on the use-case can be found in the following etherpad [1].
<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><br>
Keshava, we think that it would be ideal to have two type of use-cases: one which you described below (“dynamic” one) with the usage of IETF-defined header but also one “static” one where the whole chain can be pre-provisioned by the orchestrator via Neutron-API
  w/o usage of classifier and header extensions.  <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">[1]
<a href="https://etherpad.openstack.org/p/kKIqu2ipN6">https://etherpad.openstack.org/p/kKIqu2ipN6</a><o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-GB" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Kind regards/Mit freundlichen Grüßen
</span><span lang="EN-GB" style="color:#1F497D"><o:p></o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><span lang="EN-GB" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">Yuriy Babe</span><span lang="DE" style="font-size:10.0pt;font-family:"Arial","sans-serif";color:#1F497D">nko<o:p></o:p></span></p>
</div>
<p class="MsoNormal"><span lang="DE" style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<div>
<div style="border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in">
<p class="MsoNormal"><b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">Von:</span></b><span lang="DE" style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> A, Keshava [<a href="mailto:keshava.a@hp.com">mailto:keshava.a@hp.com</a>]
<br>
<b>Gesendet:</b> Donnerstag, 8. Januar 2015 07:19<br>
<b>An:</b> <a href="mailto:mestery@mestery.com">mestery@mestery.com</a>; OpenStack Development Mailing List (not for usage questions)<br>
<b>Betreff:</b> Re: [openstack-dev] [neutron][AdvancedServices] Confusion about the solution of the service chaining!<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><span lang="DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Yes, I agree with Kyle decision.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">First we should define what is Service.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Service is within OpenStack infrastructure ? or Service belongs  to NFV vNF/Service-VM ?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">Based on that its Chaining needs to be defined.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">If it is chaining of vNFs(which are service/set of services)  then it  will be based on ietf  ‘service header insertion’ at the ingress.
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">This header will have all the set services  that needs to be executed  across vNFV, will be carried in each of the Tennant packet.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">So it requires coordinated effort along with NFV/Telco  working groups.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D">keshava<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif"">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri","sans-serif""> Kyle Mestery [<a href="mailto:mestery@mestery.com">mailto:mestery@mestery.com</a>]
<br>
<b>Sent:</b> Wednesday, January 07, 2015 8:25 PM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> Re: [openstack-dev] [neutron][AdvancedServices] Confusion about the solution of the service chaining!<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">On Wed, Jan 7, 2015 at 6:25 AM, <<a href="mailto:lv.erchun@zte.com.cn" target="_blank">lv.erchun@zte.com.cn</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p class="MsoNormal"><span style="font-family:"Arial","sans-serif"">Hi,</span> <o:p>
</o:p></p>
<p><span style="font-family:"Arial","sans-serif"">I want to confirm that how is the project about "Neutron Services Insertion, Chaining, and Steering" going, I found that all the code implementation about service insertion</span><span style="font-family:"MS Gothic"">、</span><span style="font-family:"Arial","sans-serif"">service
 chaining and traffic steering list in JunoPlan were Abandoned .</span> <o:p></o:p></p>
<p><a href="https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan" target="_blank"><span style="font-family:"Arial","sans-serif"">https://wiki.openstack.org/wiki/Neutron/AdvancedServices/JunoPlan</span></a>
<o:p></o:p></p>
<p><span style="font-family:"Arial","sans-serif"">and I also found that we have a new project about GBP and group-based-policy-service-chaining be located at:</span>
<o:p></o:p></p>
<p><a href="https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-abstraction" target="_blank"><span style="font-family:"Arial","sans-serif"">https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-abstraction</span></a>
<o:p></o:p></p>
<p><a href="https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-service-chaining" target="_blank"><span style="font-family:"Arial","sans-serif"">https://blueprints.launchpad.net/group-based-policy/+spec/group-based-policy-service-chaining</span></a>
<o:p></o:p></p>
<p style="margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif"">so I'm confused with solution of the service chaining.</span>
<br>
<br>
<span style="font-family:"Arial","sans-serif"">We are developing the service chaining feature, so we need to know which one is the neutron's choice. Are the blueprints about the service insertion, service chaining and traffic steering list in JunoPlan all Abandoned
 ? </span><o:p></o:p></p>
</blockquote>
<div>
<p class="MsoNormal">Service chaining isn't in the plan for Kilo [1], but I expect it to be something we talk about in Vancouver for the Lxxx release. The NFV/Telco group has been talking about this as well. I'm hopeful we can combine efforts and come up with
 a coherent service chaining solution that solves a handful of useful use cases during Lxxx.<br>
<br>
Thanks,<br>
Kyle<br>
<br>
[1] <a href="http://specs.openstack.org/openstack/neutron-specs/priorities/kilo-priorities.html">
http://specs.openstack.org/openstack/neutron-specs/priorities/kilo-priorities.html</a>
<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<p style="margin-bottom:12.0pt"><span style="font-family:"Arial","sans-serif"">BR</span>
<br>
<span style="font-family:"Arial","sans-serif"">Alan</span> <o:p></o:p></p>
<pre><span style="font-size:10.0pt;font-family:"Courier New";color:blue"><o:p> </o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New";color:blue">--------------------------------------------------------<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New";color:blue">ZTE Information Security Notice: The information contained in this mail (and any attachment transmitted herewith) is privileged and confidential and is intended for the exclusive use of the addressee(s).  If you are not an intended recipient, any disclosure, reproduction, distribution or other dissemination or use of the information contained is strictly prohibited.  If you have received this mail in error, please delete it and notify us immediately.<o:p></o:p></span></pre>
<pre><span style="font-size:10.0pt;font-family:"Courier New";color:blue"><o:p> </o:p></span></pre>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</body>
</html>