Thanks, Quentin. I fully understand, and appreciate, how open source, community projects work. I am caught up in a number myself, and time + interest are always the biggest constraints. I just wanted to let the list know about where things currently stand, for the archives. I will keep checking to see when IS-IS support in FRR matures, and report feedback as and when I am able to test it. As always, much appreciated to all the developers that submit their time to building and maintaining the code. Mark. On 5/1/23 18:25, Quentin Young wrote:

Hi Mark,

...

I hope there would have been some fixes to the outstanding IS-IS issues I have posted about. Unfortunately we have quite a lot of issues to work on. FRR is really big and complex! Really big and complex software takes a lot of effort to maintain, and it's not possible to get to every concern in every release.

To provide a little context on how FRR development works, the people working on FRR can be broadly placed in one of the following groups:

1) Unpaid volunteers 2) Company employees

Group 1 is donating their time and skillset for free. They choose what to work on and no matter what they choose, we are grateful for their efforts. Any help in any area is welcomed. If they choose to work on something other than the IS-IS issues you reported, that is their prerogative. Group 2 is paid by their employer to work on areas important to their employer. If their employer doesn't prioritize the IS-IS issues you reported, then they are less likely to work on them. Note that there is always the possibility of contracting with a company to work on issues that you want prioritized.

There is overlap between the two groups - company employees sometimes act as volunteers, working on aspects of the project that interests them - but in short, my point is that work on FRR, like almost any FOSS project, is completed on a best-effort basis.

Now, obviously everyone involved in the project, from developers to users, would love for every aspect of FRR to work well. We all have the same objectives. Users want functioning software, developers want functioning software. We all want IS-IS to work. We didn't get to the issues you reported this release. That doesn't mean the issues will not be addressed in upcoming releases, and it doesn't mean that no one cares. It just means that the limited resources that work on FRR spent their efforts on other areas this release.

...

It seems IS-IS is not going to be ready for production use anytime soon, so I'll have to go back to Quagga. As a gentle reminder, the code for IS-IS, which anyone may contribute to, is located here:https://github.com/FRRouting/frr/tree/master/isisd

As ever, we are grateful for anyone who chooses to graciously donate their time to work on free software, which everyone gets to benefit from.

Hope this helps, Quentin

________________________________________ From: frog<frog-bounces+qlyoung=cumulusnetworks.com@lists.frrouting.org> on behalf of Mark Tinka<mark@tinka.africa> Sent: Sunday, April 30, 2023 9:02 AM To:frog@lists.frrouting.org Subject: Re: [FROG] FRR 8.5.1 Release

External email: Use caution opening links or attachments

I hope there would have been some fixes to the outstanding IS-IS issues I have posted about.

It seems IS-IS is not going to be ready for production use anytime soon, so I'll have to go back to Quagga.

Mark.

On 4/30/23 12:49, Jafar Al-Gharaibeh via frog wrote:

ear FRR Community,

We are pleased to announce FRR 8.5.1 bug fix release.

Packages are available at:

Debian Packages -https://deb.frrouting.org<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdeb.frrouting.org%2F&data=05%7C01%7Cqlyoung%40cumulusnetworks.com%7C1fbc3b171fac40e6d54608db497f1647%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638184583043142727%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=vvMJ7UfYKKmHvPjT5dcu64oAKNLwrdpWLQolB%2FQQhEo%3D&reserved=0> RPM Packages -https://rpm.frrouting.org<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Frpm.frrouting.org%2F&data=05%7C01%7Cqlyoung%40cumulusnetworks.com%7C1fbc3b171fac40e6d54608db497f1647%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638184583043142727%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=%2BipNWpE%2F2pBWDVgCiA%2BhFSrjqj1kgAxMwcC8GqvH4Ws%3D&reserved=0> Snaps -https://snapcraft.io/frr<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsnapcraft.io%2Ffrr&data=05%7C01%7Cqlyoung%40cumulusnetworks.com%7C1fbc3b171fac40e6d54608db497f1647%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638184583043142727%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=FeST1oGspHRFEac6LlKdubLr3dnCUCwfafbDwpZuM%2Fo%3D&reserved=0> Docker - quay.io/frrouting/frr:v8.5.1

For release notes please visit:

https://frrouting.org/release/8.5.1/<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffrrouting.org%2Frelease%2F8.5.1%2F&data=05%7C01%7Cqlyoung%40cumulusnetworks.com%7C1fbc3b171fac40e6d54608db497f1647%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638184583043142727%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=%2B13FJNiI9buSAZSbPQHHgnHpQ68R6wc61BYYHt2WxVc%3D&reserved=0>

https://github.com/FRRouting/frr/releases/tag/frr-8.5.1<https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FFRRouting%2Ffrr%2Freleases%2Ftag%2Ffrr-8.5.1&data=05%7C01%7Cqlyoung%40cumulusnetworks.com%7C1fbc3b171fac40e6d54608db497f1647%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638184583043142727%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000%7C%7C%7C&sdata=sGSphqur60C0waQK0VNh4yssL1UcHbjuMOpHAjqjxqQ%3D&reserved=0>

Cheers,

The FRR Development Team!