wg-irr - Re: [WG-IRR] Google IRR based route filtering public announcements
Subject: Registry Working Group
List archive
- From: Bill Owens <>
- To: "" <>
- Subject: Re: [WG-IRR] Google IRR based route filtering public announcements
- Date: Fri, 16 Aug 2019 12:46:13 +0000
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nysernet.org; dmarc=pass action=none header.from=nysernet.org; dkim=pass header.d=nysernet.org; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=oGZ0zbMneFl2mlHYIviqorae61YS7XONZx5ep7Nm9+g=; b=LINzpnb6abU5lv2X+G+K0+ONIIpEWBtp+Solt9gH6lxWEqLhhvChY//IgZU44qZRYp/uRhDhSXJjpPb3Cy5ud831GHAsAnUnK1VHoQwkc2AMtcw3x+hWSfIxRPcECSKUZAfJ7qCBr3NRjCgo9sAHOoGad64i36yJXIQ8HXAjv6kymD7Cy6b4JWGEpw8mTyzBq6BBxHlrjn4gPSVfOSH5nyXlKLqxUt5Z+CvAWISTgwBN4lj1zpL5OZXUeXQdBVWWtj8+HZoAR0zi9Iz9yTDVE414vC2KBa3kSz6kmPLGxr+6y/zEE3+DCVWagaB/hBTWm70g9fAQOsV/Nnn+d/q1GA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=St/tIx8svn9Ls5GuW139re/KY2Zat1G+lSf+AqBBmVzj6btscZSO2poTeitbD/3BKYQa/tsme/I29yn9s0fDVLN2dyy4rPVUI2zbpr7hX+qYz/8m+1UWpst3Jhh4Fzv/UrrmZo5nPLWlp4hMJes+g/EokeNYMr2EK16mVy+Kkg04xWlnofwSPpMGaa1lBJ0CsZ+162qnSAeB3596YfIJUCuRnm0dNcsrhzJ33DAL6Og+ZKw1N3psdpypG7Qw2FaaO4pgdVzWBSCKq4pdwu4u+2nfmFXEdSu6vCOv+PG3lWGAgjAEigGLzsu5J/47bQXGnjjlU/hc9S5YcgkAAUulng==
I remember reading that and assuming that the deficiency was that the tools aren’t written (or re-written) in Go…
Of course that problem is being remedied: https://github.com/manrs-tools/
I’ve been wondering about the more-specific routes, and so far we’re playing it safe and registering route objects for everything that any of the campuses wants to advertise*. That also keeps IRRExplorer happy since it looks for an exact match, but I have the sneaking suspicion that Google will allow orlonger at the end of their filters, to reduce the number of routes that are incorrectly (or at least unnecessarily) dropped.
Bill.
* Some of them have interesting schemes for ‘balancing’ traffic between links by dividing their /16s down as far as /24. I’m not sure they realize how asymmetric their paths are as a result, but that can be a conversation for a later date.
From: <> on behalf of Michael Hare <>
Unless someone else has insight, I may reach out to Google (Arturo) for clarification on
https://ripe78.ripe.net/presentations/54-Route-Filtering-at-the-Edge-AS15169-Connect-%40RIPE.pdf where he says regarding tooling Bgpq3 - not usable (internal problems)
I presume by internal problems he means some problem related to Google processes (such as the desire/need to scrape many sources) and not the BGPQ3 tool itself.
Slightly OT but midweek I built a filter for AS3128 based on BGPQ3 output for our as-set, applied it to a transit export mockup and found some issues to tackle. Most of my fixes will be to suppress more specifics [no-export] and rely on route aggregation, a few are asking a multihomed downstream AS to add more specifics to the IRR. I ran into what appears to be a Juniper bug re: aggregate route creation on 16.1 and will be following up with JTAC later today. If anyone is interested in the results of that just ask (public or private).
-Michael
From: <>
On Behalf Of Bill Owens
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 <>
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? --
|
- [WG-IRR] Google IRR based route filtering public announcements, Jeff Bartig, 08/15/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Michael H Lambert, 08/15/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Jeff Bartig, 08/15/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Matt Valenzisi, 08/15/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, David Farmer, 08/16/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Bill Owens, 08/16/2019
- RE: [WG-IRR] Google IRR based route filtering public announcements, Michael Hare, 08/16/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Bill Owens, 08/16/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Jeff Bartig, 08/22/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Ryan Harden, 08/22/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Bill Owens, 08/23/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Jay Ford, 08/23/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Brad Fleming, 08/26/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Bill Owens, 08/26/2019
- RE: [WG-IRR] Google IRR based route filtering public announcements, Michael Hare, 08/16/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Jeff Bartig, 08/15/2019
- Re: [WG-IRR] Google IRR based route filtering public announcements, Michael H Lambert, 08/15/2019
Archive powered by MHonArc 2.6.19.