We recently turned up a new IXP and I’m going through the motions of arranging the usual peers, etc.
I’m extremely surprised by this one:
Public Peering
Google no longer accepts new peering requests at internet exchanges (IXPs). However, Google maintains dedicated connectivity to the internet exchanges (IXPs) listed in our PeeringDB entry<https://www.peeringdb.com/asn/15169>. We also maintain existing BGP sessions across internet exchanges where we are connected. For networks who do not meet our PNI requirements Google will serve those networks via indirect paths.
I can only presume that someone who doesn’t pay for cross connect fees came up with this plan. This feels short sighted at the least. Considering the benefits of peering, I have to express some dismay at this disservice to the internet in general.
Anyone from Google care to explain what appears to be a willful withdrawal of support for the IXP community?
(Apologies for duplicates)
Hi all,
The NRO RPKI Program has published a page that consolidates existing sources on RPKI best practices and lessons learned (https://www.nro.net/technical-coordination/nro-rpki-program/rpki-best-pract…)
We want to make sure the information included is clear and operationally relevant for those deploying and maintaining RPKI.
If you see anything missing, unclear, or that needs an update, please send your input to rpki_program(a)nro.net
Thanks in advance for helping us make this a stronger resource for the community!
Warm regards,
Sofía
--
I am sending this email at a time that suits me and the time zone I work in. Please feel free to read, and act on or respond, at a time that suits you.
____________________________________________________________________
Sofía Silva Berenguer
NRO RPKI Program Manager
e: sofia(a)apnic.net<mailto:sofia@apnic.net>
____________________________________________________________________
