I see your point (and remember your earlier message), but that's not
a show stopper. To be in that situation, the small ISP has to have
bought ISP access connectivity from one or more ISPs in those geographically
disparate locations and not have them find out what's going on. If, say,
mountainview.net (which is fictional (I hope 8-)) branched out to Miami,
and bought another Alternet ISP T-1 connection out there, they would
then be getting free transit between them. Presumably if both were
Alternet connections, you'd figure it out. If they bought Sprint access
in Miami, then they might fool both of you.
You could easily avoid this by adding a statement to your service contracts
for addresses allocated from these geographical block(s), which states that
there must be full disclosure to all involved upstream providers if the
company adds sites outside that area. If they fail to do so they would
then be defrauding you. This is a matter for you to work out with your
customers, so it's not really the address blocks' managements' issue.
You just have to keep a slight eye on people using the block space.
The basic problem isn't with geographical addressing per se. It is possible
for unscrupulous end users to set up things like this, with transit achived
surrepticiously (or an ISP claiming not to be to get the cheaper connect)
already, and I'm sure in some cases it is happening. Proper policy and
awareness is required to deal with it at whatever level it appears,
geographical addressing being one such level.
-george