<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 12 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:SimSun;
panose-1:2 1 6 0 3 1 1 1 1 1;}
@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:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"\@SimSun";
panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle18
{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;}
--></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="#0563C1" vlink="#954F72">
<div class="WordSection1">
<p class="MsoNormal"><span style="color:#1F497D">Hi Igor,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Before we dive into evaluation of the rules you listed below, I would like to understand whether you are suggesting to enforce the rules or relax the rules/constraints you listed? <o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Could you clarify it?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Thanks,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="color:#1F497D">Cathy<o:p></o:p></span></p>
<p class="MsoNormal"><span style="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 style="font-size:10.0pt;font-family:"Tahoma","sans-serif"">From:</span></b><span style="font-size:10.0pt;font-family:"Tahoma","sans-serif""> Duarte Cardoso, Igor [mailto:igor.duarte.cardoso@intel.com]
<br>
<b>Sent:</b> Monday, February 13, 2017 11:12 AM<br>
<b>To:</b> OpenStack Development Mailing List (not for usage questions)<br>
<b>Subject:</b> [openstack-dev] [networking-sfc] What resources can and can't be reused<o:p></o:p></span></p>
</div>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">Hi networking-sfc,<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">As part of my work regarding SFC Encapsulation and SFC Graphs, I exercised the API to understand exactly what resources can be reused, to possibly relax a few of the constraints when a chain is encapsulated end-to-end.<o:p></o:p></p>
<p class="MsoNormal">I’m requesting that the leaders and cores take a look at the list below, and reply if you see something that doesn’t look quite right (or have any other comment/question). Thanks!<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal">1. Every flow-classifier must have a logical source port.<o:p></o:p></p>
<p class="MsoNormal">2. The flow-classifier must be unique in its (full) definition.<o:p></o:p></p>
<p class="MsoNormal">3. A port-chain can have multiple flow-classifiers associated with exactly the same definition BUT different logical source ports.<o:p></o:p></p>
<p class="MsoNormal">4. The port-chains can be ambiguous, i.e. match on the same classification criteria, if and only if there are 0 flow classifiers associated.<o:p></o:p></p>
<p class="MsoNormal">5. The flow classifiers can only be used once, by a single port-chain.<o:p></o:p></p>
<p class="MsoNormal">6. Different port-chains cannot be associated to different flow classifiers that specify the same classification criteria BUT different logical source ports (this is
<a href="https://bugs.launchpad.net/networking-sfc/+bug/1638421">https://bugs.launchpad.net/networking-sfc/+bug/1638421</a>).<o:p></o:p></p>
<p class="MsoNormal">7. A port-pair's ingress cannot be in use by another port-pair's ingress.<o:p></o:p></p>
<p class="MsoNormal">8. A port-pair's egress cannot be in use by another port-pair's egress.<o:p></o:p></p>
<p class="MsoNormal">9. A port-pair can be associated to another port-pair's ingress and egress ports BUT swapped (i1=e2, e1=i2).<o:p></o:p></p>
<p class="MsoNormal">10. The port-pairs become "in use" when a port-pair-group associates them, so they can't be reused across port-pair-groups.<o:p></o:p></p>
<p class="MsoNormal">11. A port-chain can include port-pair-groups already associated to other port-chains, as long as not the exact same sequence as another port-chain (e.g. pc1: [ppg1,ppg2]; pc2: [ppg1] - is fine).<o:p></o:p></p>
<p class="MsoNormal"><o:p> </o:p></p>
<p class="MsoNormal"><span lang="EN-IE">Best regards,<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="EN-IE">Igor.<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</body>
</html>