[as112-ops] LOA Request for AS112 Prefixes

[Frank Habicht]

Hi Joe,

On 03/11/2018 21:52, Joe Abley wrote:
> Hi Jonathan,
> 
> On Nov 3, 2018, at 04:09, Jonathan Stewart <jonathan.stewart at gmail.com> wrote:
> 
>> If this ISP cannot understand what AS112 is from the RFC, there's a good chance they won't handle the AS112 prefixes correctly.
> 
> What special handling do AS112 prefixes need compared to any other
> prefix from the perspective of a transit provider?

My thinking is that a transit provider covering large geographies 
learning AS112 these prefixes from customers SHOULD (not MUST) give them 
same local-pref as from peerings, so that traffic doesn't travel around 
the globe.
(better would be their own instances, ideally sprinkled $everywhere)

Thinking the other way, every provider could have them as their 
self-operated "customers" in many POPs.

The questions really is about what's more important: do we want to give 
fast answers to a customer resolver [by running our own AS112 or peering 
it off everywhere, by preferring peerings as much as customers], or do 
we want to transport bits over distances[from the resolver to a paying 
customer's AS112] and charge for it [by preferring a customer more].

And the answer to this question might be different for different network 
operators.

So I think of the LOA as a weapon, which the provider can use to shoot 
themselves into the foot. If they don't think twice.


Frank