Re: [sig-db]Proposal of IRR mirroring policy(P)
(Bhttp://www.nic.ad.jp/en/ip/irr/jpirr-mirroring-policy.html
(BThis policy is based on our proposal.
(B
(BThank you,
(B
(BJunichi
(B
(BOn Wed, 16 Jul 2003 18:59:30 +0900
(B"Matsumoto, Junichi" <matsumoto at gw.odn dot ad dot jp> wrote:
(B
(B] Dear all,
(B]
(B] I am Junichi, from JPNIC jpirr planning team.
(B] This wil be a proposal papers presented at Database SIG, at Korea.
(B]
(B] A brief synopsis of the proposals is provided below. Please take some
(B] time to go through this synopsis, and post any issues or questions on
(B] the sig-db at apnic dot net mailing list.
(B]
(B] > To Chair of SIG-DB
(B] I fixed sentences a little in a proposal paragraph for more
(B] understanding.
(B]
(B] --------------------------------------------------------------------
(B] Proposed by: JPNIC
(B] Date: 16 July 2003
(B]
(B] A Proposal of Policy for Mirroring on IRR
(B]
(B] 1. Background
(B]
(B] An IRR owner has a responsibility of managing its IRR's database, and
(B] currently, the owner exchanges just IRR database he owned. If the owner
(B] allowed the other IRRs to transfer its IRR database without any rule,
(B] the IRR database would spread anywhere and could not be managed any more.
(B] This is a proposal to define the policy of limitation for transferring
(B] IRR database which includes data of source not to be owned.
(B]
(B] 2. Proposal
(B]
(B] This is a proposal that each IRR may have a policy of mirroring as
(B] follows, and a IRR does not transfer the database of other IRR's source
(B] without permission of the IRR of the database if the owner of the
(B] database has this policy.
(B]
(B] $B!H(BWhen a receiver of IRR receives IRR database from the transferrer of
(B] IRR by mirroring between them, the receiver MUST request the permission
(B] of receiving the database to owners of source IRR that is included in
(B] the receiving database, and MUST ask the owners to submit their
(B] permission to the transferrer of IRR database. The transferrer of IRR
(B] database MUST NOT send the database without the permission of owners of
(B] each source$B!I(B.
(B]
(B] 3. Purpose
(B]
(B] The purpose of this proposal is that an IRR is able to know every other
(B] IRR which receives the database originated by it, and is able to limit
(B] the receiver of its database by itself. Without this limitation, IRR's
(B] owner could not care of spreading their user$B!G(Bs information to any out
(B] of their management, and its database might be tampered. The limitation
(B] of transferring makes IRR$B!G(Bs owners feel easier to agree with
(B] transferring its database.
(B]
(B] 4. Sample Mirroring Policy
(B]
(B] JPIRR mirroring policy is an example to satisfy this proposal. Please
(B] see JPNIC homepage,
(B] $B!H(Bhttp://www.nic.ad.jp/en/ip/irr/jpirr-mirroring-policy.html$B!I(B
(B] to refer for more details. This page will be updated by 7/28.
(B]
(B] 5. Implementation
(B]
(B] This proposal will hopefully be implemented by all IRRs. For exchanging
(B] IRR database between two NIRs, an NIR asks another NIR to submit the
(B] permission of transferring to a RIR and RIR transfers the NIR's database
(B] for exchanging their IRR database. This is the first step to realize a
(B] tree topology of IRR.
(B]
(B]
(B] -=-=-=-=-=-=-=-=-=-=-=-=-=-
(B] Junichi Matsumoto
(B] Japan Telecom Co., Ltd (AS4725)
(B]
(B] * sig-db: APNIC SIG on whois database issues *
(B]
(B] _______________________________________________
(B] sig-db mailing list
(B] sig-db at lists dot apnic dot net
(B] http://mailman.apnic.net/mailman/listinfo/sig-db
(B
(B-=-=-=-=-=-=-=-=-=-=-=-=-=-
(BJunichi Matsumoto
(BJapan Telecom Co., Ltd (AS4725)
