<div dir="ltr">Hi <span style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:12.8px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial;float:none;display:inline">Vivek,</span><div><span style="font-size:12.8px"><br></span><div>Originally we planned to support only in-cloud VMs, therefore, w<span style="font-size:12.8px">e do not use these bits in Dragonflow.</span></div><div><span style="font-size:12.8px">We believe we managed to follow the standard without using these bits. </span></div><div><span style="font-size:12.8px">If this is a bug, we will try to fix it.</span></div><div><span style="font-size:12.8px"><br></span></div><div><span style="font-size:12.8px">Regards,</span></div><div><span style="font-size:12.8px">Lihi<br></span><div><br></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Tue, Mar 20, 2018 at 8:45 AM, N Vivekanandan <span dir="ltr"><<a href="mailto:n.vivekanandan@ericsson.com" target="_blank">n.vivekanandan@ericsson.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div lang="EN-US" link="#0563C1" vlink="#954F72">
<div class="m_-4803365791775685785WordSection1">
<p class="MsoNormal">Hi DragonFlow Team,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We noticed that you are adding support for automatic responder for neighbor solicitation via OpenFlow Rules here:<u></u><u></u></p>
<p class="MsoNormal"><a href="https://review.openstack.org/#/c/412208/" target="_blank">https://review.openstack.org/#<wbr>/c/412208/</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Can you please let us know with latest OVS release are you using to test this feature?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We are pursuing Automatic NS Responder in OpenDaylight Controller implementation, and we noticed that there are no NXM extensions to manage the ‘R’ bit and ’S’ bit correctly.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">From the RFC: <a href="https://tools.ietf.org/html/rfc4861" target="_blank">
https://tools.ietf.org/html/<wbr>rfc4861</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<pre><span style="color:black"> R Router flag. When set, the R-bit indicates that<u></u><u></u></span></pre>
<pre><span style="color:black"> the sender is a router. The R-bit is used by<u></u><u></u></span></pre>
<pre><span style="color:black"> Neighbor Unreachability Detection to detect a<u></u><u></u></span></pre>
<pre><span style="color:black"> router that changes to a host.<u></u><u></u></span></pre>
<pre><span style="color:black"><u></u> <u></u></span></pre>
<pre><span style="color:black"> S Solicited flag. When set, the S-bit indicates that<u></u><u></u></span></pre>
<pre><span style="color:black"> the advertisement was sent in response to a<u></u><u></u></span></pre>
<pre><span style="color:black"> Neighbor Solicitation from the Destination address.<u></u><u></u></span></pre>
<pre><span style="color:black"> The S-bit is used as a reachability confirmation<u></u><u></u></span></pre>
<pre><span style="color:black"> for Neighbor Unreachability Detection. It MUST NOT<u></u><u></u></span></pre>
<pre><span style="color:black"> be set in multicast advertisements or in<u></u><u></u></span></pre>
<p class="MsoNormal"><span style="color:black"> unsolicited unicast advertisements.<u></u><u></u></span></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">We noticed that this dragonflow rule is being programmed for automatic response generation for NS:<u></u><u></u></p>
<div style="border:solid #cccccc 1.0pt;padding:15.0pt 23.0pt 15.0pt 23.0pt;background:#333333">
<p class="MsoNormal" style="margin-bottom:7.5pt;background:#333333;word-break:break-all;border:none;padding:0in">
<span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">icmp6,ipv6_dst=</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">1</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">::</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">1</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">,icmp_type=</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9"><wbr>135</span><span style="font-size:10.0pt;font-family:Consolas;color:white">
</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">actions=load:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">0x88</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">->NXM_NX_<wbr>ICMPV6_TYPE[],move:NXM_NX_<wbr>IPV6_SRC[]->NXM_NX_IPV6_DST[],<wbr>mod_dl_src:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">00</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">11</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">22</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">33</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">44</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">55</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">,<wbr>load:</span><span style="font-size:10.0pt;font-family:Consolas;color:#3677a9">0</span><span style="font-size:10.0pt;font-family:Consolas;color:#d0d0d0">->NXM_NX_ND_SLL[],IN_<wbr>PORT</span><span style="font-size:10.0pt;font-family:Consolas;color:white"><u></u><u></u></span></p>
</div>
<p class="MsoNormal">above line from spec <a href="https://docs.openstack.org/dragonflow/latest/specs/ipv6.html" target="_blank">
https://docs.openstack.org/<wbr>dragonflow/latest/specs/ipv6.<wbr>html</a><u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">However, from the flow rule by dragonflow for automatic response above, we couldn’t notice that R and S bits of the NS Response is being managed.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Can you please clarify if you don’t intend to use ‘R’ and ‘S’ bits at all in dragonflow implementation?
<u></u><u></u></p>
<p class="MsoNormal">Or you intend to use them but you weren’t able to get NXM extensions for the same with OVS and so wanted to start ahead without managing those bits (as per RFC)?<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Thanks in advance for your help.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">--<u></u><u></u></p>
<p class="MsoNormal">Thanks,<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Vivek<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
<br>______________________________<wbr>______________________________<wbr>______________<br>
OpenStack Development Mailing List (not for usage questions)<br>
Unsubscribe: <a href="http://OpenStack-dev-request@lists.openstack.org?subject:unsubscribe" rel="noreferrer" target="_blank">OpenStack-dev-request@lists.<wbr>openstack.org?subject:<wbr>unsubscribe</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" rel="noreferrer" target="_blank">http://lists.openstack.org/<wbr>cgi-bin/mailman/listinfo/<wbr>openstack-dev</a><br>
<br></blockquote></div><br></div>