[sig-db]Proposal of IRR mirroring policy(P)

["Matsumoto, Junichi" <matsumoto@gw.odn.ad.jp>]

Dear all,
(B
(BI am Junichi, from JPNIC jpirr planning team.
(BThis wil be a proposal papers presented at Database SIG, at Korea.
(B
(BA brief synopsis of the proposals is provided below.  Please take some
(Btime to go through this synopsis, and post any issues or questions on
(Bthe sig-db@apnic.net mailing list. 
(B
(B> To Chair of SIG-DB
(BI fixed sentences a little in a proposal paragraph for more
(Bunderstanding.
(B
(B--------------------------------------------------------------------
(BProposed by: JPNIC
(BDate: 16 July 2003
(B
(BA Proposal of Policy for Mirroring on IRR
(B
(B1.	Background
(B
(BAn IRR owner has a responsibility of managing its IRR's database, and 
(Bcurrently, the owner exchanges just IRR database he owned.  If the owner
(Ballowed the other IRRs to transfer its IRR database without any rule,
(Bthe IRR database would spread anywhere and could not be managed any more. 
(BThis is a proposal to define the policy of limitation for transferring
(BIRR database which includes data of source not to be owned.
(B
(B2.	Proposal
(B
(BThis is a proposal that each IRR may have a policy of mirroring as 
(Bfollows, and a IRR does not transfer the database of other IRR's source
(Bwithout permission of the IRR of the database if the owner of the
(Bdatabase has this policy.
(B
(B  $B!H(BWhen a receiver of IRR receives IRR database from the transferrer of 
(BIRR by mirroring between them, the receiver MUST request the permission
(Bof receiving the database to owners of source IRR that is included in
(Bthe receiving database, and MUST ask the owners to submit their
(Bpermission to the transferrer of IRR database.  The transferrer of IRR
(Bdatabase MUST NOT send the database without the permission of owners of
(Beach source$B!I(B.
(B
(B3.	Purpose
(B
(BThe purpose of this proposal is that an IRR is able to know every other 
(BIRR which receives the database originated by it, and is able to limit
(Bthe receiver of its database by itself.  Without this limitation, IRR's
(Bowner could not care of spreading their user$B!G(Bs information to any out
(Bof their management, and its database might be tampered.  The limitation
(Bof transferring makes IRR$B!G(Bs owners feel easier to agree with
(Btransferring its database.
(B
(B4.	Sample Mirroring Policy
(B
(BJPIRR mirroring policy is an example to satisfy this proposal.  Please
(Bsee JPNIC homepage,
$B!H(Bhttp://www.nic.ad.jp/en/ip/irr/jpirr-mirroring-policy.html$B!I(B 
(Bto refer for more details.  This page will be updated by 7/28.
(B
(B5.	Implementation
(B
(BThis proposal will hopefully be implemented by all IRRs.  For exchanging
(BIRR database between two NIRs, an NIR asks another NIR to submit the
(Bpermission of transferring to a RIR and RIR transfers the NIR's database
(Bfor exchanging their IRR database.  This is the first step to realize a
(Btree topology of IRR.
(B
(B
(B-=-=-=-=-=-=-=-=-=-=-=-=-=-
(BJunichi Matsumoto
(BJapan Telecom Co., Ltd (AS4725)