Registry Working Group

[John Hernandez <>]

On Mon, Aug 26, 2019 at 10:07 AM Bill Owens <> wrote:

As Jeff Bartig pointed out last week, Google is now flagging routes as 'irr-invalid' in their ISP portal. However, in our case every 'invalid' route is actually being accepted and carrying traffic, though I can't tell whether that's because they are simply flagging, or because the ISP portal report is out of sync with the real filters. I'm leaning towards the former, that they are only reporting errors without placing the filters on the actual BGP sessions, because we have one prefix that is intentionally not in the RADb or any other IRR and it is still accepted. 

Hey Bill, I think you're correct - Google is flagging but not enforcing at this point.  This is supported by the import field in their AUT-NUM object (below).  When enforcement begins, one might expect their import policy to change, hopefully?

aut-num:    AS15169
as-name:    Google
descr:      Google, Inc
import:     from AS-ANY   accept ANY AND NOT {0.0.0.0/0}
export:     to AS-ANY   announce AS-GOOGLE AND NOT {0.0.0.0/0}
import:     from AS1273   accept ANY
import:     from AS3356   accept ANY
import:     from AS6453   accept ANY
admin-c:    Google Network Engineering
tech-c:     Google Network Engineering
notify:    
mnt-by:     MAINT-AS15169
changed:     20190626
source:     RADB

-- 

John Hernandez (he/him/his), Network Engineer

1850 Table Mesa Drive, Boulder, CO 80305
Tel. 303-497-1280