registry DB issues

Kazu Yamamoto (山本和彦) kazu@iijlab.net
Thu, 23 Dec 1999 11:00:52 +0900 (JST)
Previous message: PPP tunnel configuration
Next message: registry DB issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
----Next_Part(Thu_Dec_23_11:00:52_1999_535)--
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

I think it is a good time to explain what's going on between APNIC and
JPNIC. I will explain it with a JPNIC hat.

Some countries has a NIR under a RIR. For example, there is JPNIC in
Japan, which is a sub registry under APNIC.

In such country, *IPv4* address space is allocated as follows:

(1) IPv4 address block is deligated to the NIR by the RIR.
(2) An ISP requests IPv4 address block to the NIR.
(3) The NIR assigns a portion of the IPv4 address block to the ISP.
(4) The ISP assigns some IPv4 addresss to its customers.
(5) The ISP updates customer information on NIR DB.
(6) The NIR configures DNS reverse lookup according to the information.

For IPv6, there are many differences.

(a) The RIR has IPv6 sTLA block and its DB.
(b) An ISP requests a sTLA to the RIR.
(c) RIR assigns a sTLA to the ISP and RIR configures DNS reverse
    lookup (/35) to ISP's DNS server.
(d) The ISP has responsibility to update RIR DB. Also, it is up to ISP
    to configure DNS reverse lookup for its customers.

So, our current question is what roles NIR should play in this model?

Kenken's plan is as follows:

(i)   Prepare NIR DB.
(ii)  ISPs updates NIR DB.
(iii) The NIR syncs its DB with RIR DB.

Currently, this is a tough job, at least for JPNIC. So, WIDE Project
decided to do research on this for JPNIC.

P.S.

As far as (b) is concerned, JPNIC is preparing agency service. For more 
information, see an attached message.

--Kazu

----Next_Part(Thu_Dec_23_11:00:52_1999_535)--
Content-Type: Message/Rfc822
Content-Transfer-Encoding: 7bit

Received: from mgi.iij.ad.jp (mgi.iij.ad.jp [192.168.2.5]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id MAA28007 for <kazu@iij.ad.jp>; Mon, 13 Dec 1999 12:58:28 +0900 (JST)
Received: from sh1.iijlab.net (sh1.iijlab.net [202.232.15.98])
	by mgi.iij.ad.jp (8.8.8/MGI2.0) with ESMTP id MAA17251
	for <kazu@iij.ad.jp>; Mon, 13 Dec 1999 12:58:28 +0900 (JST)
Received: from msgmgr.nic.ad.jp (msgmgr.nic.ad.jp [202.12.30.226])
	by sh1.iijlab.net (8.9.1+3.1W/3.7W) with ESMTP id MAA12755
	for <kazu@iijlab.net>; Mon, 13 Dec 1999 12:57:20 +0900 (JST)
Received: (from majordom@localhost)
	by msgmgr.nic.ad.jp (8.9.3+3.1W/3.7W/JPNIC-msgmgr.def,v-99091900/smtpfeed 0.92) id MAA16386
	for ip-v6-out; Mon, 13 Dec 1999 12:58:27 +0900 (JST)
	(envelope-from owner-ip-v6)
Received: from spool.nic.ad.jp (spool.nic.ad.jp [192.168.10.252])
	by msgmgr.nic.ad.jp (8.9.3+3.1W/3.7W/JPNIC-msgmgr.def,v-99091900) with ESMTP id MAA16381
	for <ip-v6@ml.nic.ad.jp>; Mon, 13 Dec 1999 12:58:26 +0900 (JST)
	(envelope-from owner-ip-v6@msgmgr.nic.ad.jp)
Received: from mx1.nic.ad.jp (mx1.nic.ad.jp [202.12.30.137])
	by spool.nic.ad.jp (8.9.3+3.1W/3.7W/JPNIC-spool.def,v-1.7-1999111822) with ESMTP id MAA03604;
	Mon, 13 Dec 1999 12:58:23 +0900 (JST)
	(envelope-from owner-nir-discuss@whois.apnic.net)
Received: from whois.apnic.net (whois1.apnic.net [203.37.255.98])
	by mx1.nic.ad.jp (8.9.3+3.1W/3.7W/JPNIC-relay.def,v-99111822) with ESMTP id MAA19475;
	Mon, 13 Dec 1999 12:57:15 +0900 (JST)
	(envelope-from owner-nir-discuss@whois.apnic.net)
Received: (from majordom@localhost)
	by whois.apnic.net (8.9.3/8.9.3) id NAA86217;
	Mon, 13 Dec 1999 13:54:02 +1000 (EST)
Received: from mgo.iij.ad.jp (mgo.iij.ad.jp [202.232.15.6])
	by whois.apnic.net (8.9.3/8.9.3) with ESMTP id NAA86203
	for <nir-discuss@ns.apnic.net>; Mon, 13 Dec 1999 13:53:58 +1000 (EST)
Received: from ns.iij.ad.jp (root@ns.iij.ad.jp [192.168.2.8])
	by mgo.iij.ad.jp (8.8.8/MGO1.0) with ESMTP id MAA25502
	for <nir-discuss@ns.apnic.net>; Mon, 13 Dec 1999 12:53:56 +0900 (JST)
Received: from fs.iij.ad.jp (root@fs.iij.ad.jp [192.168.2.9]) by ns.iij.ad.jp (8.8.5/3.5Wpl7) with ESMTP id MAA27381 for <nir-discuss@ns.apnic.net>; Mon, 13 Dec 1999 12:53:56 +0900 (JST)
Received: from Mew.org (mine.iij.ad.jp [192.168.10.205]) by fs.iij.ad.jp (8.8.5/3.5Wpl7) with SMTP id MAA22061 for <nir-discuss@ns.apnic.net>; Mon, 13 Dec 1999 12:53:56 +0900 (JST)
Date: Mon, 13 Dec 1999 12:54:53 +0900 (JST)
Message-Id: <19991213.125453.112542885.kazu@Mew.org>
To: nir-discuss@ns.apnic.net
Subject: [JPNIC ip-v6 170] the entire procedure
From: Kazu Yamamoto (=?iso-2022-jp?B?GyRCOzNLXE9CSScbKEI=?=)
 <kazu@iijlab.net>
X-Mailer: Mew version 1.95b11 on Emacs 20.5 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-ip-v6@nic.ad.jp
Precedence: bulk
Reply-To: ip-v6@nic.ad.jp
X-UIDL: 1772b9ad327dfa95d5aa7022d823aa47

Here is the entire picture of the JPNIC service for sTLA. If you have
comments, please speak up right now.

(0) JPNIC prepares a web page which is a modification version of
    APNIC's one. Also, JPNIC prepares some documents on the service.

(1) A sTLA applicant of JPNIC member (say an ISP hereafter) first
    obtains a APNIC NIC handle from APNIC.

(2) The ISP fills the web then press the submit button. An email will
    be sent to the ISP according to the email address in the form.

	The intention here is authentication of email reachability.

(3) When the ISP receives the email, the ISP checks out the form. If
    there are no errors, the ISP sends the form to JPNIC by email.

(4) When JPNIC receives the email from the ISP, JPNIC sees whether or
    not the form is sent by JPNIC members. If so, JPNIC forwards the
    form to APNIC.

(5) APNIC may want to ask some questions to the ISP. In this case,
    APNIC sends them to JPNIC. JPNIC then relays questions/answers
    between APNIC and the ISP.

(6) APNIC assigns one sTLA to the ISP then tells APNIC. JPNIC relays
    the notification to the ISP.

(7) JPNIC requests payment for the ISP.

(8) The ISP pays the fee.

(9) JPNIC pays 245.76 USD into APNIC account.

--Kazu


----Next_Part(Thu_Dec_23_11:00:52_1999_535)----
Previous message: PPP tunnel configuration
Next message: registry DB issues
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]