Action 1: Prevent propagation of incorrect routing information
As part of our work to improve how we receive BGP advertisements from our interconnect partners we will start adding inbound route filters in all of our BGP sessions. To build these filters we will initially use IRR data and we are evaluating the use of RPKI.
We will start filtering sessions on Q2-2019.
We are also building a MANRS webpage that we will publish under https://peering.google.com. We expect the URL to be https://peering.google.com/MANRS but we will update you as soon as we define and publish it.
Action 2: Prevent traffic with spoofed source IP addresses
Google network operates under the principles under of BCP38.
Action 3: Facilitate global operational communication and coordination
Our NOC contact information is located on our PeeringDB Entry: https://www.peeringdb.com/asn/15169.
For questions regarding network support from Google please visit https://peering.google.com/#/learn-more/faq.
Action 4: Facilitate validation of routing information on a global scale
We have a generally open peering policy that could be found at https://peering.google.com/#/options/peering and https://peering.google.com/#/options/peering.
From 2019-Q2 we will be applying route filters to all our BGP sessions. To build these filters we will use your ASN data on the IRR system. To avoid any routing issues please keep your IRR objects up to date.