[as112-ops] AS112 peering coordination?

[Jonathan Stewart]

Aleksi,

It's hard to imagine how us AS112 volunteers are going to influence teir-1
ISPs, unless we have someone on the inside.

AS112 is a project to catch mistakes, anyway--how many people care about
getting fast response to someone's foolish DNS queries (query to Global DNS
for a local-only address).

What i'm saying is, I can't see any way for the AS112 project to coordinate
peering, other than continuing to do what we are doing. Deploying at IXes
seems the best.

Cheers,
Jonathan

On Wed, Jul 29, 2015 at 5:48 AM, Aleksi Suhonen <as112-ops at trex.fi> wrote:

> Hi,
>
> Currently the general AS112 peering policy is very open, although only
> nodes that are hosted at IXPs are easily available for direct peering.
> (Right?)
>
> This is alright for peers that only have interconnections in a couple of
> cities. But for ISPs that have interconnections on multiple continents: I
> feel it could use better coordination.
>
> A "backbone operator" will be receiving the AS112 prefixes with different
> AS path lengths and other attributes in different places. They will also
> probably be receiving it from a mix of customers and peers.
>
> Here's one example view:         http://bgp.he.net/AS112
>
> I think ISPs should forward this traffic to the closest node regardless of
> AS path length and other attributes. Since that is technically not feasible
> to guarantee right now, maybe we should try to coordinate peering with "the
> top peerers," so that they can receive similar announcements on every
> continent?
>
> Is this something we want to do?
>
> Yours,
>
> --
>         +358 44 9756548 / http://www.trex.fi/
>         Aleksi Suhonen / TREX Regional Exchanges Oy
>
>         Let bogons be bogons.
> _______________________________________________
> as112-ops mailing list
> as112-ops at lists.dns-oarc.net
> https://lists.dns-oarc.net/mailman/listinfo/as112-ops
>



-- 
     Jonathan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.dns-oarc.net/pipermail/as112-ops/attachments/20150730/5d50cc02/attachment.html>