Skip to Content.
Sympa Menu

wg-irr - RE: [WG-IRR] Google IRR based route filtering public announcements

Subject: Registry Working Group

List archive

RE: [WG-IRR] Google IRR based route filtering public announcements


Chronological Thread 
    < Chronological >      < Thread >
  • From: Michael Hare <>
  • To: "" <>
  • Subject: RE: [WG-IRR] Google IRR based route filtering public announcements
  • Date: Fri, 16 Aug 2019 11:41:28 +0000
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=wisc.edu; dmarc=pass action=none header.from=wisc.edu; dkim=pass header.d=wisc.edu; 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=k+TId1GRh4kGbxepwt6VzRwNBE4wsIkJvu16+fv2AE4=; b=Zxa1WAXQ8/JEUyognAEtUUfxgVRQC0GSDLnmhRaZkTC0bR7fln8T8ERtyAH0QqOIVTlSUxCMAuK4vueE9+dqgyHuoRb0SITTm28YfaKqrqQE1VBiERaQ/48yAujFQ8rBwy8gIdiKjlZAKbTWLougdBNcql2KpMyMX2rIArUjqJND1fMqNcB7oHv8rsAJkb1EDQ3bpL6awr5y5l9aWeYwFqiRcETbFJfLpK3KdKilZAXZFthmBYGUuUxqxwJuzHbtKXuQkq67SLapVFfqgEO5qbxaBICbFSFwutVJUuDSjgMs9AQQJvm72xMDJO5PP7EDAyNfQg5A3sqk8Gs5UKD+4Q==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=nAqB3QunbDm31UEN0uBaQRKEtgIK58Qwn6Chn523qC1Az86T3JuT1prktOJWFCEedfoqHIZ8Pp0dyAwwZk/XuNCghqcciWqFxZsuJ7juGv/zd0+9AxLD2fMVocWQaMbWBuuk0nCx+edXDRzP5idl7/xosFnp9EQN9I9Nj4s3GfXM+HdM/OeX24HBs1NeLHwwLDLSdOWo+ecpfyLnDjfxgJq+8rtfZRfjmDLPN6WzWa3HtUXfc7z3QAIcVGLIff1uer6csnYwjm0yNGwr98LbBr2DgOwQwoG1JP8Rz9dqxSHc5whXCIW5Suah64hDNgzxAXI0nD8Oq2WomLECBcfyRw==

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
Sent: Thursday, August 15, 2019 8:05 PM
To:
Subject: Re: [WG-IRR] Google IRR based route filtering public announcements

 

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


Archive powered by MHonArc 2.6.19.

Top of Page