Registry Working Group

[Bill Owens <>]

It does:

 

 

That particular advertisement is one of the ones that I think has been flagged Invalid for invalid reasons, since it has a perfectly good RADb object:

 

route:      199.109.16.0/21

origin:     AS3756

descr:      NYSERNet Syracuse

admin-c:    William Owens

tech-c:     NYSERNet NOC

notify:    

mnt-by:     MAINT-AS3754

changed:    20190815  #18:32:27Z

source:     RADB

 

FWIW, here’s what a traceroute looks like from my test GCP instance to one of your nameservers:

 

owens@bill-traceroute-1:~$ sudo tcptraceroute 164.113.192.242 53

Running: traceroute -T -O info -p 53 164.113.192.242

traceroute to 164.113.192.242 (164.113.192.242), 30 hops max, 60 byte packets

1 64.57.21.202 (64.57.21.202) 36.050 ms 35.571 ms 35.662 ms

2 bb-kc-grand-et0-0-0-0.bb.net.kanren.net (164.113.192.41) 36.663 ms 36.647 ms 36.644 ms

3 nic.kanren.net (164.113.192.242) <syn,ack> 36.374 ms 36.573 ms 36.111 ms

 

Seems like everything is in order…

 

Bill.

 

 

From: <> on behalf of Brad Fleming <>
Reply-To: <>
Date: Monday, August 26, 2019 at 11:53
To: <>
Subject: Re: [WG-IRR] Google IRR based route filtering public announcements

 

Does “Invalid IRR” show up in the “Problems” column? And does it show for any announced prefix with issues or only those originated by your AS? Asking because my portal looks the same as always.

--
Brad Fleming

On Aug 22, 2019, at 4:49 PM, Jeff Bartig <> wrote:

 

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