Security ought to not make the system being protected brittle. Like the example of routing changes being held up until the paperwork went through - maybe an improvement in tools will enable this.
It should be possible for a network operator to make their own policy decisions on this. Some may choose to accept uncertified routes in certain address ranges because this makes their network less brittle. Others may consider the brittleness to be a feature because it tends to highlight deficiencies with the 3rd party tools, databases, systems, which should be fixed. Consider the phone number translation databases used for number portability. If they are not updated when a telephone moves to another location, then the service is disrupted. If PSTN operators can find a way to share and synchronize a number portability database, then why can't network operators do something similar? --Michael Dillon