Bird is unaffected, so I assume their response is satisfaction for a job well done. FRR, on the other hand, appears to be less responsive to concerns -- which does actually concern me since I use FRR, though not presently for eBGP. Disclosure seems to have done the job thankfully, as there appears to have been a little scramble over at FRRouting/frr about an hour ago.

BIRD was not affected, so we just found out today from Hacker News :-)

We made some thorough code review w.r.t. RFC 7606 compliance years ago.