Should we back-port max-ixfr-ratio from 9.17 to earlier versions of BIND?
I can't see any other elegant option currently that could be used to 'protect' a zone hosting set-up from receipt and onward propagation of a massive IXFR to the service-providing authoritatives.
This happens sometimes accidentally (see Support Ticket #17366) and I would rather provide a solid solution in named, than encourage scripting that spots when something like this happens, and then goes off to delete .jnl or zone files on disk to prevent the same IXFR heading out to Internet-facing servers, where the effects of applying it can be seriously detrimental to server performance.