robust scalability of routing system (4)

what is needed (courtesy tim griffin, phil karn)
defined routing policy languages guaranteed to be globally sane
no matter the what local policies are defined
BGP speakers must be forced to use them  (i.e, standardize MUST)
give user control of packets to/from his/her own IP address
rather than clumsy, brittle firewalls not understood by the ISP's phone support anyway
open standard for the secure remote control of a generic packet-filtering firewall

research questions 
is it possible to design such languages and protocols? 
how can we find the right balance between local policy expressiveness and global sanity? 
what exactly do we mean by "autonomy" of routing policy?  
do we need additional protocols to enforce global sanity conditions? 
how can we enforce compliance of policy language usage?