Comment 1 for bug 1986591

I'm going to make a few comments here:

(1) DO NOT touch the bug status of developer process bugs such as MIR and SRU bugs. **They have specific statuses set for a reason, and if you don't know what those statuses mean for those process bugs, don't touch them.** I've reset this and your previous SRU bug for BIND9 related to this to the **proper** statuses.

(2) I have some concerns. It's fairly common knowledge that it's *rare* MIRs happen post-release, especially on a release of Ubuntu that's 2 and a half years old at this rate. Because of this, I don't believe this is a good choice for historic MIR in pre-Jammy releases. I can see some benefit for Jammy (latest LTS), but older I would leave alone.

(3) This is extremely close to Feature Freeze for Kinetic - August 25th. I don't see any reason to expedite the MIR to reach this deadline, but in the off chance that this is NOT processed prior to Feature Freeze on August 25th 2022, then this would need to be applicable for L-series and would not make it into Kinetic. FeatureFreeze is also relevant for the changes that would add dnstap to BIND9 in Kinetic as well.

I'm of the strong opinion this should not be for pre-Jammy.

Another strong consideration: The upstream repo for this is owned by Farsight Security and has no commits to Master since April 2021. Farsight since this time has been acquired by DomainTools, so the future of Farsight maintaining these sources and packages is actually in question - there's no active change on the repositories' branches that I can see since April, despite the bugs, and there's no guarantee DomainTools will continue to let Farsight devs focus their time and effort on fstrm. Which is another consideration factor here.