<div dir="ltr" class="gmail_msg">Also, for TAP devices, they can be deployed in both active ( forward traffic back to networking devices) and passive mode . Our *current BP* scope is only for passive TAP. Apart from these two, there are other mode of deployment s also.</div><div dir="ltr" class="gmail_msg"> </div><div dir="ltr" class="gmail_msg">Others reading can add.</div><span class="gmail_msg">
</span><br class="gmail_msg"><div class="gmail_quote gmail_msg"><div dir="ltr" class="gmail_msg">On Tue, Mar 21, 2017, 11:16 PM Vikash Kumar <<a href="mailto:vikash.kumar@oneconvergence.com" class="gmail_msg" target="_blank">vikash.kumar@oneconvergence.com</a>> wrote:<br class="gmail_msg"></div><blockquote class="gmail_quote gmail_msg" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="gmail_msg"><div class="gmail_default gmail_msg" style="font-family:verdana,sans-serif"><div class="gmail_default gmail_msg" style="font-family:verdana,sans-serif">Hi Igor,<br class="gmail_msg"><br class="gmail_msg"></div> <br class="gmail_msg"></div><div class="gmail_extra gmail_msg"><br class="gmail_msg"><div class="gmail_quote gmail_msg"></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg">On Tue, Mar 21, 2017 at 10:02 PM, Duarte Cardoso, Igor <span dir="ltr" class="gmail_msg"><<a href="mailto:igor.duarte.cardoso@intel.com" class="gmail_msg" target="_blank">igor.duarte.cardoso@intel.com</a>></span> wrote:<br class="gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div lang="EN-US" class="gmail_msg">
<div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678WordSection1 gmail_msg">
<p class="MsoNormal gmail_msg"><a name="m_-8096211857411928421_m_1995629119392269188_m_-4252920224941825971_m_-5810197258979053678__MailEndCompose" class="gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">Hi Vikash,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></a></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">It’s best to start with RFC 7665.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">NSH decouples traffic forwarding from both the internals of packets and service functions. A special entity called SFF will take on that job. L2/L3 then become
something that the SFF might have to deal with it. </span></p></div></div></blockquote></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div style="font-family:verdana,sans-serif;display:inline" class="gmail_default gmail_msg">which means it can co-exist with (L2/L3 insertion mode) and not necessarily mutually exclusive.<br class="gmail_msg"></div> </div></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US" class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678WordSection1 gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">However, networking-sfc API doesn’t expose or require details about individual SFC dataplane elements such as the SFF… it is up to the backend/driver to know those low-level details.</span></p></div></div></blockquote></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div style="font-family:verdana,sans-serif;display:inline" class="gmail_default gmail_msg">Agree.<br class="gmail_msg"></div></div></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US" class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678WordSection1 gmail_msg"><p class="MsoNormal gmail_msg"> </p></div></div></blockquote><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US" class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678WordSection1 gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">NSH doesn’t classify and forward traffic itself. It’s only a header that identifies what and where in the chain the packet belongs to/is (plus other goodies such
as metadata). Classifier will classify, SFF will forward.</span></p></div></div></blockquote></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><div class="gmail_msg"><br class="gmail_msg"><div style="font-family:verdana,sans-serif;display:inline" class="gmail_default gmail_msg"> I was referring to NSH
in totality and not excluding SFF
(<a href="https://tools.ietf.org/html/draft-ietf-sfc-nsh-12" class="gmail_msg" target="_blank">https://tools.ietf.org/html/draft-ietf-sfc-nsh-12</a>). Look like I extended the scope of NSH in term of SFC. </div> </div></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"><blockquote class="gmail_quote gmail_msg" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div lang="EN-US" class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678WordSection1 gmail_msg"><p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">By the way, I left a question on the tap blueprint whiteboard, I’ll copy it here too:<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">“Is there a use case for "tap chains"? I.e. not only you send traffic to your tap function, but then your tap function also sends traffic to a next hop too, so
a full chain starts after traffic gets tapped at the first chain (the first chain also continues).”<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg">I suppose the answer is no since you mentioned “Note - TAP SFs do not forward packet”, but I’m happy to hear extended info about this – from anyone reading.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" lang="EN-IE" class="gmail_msg">Best regards,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" lang="EN-IE" class="gmail_msg">Igor.<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif;color:rgb(31,73,125)" class="gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></span></p>
<p class="MsoNormal gmail_msg"><a name="m_-8096211857411928421_m_1995629119392269188_m_-4252920224941825971_m_-5810197258979053678______replyseparator" class="gmail_msg"></a><b class="gmail_msg"><span style="font-size:11pt;font-family:"calibri",sans-serif" class="gmail_msg">From:</span></b><span style="font-size:11pt;font-family:"calibri",sans-serif" class="gmail_msg"> Vikash Kumar [mailto:<a href="mailto:vikash.kumar@oneconvergence.com" class="gmail_msg" target="_blank">vikash.kumar@oneconvergence.com</a>]
<br class="gmail_msg">
<b class="gmail_msg">Sent:</b> Tuesday, March 21, 2017 3:32 PM<br class="gmail_msg">
<b class="gmail_msg">To:</b> OpenStack Development Mailing List (not for usage questions) <<a href="mailto:openstack-dev@lists.openstack.org" class="gmail_msg" target="_blank">openstack-dev@lists.openstack.org</a>><br class="gmail_msg">
<b class="gmail_msg">Subject:</b> Re: [openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p><div class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-h5 gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-bottom:12pt"><span style="font-family:"verdana",sans-serif" class="gmail_msg">Hi,<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-bottom:12pt"><span style="font-family:"verdana",sans-serif" class="gmail_msg"> Moving definition of SF from port-pair to port-pair-group looks good.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg" style="margin-bottom:12pt"><span style="font-family:"verdana",sans-serif" class="gmail_msg"> TAP is also an insertion mode like L2/L3 but since it simplifies to keep 'tap-enabled' field also in port-pair-group, so it should be fine from implementation
point of view (Note - TAP SFs do not forward packet). TAP enabled and L2/L3 insertion mode should be mutually exclusive.
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-family:"verdana",sans-serif" class="gmail_msg"> According to IETF draft NSH can classify & forward traffic (correct ?) but then the draft assumes uniformity of working of devices (which IMHO refers L3) which doesn't cover the entire use
case. Can insertion mode (L2/L3) & traffic encapsulation(NSH) co-exist also ? <u class="gmail_msg"></u>
<u class="gmail_msg"></u></span></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-family:"verdana",sans-serif" class="gmail_msg"><br class="gmail_msg">
<u class="gmail_msg"></u><u class="gmail_msg"></u></span></p>
</div>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><u class="gmail_msg"></u> <u class="gmail_msg"></u></p>
<div class="gmail_msg">
<p class="MsoNormal gmail_msg">On Mon, Mar 20, 2017 at 11:35 PM, Cathy Zhang <<a href="mailto:Cathy.H.Zhang@huawei.com" class="gmail_msg" target="_blank">Cathy.H.Zhang@huawei.com</a>> wrote:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<blockquote style="border-width:medium medium medium 1pt;border-style:none none none solid;border-color:currentcolor currentcolor currentcolor rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm" class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg">Hi Igor,</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg">Moving the correlation from port-pair to port-pair-group makes sense. In the future I think we should add all new attributes for a SF to port-pair-group-param.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg">But I think L2/L3 is different from encap type NSH or MPLS. An L3 type SF can support either NSH or MPLS. I would suggest the following:</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
port-pair-group (port-pair-group-params):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
insertion-mode:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L2<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L3 (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
Correlation: <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- MPLS<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- NSH<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
tap-enabled:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- False (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- True<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg">Thanks,</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg">Cathy</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span style="color:rgb(31,73,125)" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg">
<div style="border-width:1pt medium medium;border-style:solid none none;border-color:rgb(181,196,223) currentcolor currentcolor;padding:3pt 0cm 0cm" class="gmail_msg">
<p class="MsoNormal gmail_msg"><b class="gmail_msg"><span style="font-size:10pt;font-family:"tahoma",sans-serif" class="gmail_msg">From:</span></b><span style="font-size:10pt;font-family:"tahoma",sans-serif" class="gmail_msg"> Duarte Cardoso, Igor [mailto:<a href="mailto:igor.duarte.cardoso@intel.com" class="gmail_msg" target="_blank">igor.duarte.cardoso@intel.com</a>]
<br class="gmail_msg">
<b class="gmail_msg">Sent:</b> Monday, March 20, 2017 8:02 AM<br class="gmail_msg">
<b class="gmail_msg">To:</b> OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
<b class="gmail_msg">Subject:</b> [openstack-dev] [networking-sfc] About insertion modes and SFC Encapsulation</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg">Hi networking-sfc,<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg">At the latest IRC meeting [1] it was agreed to split TAP from the possible insertion modes (initial spec version [2]).<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg">I took the ARs to propose coexistence of insertion modes, correlation and (now) a new tap-enabled attribute, and send this email about possible directions.<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg">Here are my thoughts, let me know yours:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678m8735276103575523103m-4542994552255199751msolistparagraph gmail_msg">1.<span style="font-size:7pt" class="gmail_msg">
</span>My expectation for future PP and PPG if TAP+insertion modes go ahead and nothing else changes (only relevant details outlined):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
port-pair (service-function-params):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
correlation:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- MPLS<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- None (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
port-pair-group (port-pair-group-params):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
insertion-mode:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L2<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L3 (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
tap-enabled:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- False (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- True<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail-m_-5810197258979053678m8735276103575523103m-4542994552255199751msolistparagraph gmail_msg">2.<span style="font-size:7pt" class="gmail_msg">
</span>What I propose for future PP and PPG (only relevant details outlined):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"> <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
port-pair (service-function-params):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
<remove correlation – reasons outlined in [3] and below><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
port-pair-group (port-pair-group-params):<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
mode:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L2<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- L3 (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- MPLS<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- NSH<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
tap-enabled:<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- False (default)<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg" style="margin-left:36pt">
- True<u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">With what’s proposed in 2.:</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">- every combination will be possible with no clashes and no validation required.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">- port-pair-groups will always group “homogeneous” sets of port-pairs, making load-balacing and next-hop processing simpler and consistent.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">- the “forwarding” details of a Service Function are no longer dictated both by port-pair and port-pair-group, but rather only by port-pair-group.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">Are there any use cases for having next-hop SF candidates (individual port-pairs) supporting different SFC Encapsulation protocols?</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">I understand, however, that removing correlation from port-pairs might not be ideal given that it’s a subtractive API change.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">[1]
<a href="http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-16-17.02.html" class="gmail_msg" target="_blank">
http://eavesdrop.openstack.org/meetings/service_chaining/2017/service_chaining.2017-03-16-17.02.html</a></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">[2]
<a href="https://review.openstack.org/#/c/442195/" class="gmail_msg" target="_blank">https://review.openstack.org/#/c/442195/</a></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">[3]
<a href="https://github.com/openstack/networking-sfc/blob/17c537b35d41a3e1fd80da790ae668e52cea6b88/doc/source/system_design%20and_workflow.rst#usage" class="gmail_msg" target="_blank">
https://github.com/openstack/networking-sfc/blob/17c537b35d41a3e1fd80da790ae668e52cea6b88/doc/source/system_design%20and_workflow.rst#usage</a></span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg"> </span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">Best regards,</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<p class="MsoNormal gmail_msg"><span lang="EN-IE" class="gmail_msg">Igor.</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div>
<p class="MsoNormal gmail_msg" style="margin-bottom:12pt"><br class="gmail_msg">
__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" class="gmail_msg" target="_blank">
OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</blockquote>
</div>
<p class="MsoNormal gmail_msg"><br class="gmail_msg">
<br clear="all" class="gmail_msg">
<br class="gmail_msg">
-- <u class="gmail_msg"></u><u class="gmail_msg"></u></p>
<div class="gmail_msg">
<div class="gmail_msg">
<div class="gmail_msg">
<p class="MsoNormal gmail_msg"><span style="font-family:"trebuchet ms",sans-serif" class="gmail_msg">Regards,</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
<p class="MsoNormal gmail_msg"><span style="font-family:"trebuchet ms",sans-serif" class="gmail_msg">Vikash</span><u class="gmail_msg"></u><u class="gmail_msg"></u></p>
</div>
</div>
</div>
</div>
</div></div></div>
</div>
<br class="gmail_msg">__________________________________________________________________________<br class="gmail_msg">
OpenStack Development Mailing List (not for usage questions)<br class="gmail_msg">
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" class="gmail_msg" target="_blank">OpenStack-dev-request@lists.openstack.org?subject:unsubscribe</a><br class="gmail_msg">
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" class="gmail_msg" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br class="gmail_msg">
<br class="gmail_msg"></blockquote></div></div></div><div dir="ltr" class="gmail_msg"><div class="gmail_extra gmail_msg"><div class="gmail_quote gmail_msg"></div><br class="gmail_msg"><br clear="all" class="gmail_msg"><br class="gmail_msg">-- <br class="gmail_msg"><div class="m_-8096211857411928421m_1995629119392269188m_-4252920224941825971gmail_signature gmail_msg"><div dir="ltr" class="gmail_msg"><div class="gmail_msg"><span style="font-family:trebuchet ms,sans-serif" class="gmail_msg">Regards,<br class="gmail_msg"></span></div><span style="font-family:trebuchet ms,sans-serif" class="gmail_msg">Vikash</span><br class="gmail_msg"></div></div>
</div></div>
</blockquote></div>