<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Ben, <br>
</p>
<p>Thank you very much for your answers. I have some comments that
you can find inline.</p>
<p>Again, thank you very much for your time and attention.<br>
</p>
<p>Regards,</p>
<p>Jordi<br>
</p>
<div class="moz-cite-prefix">On 19/11/2020 18:35, Ben Pfaff wrote:<br>
</div>
<blockquote type="cite" cite="mid:20201119173541.GN3324419@ovn.org">
<pre class="moz-quote-pre" wrap="">On Thu, Nov 19, 2020 at 12:20:01PM +0100, Jordi Baranda wrote:
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">If I use break-before-make, there is no problem because I replace the rules
and that is. However for the make-before-break approach, I foresee that there
will be some flow rules with the same match fields but different action
fields. (e.g, t0: in_port: 3 -> out_port: 2 vs t1: in_port: 3 -> out_port:4,
where t0 means time0 and t1 means time1 and t1 > t0 (older time instant) ). I
know I could handle that with priorities but I think this may add further
complexity to the SDN controller app.
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I don't think this makes any sense. You cannot have two flows in a
table with the same match fields and the same priority. Those are the
same flow, and it has either one set of actions or another.</pre>
</blockquote>
<font color="#008000">Yes, I understand. These entries will coexist
for short time due to the make-before-break approach. I will
install the "new rule" with the same match and different action
and then remove the "old rule". My question as you well described
bellow is what happens while they coexist.</font><br>
<blockquote type="cite" cite="mid:20201119173541.GN3324419@ovn.org">
<pre class="moz-quote-pre" wrap="">
</pre>
<blockquote type="cite">
<pre class="moz-quote-pre" wrap="">I am wondering if I can skip this treatment at the SDN controller app making
use of how OVS applies/evaluates rules in the flow table. More specifically,
rules in the flow table of OVS (for the same priority) are evaluated in any
time order? That is, OVS is considering "t1 rule" (which is more recent than
the one of t0) before than "t0 rule" (however, t0 rule will be erased
afterwards)? Or are the flow-rules in the flow table ordered/evaluated
"randomly"? Additionally, has this changed through the OVS versions?
</pre>
</blockquote>
<pre class="moz-quote-pre" wrap="">
I'm not sure I understand the question. Skipping by the problem above,
let me rephrase my understanding of it in another way, and you can
correct me if I get it wrong. I think you are saying, if a given packet
has two "best match" flows at the same priority, will OVS choose the one
added later by preference? No, OVS doesn't work that way; it has never
used the order in which flows are added as an input into the
classification process.</pre>
</blockquote>
<p><font color="#008000">Yes, the problem is as you described. While
the rules coexists, which one will be applied? According to what
I read, I suppose OVS checks the rules in the flow table and
applies the first one making match. However, as I understand,
OVS is not applying "any given order" to evaluate the rules in
the flow-table, it could be that sometimes applies one rule and
other time applies the other rule. Is my understanding correct?
I have found a thread in stackoverflow asking about the same <a
moz-do-not-send="true"
href="https://stackoverflow.com/questions/45195182/what-if-there-are-multiple-forwarding-rules-for-the-same-flow-in-the-openflow-sw">issue</a>
that I am presenting. They say OVS will match the new rule, but
maybe it was casual. Is the behaviour that they see consistent
in OVS? </font><br>
</p>
<blockquote type="cite" cite="mid:20201119173541.GN3324419@ovn.org">
<pre class="moz-quote-pre" wrap="">
</pre>
</blockquote>
<div class="moz-signature">-- <br>
<font face="Calibri">
</font>
<table>
<tbody>
<tr>
<td rowspan="2"><img src="https://sites.cttc.es/cttc.png"
alt="CTTC Logo" align="top"><br>
<br>
<br>
<br>
<br>
</td>
<td> <br>
</td>
<td>
<p><span style="font-size: 10pt;"><strong>Jorge Baranda</strong>
<br>
Senior Researcher, MsC<br>
<a href="mailto:jorge.baranda@cttc.cat">jorge.baranda@cttc.cat</a></span></p>
</td>
</tr>
<tr>
<td> <br>
</td>
<td>
<p><span style="font-size: 9pt;">Centre Tecnològic de
Telecomunicacions de Catalunya (CTTC)<br>
Av. Carl Friedrich Gauss, 7 - Building B4<br>
08860 - Castelldefels<br>
Tel.: +34 93 645 29 00</span></p>
</td>
</tr>
</tbody>
</table>
<font face="Calibri">
</font>
<table>
<tbody>
<tr>
<td>
<p><span style="font-size: 8pt;"><u>DATA PROTECTION
INFORMATION. Data controller: CENTRE TECNOLOGIC DE
TELECOMUNICACIONS DE CATALUNYA (G62616586):</u></span></p>
</td>
</tr>
<tr>
<td>
<p><span style="font-size: 8pt;">We inform you that your
identification data and the data contained in the
emails and attached files can be incorporated into our
databases,
in order to maintain professional and / or commercial
relationships, and that it will be preserved
throughout the relationship.
According to the current regulations, you can exercise
your right to access, rectification, erasure,
restriction of processing, to portability and to
object by sending an email to <a class="moz-txt-link-abbreviated" href="mailto:dpo@cttc.cat">dpo@cttc.cat</a>. <br>
This message and any attached document, where
appropriate, may be confidential and intended for the
original recipient only.<br>
</span></p>
</td>
</tr>
<tr>
<td><br>
</td>
</tr>
<tr>
<td>
<p><span style="font-size: 8pt;">L'informem que les seves
dades identificatives i les compreses als correus
electrònics i fitxers adjunts poden ser incorporades a
les nostres bases de dades amb la finalitat de
mantenir relacions professionals i/o comercials i, que
seran conservades mentre es mantingui aquesta relació.
Si ho desitja, pot exercir el seu dret d'accés,
rectificació, supressió, limitació del tractament,
portabilitat i objecció enviant un correu electrònic a
<a class="moz-txt-link-abbreviated" href="mailto:dpo@cttc.cat">dpo@cttc.cat</a>. <br>
Aquest missatge i qualsevol document adjunt, en el seu
cas, pot ser confidencial i destinat únicament a la
persona o entitat a qui s'hagi enviat.
<br>
</span></p>
</td>
</tr>
<tr>
<td>
<p><span style="font-size: 7pt;"><font color="green">Before
printing this e-mail or attachments, be sure it is
necessary. It is in our hands to protect the
environment.</font><br>
</span></p>
</td>
</tr>
</tbody>
</table>
</div>
</body>
</html>