80 likes | 175 Views
This proposal suggests the implementation of an IRR Mirroring Policy for efficient exchange and sharing of database among RIRs, NIRs, and LIRs, addressing issues in the current hierarchical topology. The policy outlines steps for defining, proposing, and deploying the common policy at APOPM for consensus and operational model improvement.
E N D
A Proposal of “IRR Mirroring Policy” Junichi Matsumoto JPNIC IRR-planning team Japan Telecom CO., LTD.
1. Review IRR hierarchical topology • Consensus at 13th APOPM • An IRR Operational Model, which was like a hierarchical topology of registry system APNIC ARIN RIPE NIR A NIR ・・・ LIR ・・・ LIR LIR
1. Review • Characteristics of this model • RIR/NIR IRR exchange and share their own database. • RIR/NIR share “PUBLIC database” • LIRs receive the shared PUBLIC database. • A LIR needs to mirror just one RIR/NIR
2. Issues Collecting Issue • An IRR needs negotiations with several IRRs toreceive database. • Too many bi-lateral agreements are needed! RADB APNIC RIPE LIR LIR JPNIC LIR LIR
LIR C LIR B 2. Issues Distributing Issue • IRR’s database is transferred to unintentional IRRs. • Unknown owner of IRR might abuse the database. APNIC JPNIC LIR LIR A
3. Proposal • Define and deploy “IRR Mirroring Policy” • The policy shall include; • RIRs and NIRs exchange and share their PUBLIC database. • RIR/NIRs transfer shared PUBLIC database to downstream IRR by their decision. • LIR’s IRR receives PUBLIC database from an upstream IRR, but cannot transfer the database.
4. Implementation process • Defining and deploying process • 1st Step Defining the detail of this common policy • 2nd Step Proposing the common policy at APOPM • 3rd Step Deploying this policy among RIRs and NIRs.