Registry Working Group

[Bill Owens <>]

I opened a Google ISP portal ticket earlier this week with the following info:

"NYSERNet AS3630 peers with Google on a PNI at 111 8th Ave in NYC. I believe 
we have a valid IRR configuration (mostly with RADb records) but for several 
weeks our routes have been flagged in the BGP portal as Invalid IRR. With the 
latest portal change, they mostly show up as "No AS-SET Relationship". 

We have a PeeringDB record for NYSERNet-COM (https://peeringdb.com/net/12186) 
which references our as-set as3630:as-all. We also have an aut-num object for 
as3630 which includes export and mp-export lines containing as3630:as-all. 
I'm not sure what else we would need to do in order to create an "AS-SET 
Relationship" for this peering, can you provide me with anything I'm 
missing?"

Here's the obviously canned, and completely useless response:

"Thank you for contacting Google's NOC. We will be rolling out IRR filtering 
over the next few months. Our BGP prefix page in the ISP portal 
(https://isp.google.com/bgp/) shows prefixes received from you and any IRR 
issues.

We're currently flagging issues IRR only, no route filtering or routing 
decisions are being made with this data. We do encourage you to ensure there 
are no IRR issues with your network as we will build filters based upon this 
data later this year.

We will be in contact with further instructions in the coming weeks in 
relation to this. In the meantime if you wish to prepare further please 
review Google's FAQ at https://support.google.com/interconnect/answer/9325703

Further information on IRR and best practices can be found at:

BCP194: https://tools.ietf.org/html/bcp194
RFC2650: https://tools.ietf.org/html/rfc2650";


Indeed, I would like to 'ensure there are no IRR issues' but they aren't 
making it easy to do that...

Bill.