<div><div dir="auto">Thanks Olivier, good to know!</div></div><div dir="auto">While DC use case doesn’t require link MSD (single chipset), for sake of completeness please do consider implementing it.</div><div dir="auto"><br></div><div dir="auto">Thanks,</div><div dir="auto">Jeff </div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Apr 12, 2019 at 16:29 <<a href="mailto:olivier.dugeon@orange.com">olivier.dugeon@orange.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p><font face="DejaVu Sans">Hello Jeff,</font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans">It is in the<font face="DejaVu Sans"> todo list. The IS<font face="DejaVu
Sans">IS SR implementation is a back port of the OSPF one.
So, MSD propagation is on board.</font></font></font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans">Regards</font></font></font></font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans">Olivier</font></font></font></font></font></font><br>
</p></div><div bgcolor="#FFFFFF" text="#000000">
<br>
<div class="m_6755672742995231645moz-cite-prefix">Le 12/04/2019 à 13:10, Jeff Tantsura a
écrit :<br>
</div>
<blockquote type="cite">
<div>
<div dir="auto">Olivier,</div>
</div>
<div dir="auto"><br>
</div>
<div dir="auto">Would be great if you’d implement MSD (that’s RFC
by now) in ISIS, given that the target is merchant silicon, it
would be rather important.</div>
<div dir="auto">Let me know if I can help.</div>
<div dir="auto"><br>
</div>
<div dir="auto">Cheers,</div>
<div dir="auto">Jeff</div>
<div><br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, Apr 12, 2019 at 9:40
AM <<a href="mailto:olivier.dugeon@orange.com" target="_blank">olivier.dugeon@orange.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<p><font face="DejaVu Sans">Hello Shurov,<font face="DejaVu Sans"><br>
</font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans">As
the develop<font face="DejaVu Sans">er of OSPF-SR, I<font face="DejaVu Sans">'m currently adding the
support of SR to IS-IS. Work is done at 70%, but
due to a re<font face="DejaVu Sans">cent bug
discovered with MPLS-TE (<font face="DejaVu
Sans">Issue #4032) I need to first solve th<font face="DejaVu Sans">is</font> problem, and
then adapt IS-IS<font face="DejaVu Sans">-</font>SR
code to this new feature.</font></font></font></font></font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans">I hope I could release
a pre-alpha version by one <font face="DejaVu Sans">mont<font face="DejaVu Sans">h.</font></font></font></font></font></font></font></font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu
Sans"><font face="DejaVu Sans"><font face="DejaVu Sans">Regards</font></font></font></font></font></font></font></font></font></font></p>
<p><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu
Sans"><font face="DejaVu Sans"><font face="DejaVu Sans"><font face="DejaVu Sans">Olivier</font></font></font></font></font></font></font></font></font></font></font><br>
</p>
</div>
<div bgcolor="#FFFFFF" text="#000000"> <br>
<div class="m_6755672742995231645m_-8526427978267934181moz-cite-prefix">Le
12/04/2019 à 05:36, Shuvro a écrit :<br>
</div>
<blockquote type="cite">
<div dir="ltr">Hi Team,
<div><br>
</div>
<div>Last few days I was doing few configs in OSPF-SR
and found decent support being available there in
FRR but I do not see the same for ISIS,nor does the
official FRR documentation mention anything about
the same.</div>
<div><br>
</div>
<div>Is it safe to assume ISIS-SR is still not
supported in FRR or is there any work around to make
SR work using ISIS?</div>
<div><br>
</div>
<div>Your kind response on the same is appreciated.</div>
<div><br>
</div>
<div>Thanks,</div>
<div>Shuvro</div>
</div>
<br>
<fieldset class="m_6755672742995231645m_-8526427978267934181mimeAttachmentHeader"></fieldset>
<br>
<pre>_______________________________________________
dev mailing list
<a class="m_6755672742995231645m_-8526427978267934181moz-txt-link-abbreviated" href="mailto:dev@lists.frrouting.org" target="_blank">dev@lists.frrouting.org</a>
<a class="m_6755672742995231645m_-8526427978267934181moz-txt-link-freetext" href="https://lists.frrouting.org/listinfo/dev" target="_blank">https://lists.frrouting.org/listinfo/dev</a>
</pre>
</blockquote>
<br>
</div>
<div bgcolor="#FFFFFF" text="#000000">
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre>
</div>
_______________________________________________<br>
dev mailing list<br>
<a href="mailto:dev@lists.frrouting.org" target="_blank">dev@lists.frrouting.org</a><br>
<a href="https://lists.frrouting.org/listinfo/dev" rel="noreferrer" target="_blank">https://lists.frrouting.org/listinfo/dev</a><br>
</blockquote>
</div>
</div>
</blockquote>
<br>
<pre>_________________________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.
This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.
</pre></div>
</blockquote></div></div>