Registry Working Group

[Jay Ford <>]

That Google information seems to be stale or it includes historical data 
which isn't marked well as old.  For us it includes a prefix which hasn't 
been announced since Mar 2018.

________________________________________________________________________
Jay Ford, Network Engineering Group
University of Iowa, Iowa City, IA 52242
email: , phone: 319-335-5555

On Fri, 23 Aug 2019, Bill Owens wrote:
> Right you are - the ISP portal now shows a bunch of Invalid IRR - most of 
> which have valid RADb entries, confirmed manually
> and through IRRExplorer. So I’m not really sure what’s going on with Google 
> yet...
>
> Bill.
>
> ______________________________________________________________________________________________________________________________
> From: Jeff Bartig <>
> Sent: Thursday, August 22, 2019 5:49:31 PM
> To:  <>; Bill Owens 
> <>
> Subject: Re: [WG-IRR] Google IRR based route filtering public announcements  
> You may want to check again.  Google deployed some new software this week.  I'm 
> now seeing most prefixes flagged as "Invalid
> IRR".  60% of these prefixes have valid IRR, but I2PX/AS11164 hasn't 
> published an AS-SET for Google to use.
>
> For those networks that have direct peering with Google, their ISP portal is 
> at:  https://isp.google.com/bgp/
>
> Jeff
>
> Bill Owens wrote on 8/15/19 8:05 PM:
>       I happened to check earlier today and there are no IRR errors on our 
> routes, even though we know we still have
>       some bad or missing records. We divided up the 29 peers between the 
> three of us engineers to take care of and
>       *some* folks are finished with their lists, but others aren’t ;)
>
> Bill.
>
> ______________________________________________________________________________________________________________________________
> From:  <> on behalf of Jeff 
> Bartig <>
> Sent: Thursday, August 15, 2019 7:37 PM
> To: ; Michael H Lambert
> Subject: Re: [WG-IRR] Google IRR based route filtering public announcements  
> 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?
>
> Jeff
>
> --
> Jeff Bartig
> Interconnection Architect
> Internet2  AS11164 / AS11537
> +1-608-616-9908