Registry Working Group

[Matt Valenzisi <>]

On Thu, Aug 15, 2019 at 7:37 PM Jeff Bartig <> wrote:
>
>
>
> Michael H Lambert wrote on 8/15/19 6:17 PM:
>
> On 15 Aug 2019, at 19:06, Jeff Bartig <> wrote:
>
> Google has also been putting some content on their web site:
>
> https://support.google.com/interconnect/answer/9368848?hl=en&ref_topic=9326690 (see each of the links on the right of this page)
> https://peering.google.com/#/options/peering (search page for IRR)
>
> Regarding these two links:  I did ask Google exactly what they meant by "supported registries”.  The answer I got a couple of weeks ago was that this is the list of registries they are actually going to query.  They do not plan to restrict their filter-building to objects having one of those registries as the source.  Since, for example, ALTDB is mirrored by RADB, objects in ALTDB will be candidates for use.  The purpose behind querying multiple registries is to maximize coverage, not tie folks into particular registries. Of course, this could all change upon implementation.
>
> The Frequently Asked Questions page found on the first link above does list the registries that they are currently using:
>
> Which IRRs can I use?
>
> We currently use:
>
> ALTDB, APNIC, ARIN, BBOI, BELL Canada, CANARIE, EASYNET, HOST, JPIRR, Level4, NESTEGG, NTT, OPENFACE, OTTIX, PANIX, REACH, RADB, RGNET, RIPE, RISQ, ROGERS, TC
>
> If your IRR is not there please let us know at and we will review. If you also use an AS-SET, please also update the IRR record in PeeringDB with your AS-SET.
>
>
> This list seems to closely match the list of IRRs that are mirrored by RADb, so they probably used that as their starting point.
>
>
> On the same Frequently Asked Questions page, I find:
>
> My traffic shifted from peering to transit, is it related to this project?
>
> Possibly. We recommend to check the validity of your prefixes at the ISP Portal under the Monitoring -> BGP Section: https://isp.google.com/bgp/
>
> If you have invalid prefixes please resolve those issues before contacting us again at . If all your prefixes are valid then contact us again at .
>
>
> When I visit this their ISP Portal and login as AS11164 (I2PX), it does show me a list of all of the prefixes they receive from AS11164, but currently none of them are marked as having any IRR issues.  If you click on "filter by problem", there is a choice of "Invalid IRR", but it produces no results.  Does anyone else that has direct peering with Google see any of your prefixes flagged as Invalid IRR?

Hello Jeff, I do not see any of our prefixes flagged as Invalid IRR.

Thanks,

Matt

>

> Jeff
>
> --
> Jeff Bartig
> Interconnection Architect
> Internet2  AS11164 / AS11537
> +1-608-616-9908
>