<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Olivier,<div class=""><br class=""></div><div class="">I’m the author of MSD drafts, let me know if I can help.</div><div class="">Drafts are stable and will go to WGLC after Prague (IETF99), </div><div class="">My thinking - to keep it simple, only Base MSD has been defined and pre-allocated by IANA, all other types will be defined in another documents.</div><div class="">In most cases, MSD is limited by the underlying HW, obviously SW has to support larger stack too. </div><div class="">I have discussed an API that could be used to derive MSD value (could be more than 1 by using new MSD type) by querying it with BCM and Barefoot, both agreed on the need to do so.</div><div class=""><br class=""></div><div class="">As I said before - there’s no free lunch in fast path universe, there’s a price to pay in latency, reduced throughput, number of additional features, etc</div><div class="">Sane limits are healthy and protect a system from abuse.</div><div class=""><br class=""></div><div class="">From implementation prospective - extensions to OSPF/ISIS/BGP-LS are needed to signal MSD, while on x86 platform link MSD doesn’t make much sense, please do implement it for the completeness. </div><div class="">HW MSD, when available thru an API call should become the node/link MSD, otherwise should be configured under “routing protocol/interface” stanza.</div><div class=""><br class=""></div><div class="">Have you looked into entropy labels yet? <br class=""><div class="">
<br class="Apple-interchange-newline"><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;" class="">Cheers,</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><span style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; display: inline !important; float: none;" class="">Jeff</span><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><br style="color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">
</div>
<br class=""><div><blockquote type="cite" class=""><div class="">On Jul 3, 2017, at 06:13, <a href="mailto:olivier.dugeon@orange.com" class="">olivier.dugeon@orange.com</a> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" class="">
<div text="#000000" bgcolor="#FFFFFF" class=""><p class=""><font face="Ubuntu" class="">Hello,</font></p><p class=""><font face="Ubuntu" class=""><font face="Ubuntu" class="">This limit must not be
avoided. But, fix looking up to what<font face="Ubuntu" class=""> the
kernel support.</font></font></font></p><p class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class="">In addition, for Segment Routing, there <font face="Ubuntu" class="">is a ne<font face="Ubuntu" class="">w draft (</font></font></font></font></font></font>draft-ietf-ospf-segment-routing-msd-05.txt<font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class="">)
that could be used to adverti<font face="Ubuntu" class="">s</font>e
the Maxim<font face="Ubuntu" class="">um Stack Depth. It is on
my TODO list for OSPF Seg<font face="Ubuntu" class="">ment
Routing support in FRR.</font><br class="">
</font></font></font></font></font></font></font></p><p class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class="">Regards</font></font></font></font></font></font></font></font></p><p class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class=""><font face="Ubuntu" class="">Olivier</font></font></font></font></font></font></font></font></font><br class="">
</p>
<br class="">
<div class="moz-cite-prefix">Le 03/07/2017 à 14:37, Алексей Болдырев
a écrit :<br class="">
</div>
<blockquote type="cite" cite="mid:1174331499085421@web22j.yandex.ru" class="">
<pre wrap="" class="">By the way, kernel 4.12 is already available: (<a class="moz-txt-link-freetext" href="https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.12.tar.xz">https://cdn.kernel.org/pub/linux/kernel/v4.x/linux-4.12.tar.xz</a>)
In this kernel, according to the developers, the number of MPLS tags on the stack is 30.
Therefore, I suggest that this limit in Zebra should be avoided.
<a class="moz-txt-link-freetext" href="https://github.com/FRRouting/frr/issues/776">https://github.com/FRRouting/frr/issues/776</a>
_______________________________________________
dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dev@lists.frrouting.org">dev@lists.frrouting.org</a>
<a class="moz-txt-link-freetext" href="https://lists.frrouting.org/listinfo/dev">https://lists.frrouting.org/listinfo/dev</a>
</pre>
</blockquote>
<br class="">
<pre class="">_________________________________________________________________________________________________________________________
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 class="">dev mailing list<br class=""><a href="mailto:dev@lists.frrouting.org" class="">dev@lists.frrouting.org</a><br class="">https://lists.frrouting.org/listinfo/dev<br class=""></div></blockquote></div><br class=""></div></body></html>