70 likes | 84 Views
Explore the history, goals, issues, and timeline of the APNIC IRR pilot project transition to an operating service. Learn about the goals of providing authoritative routing information and the challenges faced in integrating and authorizing route objects. Follow the timeline from the project initiation to final withdrawal.
E N D
Overview • History • Goals • Issues • Timeline
History • APIRR project initiated with support and encouragement of the APNIC db sig, member community • JP IRR wg provided input, motivations, leadership • APIRR pilot showcased at JANOG 2002 Toyama • 30+ mirrors • Meshed with RADB/RIPE IRR
Goals: integration • Provide authoritative routing information • Route object authorization derives from inetnum and aut-num permissions • Only RIR & NIR can be authoritative about inetnum and aut-num objects • Permit cross-registry authentication • Single source for whois at APNIC • LIR Can still run 'non-authoritative' RR
Issues • Data needs to be back-imported • Only IRR-related updates to core APNIC data • Some data was experimental • Will require checking, confirmation from maintainer • Liaison with RADB,RIPE,<mirrors> • Withdraw source APIRR after successful re-sync with source APNIC • Concerns about AS assignment records in registry having import/export value from application
Timeline • Jan APIRR pilot launch at JANOG 2002 • Mar-Aug APNIC whois V3 deployment project • Sep Identify extra routing objects in APIRR after reload from source APNIC • Nov Complete insertion into source APNIC, add APNIC to RADB, mirrors • Dec Withdraw APIRR from RADB, mirrors