[dev] Next step for the Telco Meeting

Wed Jan 12 15:31:01 UTC 2022

Dear all,

It seems that nobody received the update I sent one week ago to re-schedule the Telco meeting from 17h-18h to 16h-17h Paris time due to a conflict with the PIM meeting.

Apologize for the inconvenient. This is due to my IT service that configure our mail server to not accept e-mail we (at Orange) send to external mailing list. They consider that external mail server are usurping our identities. Thus, I'm blind when sending an e-mail to dev-frr mailing list. Sometimes I check the archive, sometimes not. And here, I'm too confident.

As consequence, I'm connected at 16h Paris time waiting for people to join, and of course, nobody comes :-(

Thus, I think it will be better if somebody else will organize this meeting as I could not guarantee that the same problem will not occur again.

Best regards,

Olivier

Le 21/12/2021 à 11:25, olivier.dugeon at orange.com<mailto:olivier.dugeon at orange.com> a écrit :

Dear all,

Following the last Telco Meeting and the discussion about the future of the Telco Meeting
during the last regular meeting, I open a new thread on the mailing list to discuss how to
organize Telco Meeting for 2022.

Context:
========

- First, starting mid-2021, we reduce the number of Telco Meeting from bi-weekly to monthly meeting.
- Second, number of attendees decrease regularly as well as number of subjects.
- As a consequence, it seams reasonable to stop Telco Meeting by end of 2021.
- However, during the lastTelco meeting, it appears that we need to continue coordination
  at least for Segment RoutingFlex algorithm at least between Hiroki who develop Flex Algo
  for IS-IS, Pushpasis who do thesame for OSPF and myself who develop Constraints SPF algorithm
  for Flex Algo based on delayand TE metric.

Proposal:
=========
- Continue a regular cycle of meeting dedicated to coordinate the development of new features
- Give time for presentation of new features, new architectures, new daemons ... for FRR
- Discuss FRR roadmap and organize which features will be part of the next FRR release
- And to reflect the new orientation, rename Telco Meeting e.g. New Features Meeting

Thus, it was decided during the last regular meeting, to open discussion on the mailing list
(the object of this thread) and organize a dedicated meeting to discuss the future of the
Telco Meeting for 2022 and beyond.
I'll send an invit for such meeting by taking the slot of the next Telco Meeting i.e. the 12th
of January 17h00 CEST.

Best Regards

Olivier

_________________________________________________________________________________________________________________________

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.

_______________________________________________
dev mailing list
dev at lists.frrouting.org<mailto:dev at lists.frrouting.org>
https://lists.frrouting.org/listinfo/dev

--
[Orange logo] <http://www.orange.com>

Olivier Dugeon
Orange Expert, Future Networks
Open Source Referent
Orange/IMT/OLN/WTC/IEE/iTeQ

fixe : +33 2 96 07 28 80
mobile : +33 6 82 90 37 85
olivier.dugeon at orange.com<mailto:olivier.dugeon at orange.com>

_________________________________________________________________________________________________________________________

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.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20220112/b226be79/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: small_logo.png
Type: image/png
Size: 219 bytes
Desc: small_logo.png
URL: <http://lists.frrouting.org/pipermail/dev/attachments/20220112/b226be79/attachment.png>