consistent policy != consistent announcements

on the first example, if someone is complaining about what
you're doing, then, unless i'm missing something, they're
concerned much more about the letter of the policy than
the tone

add a peer P to your first example. if P peers with you at
Point1 close to A's connection and again at a Point2 close
to B's connection, then P will hear M's prefixes at Point1
as "R A M" and at Point2 as "R B M". but because the AS
path length is equal, they'll still be able to do closest
exit for M's prefixes. the tone of the "consistent route"
policy is to keep one provider from having to carry
packets cross-country in both directions: in this example
P does not have to do that

/jws