Are You Ready for Google’s New Peering Requirements?
The rules for interconnecting networks that form the global Internet are changing in ways that impact the Internet2 community.
Without important action, new rules from network operators such as Google and Hurricane Electric, will significantly reduce efficiencies members receive for their investments in Internet2's peering service--I2PX (formerly TR-CPS).
Without action by campuses and regional networks these new rules will cause more traffic to be forced onto commercial internet links, potentially leading to higher internet costs. The changes are being implemented now, through the end of the year.
Internet2 is preparing a short-term fix to mitigate the adverse effect on I2PX efficiency; however, a complete solution requires widespread use of Internet Routing Registries (IRRs) by the broader community.
IRRs provide network operators (such as Google) with the documentation they require from peer networks to route traffic to users. If customers' IP addresses aren't recorded in an IRR, then the network operator (e.g., Google) won't accept those announcements.
Campuses and/or Regional R&E Networks need to maintain IRR entries to solve this problem--and also to help guard against route hijacking and internet outages. Internet2 is actively working to ensure the community is well-informed and has access to the knowledge and resources required to comprehensively adopt the use of IRRs.
Networking teams should take these actions promptly to better understand the purpose and use of IRRs.
- Become a member of the NTAC IRR working group by sending e-mail to firstname.lastname@example.org. Membership in this list will ensure you receive information concerning Internet2's short-term mitigation efforts to reduce the impact on the peering service.
- Attend the webinar on August 21, 2019 at 11:00 a.m. ET.
Registering in the IRR: An introduction to IRR object registration via RADb.net
A practical introduction to the Internet Routing Registry (IRR), Routing Policy Specification Language (RPSL), and usage of the RADb.net web platform to register IRR objects.
This presentation will step through the best practices and creation of aut-num, route, and asset objects for MANRS collaboration and Internet exchange (IX) participation. The positive publication of prefix+origin pairs enables neighbors and transit operators to better guard against prefix hijacking and route table leaks. We'll briefly touch on the opportunities available to network operators to consume IRR for more automated router configuration and prefix list generation. This session is ideal for current and prospective IRR users.
Join Zoom Meeting
One tap mobile
+16465588656,,993488896# US (New York)
+16699006833,,993488896# US (San Jose)
Dial by your location
+1 646 558 8656 US (New York)
+1 669 900 6833 US (San Jose)
Meeting ID: 993 488 896
Find your local number: https://zoom.us/u/aoVMYfuoU
Join by SIP
Join by H.323
220.127.116.11 (US West)
18.104.22.168 (US East)
22.214.171.124 (Hong Kong)
Meeting ID: 993 488 896
Join by Skype for Business