<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<p><font face="Ubuntu">Dear all,</font></p>
<p><font face="Ubuntu">Here it is the meeting minutes of today FRR
Telco meeting. The minutes are also available on the wiki page:
<a class="moz-txt-link-freetext" href="https://github.com/FRRouting/frr/wiki/FRR-Telco-SP-projects">https://github.com/FRRouting/frr/wiki/FRR-Telco-SP-projects</a></font></p>
<p><font face="Ubuntu">@Donald Can you add to the agenda to the next
FRR weekly meeting 5 minutes to review the list of requested
features <a class="moz-txt-link-freetext" href="https://github.com/FRRouting/frr/wiki/Feature-Requests">https://github.com/FRRouting/frr/wiki/Feature-Requests</a>
to update the list by marking by done or FRR release version
which features are already available ?<br>
</font></p>
<p><font face="Ubuntu">Regards</font></p>
<p><font face="Ubuntu">Olivier</font></p>
<p><font face="Ubuntu">----------</font></p>
<h3>2020-02-19 call</h3>
<p>Brief status about on-going development for IS-IS Segment Routing
was provided by Olivier. Due to its contribution to OpenDaylight,
Olivier will provide PR next week.</p>
<p>BGP-LS interest was requested. For the moment, some peoples are
interested by the feature, but have no plan to develop part of
BGP-LS code. Olivier will re-contact people that are interested by
developing such function and will share the old code that has been
developed 3 years ago (on Quagga base prior to FRR project).
Unfortunately, it is not possible to merge this code as is in the
current FRR master. So, only new files (parser and serializer)
will be publish.</p>
<p>A point was done about the Traffic Engineering Database. This
feature is mandatory for BGP-LS but will be of interest for other
part e.g. RSVP-TE, PCE. Olivier clarified how he saw the use of
Traffic Engineering Database. In one side, there are daemons
(IS-IS or OSPF) which are in charge to fulfil it from the TE
information they receive from neighbours and what is configured on
the interfaces. And in other side, daemon consumers which will
have access to the TED either via ZEBRA and new ZAPI messages
(e.g. BGP for BGP-LS) or directly (e.g. IS-IS for Segment Routing
flexible algorithm) since the TED will be stored in the same
address space as the process that will produce it e.g. IS-IS.</p>
<p>Olivier suggested establishing a roadmap for future developments.
It may still be too early. However, it was decided to review the
list of requested features listed in the FRR Wiki. Renato
suggested seeing this during the weekly FRR meetings. Olivier will
ask Donald to add this to the agenda of the next FRR meetings.</p>
<div class="moz-signature">-- <br>
<a style="text-decoration:none;" href="http://www.orange.com"> <img
style="border:none;margin-top: 5px;margin-bottom: 3px;"
alt="Orange logo" src="cid:part1.F182E412.089E1B4D@orange.com">
</a>
<p style="line-height:10px;margin:0px"> </p>
<span style="font-weight:bold;font-family:Arial,
sans-serif;font-size:10pt;color:#000000;"> Olivier Dugeon<br>
</span> <span style="font-family:Arial,
sans-serif;font-size:10pt;color:#000000;"> Orange Expert, Future
Networks <br>
Open Source Referent <br>
Orange/IMT/OLN/WTC/IEE/iTeQ<br>
</span>
<p style="line-height:20px;margin:0px"> </p>
<span style="font-family:Arial,
sans-serif;font-size:10pt;color:#000000"> fixe : +33 2 96 07 28
80<br>
mobile : +33 6 82 90 37 85<br>
</span> <span style="margin:0px 0 20px 0;"> <a style="margin:0px
0 20px 0;font-family:Arial,
sans-serif;font-size:10pt;color:#FF6600;text-decoration:none;"
href="mailto:olivier.dugeon@orange.com">olivier.dugeon@orange.com</a>
</span> </div>
<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></body>
</html>