$Id: apnic-db-regist.txt,v 1.1.1.1 2001/06/02 06:03:17 kenken Exp $ How to regist IPv6 address in the APNIC Database. 1.Introduction It is defined that sub-TLA address must be registerd in the APNIC database every assignment and allocation (IPv6 policy draft 2.2.4). So this document describes how to regist IPv6 address in the APNIC Database. Note that APNIC is one of the Regional Internet Registry(RIR), and this way may apply to another two RIRs(RIPE,ARIN). 2.APNIC database overview APNIC database is consists of various objects.Objects are set of attiributes about addresses and networks per organizations, such as IPv6 address(inet6num),AS numbers(autnum),routing information(route). The most important matter is that all objects are under control of Maintainer object.(fig.1) +--------------+-create/update--->person |maintainer |-create/update--->autnum | object |-create/update--->route |ex. |-create/update->inet6num(ex.inet6num:2001:200::/35 |MAINT-JP-WIDE | mnt-by:MAINT-JP-WIDE +--------------+ tech-c:AA1-AP... ) fig.1 apnic database model If the organization wants to update/create autnum,inet6num,route, and person(except for maintainer object),there needs 2 steps. 1.authentication By using password,check whether the request that was issued by the organization is a proper request or not. 2.authorization By checking "mnt-by" field in person object ,check if the person who wants to create/update has the authorization.(ex is fig2) person: Kengo Nagahashi address: 5322 Endo FUjisawa City Kanagawa Pref. Japan country: JP phone: +81-49-1394 fax-no: +81-49-1101 e-mail: kenken@sfc.wide.ad.jp nic-hdl: KN9-AP mnt-by: MAINT-JP-WIDE changed: kenken@sfc.wide.ad.jp 20000114 source: APNIC fig.2 sample of person object In fig.2,mnt-by is MAINT-JP-WIDE,it means that KN9-AP has the authorization to update/access all "mnt-by: MAINT-JP-WIDE" objects . Note that to create Maintainer object,it is need to get account name(become a APNIC membership).And all Maintainer objects are created by hand(it takes 2-3 days to finish it). 3.Approaches to update APNIC database Address allocation structure is fig.3. +--------+ +-------+ +-------+ |sTLA A |--->|NLA1 B |--->|NLA2 C | |MAINT-A | |MAINT-B| |MAINT-C| +--------+ +-------+ +-------+ fig.3 address allocation structure It is assumed that there are 2 ways to be registered IPv6 address in APNIC DB. 1.sTLA A creates each organization's(NLA1 B,NLA2 C) Maintainer object and then NLA1 B or NLA2 C creates inet6num object by own. 2.sTLA A creates only inet6num of NLA1 B or NLA2 C The most difference between 1. and 2. is whether sTLA A creates maintainer object or not. *strong point of 1. -NLA1 B can create/update inet6num by own. *weak point of 1. -MAINT-A must inform raw-password to MAINT-B. -It takes time to create maintainer object. *strong point of 2. -It is no need to create another Maintainer object. -MAINT-A just creates inet6num and it is processed automatically. *weak point of 2. -NLA1-B(just same as NLA2-C) can't update its inet6num by own. WIDE IPv6 registry selects 2(create only inet6num) because it takes less human resources than 1. 4.Actual Registration it's an example,following NLA1 request are comming via e-mail.(fig.5). inet6num: 2001:200:y000::/40 netname: test-net descr: NLA1 allocation from WIDE-JP country: JP admin-c: AA1-AP tech-c: BB1-AP notify: you-email-address@mail Then based on this request,send a request message to APNIC(auto-dbm@apnic.net) To:auto-dbm@apnic.net -- inet6num: 2001:200:y000::/40 netname: test-net descr: NLA1 allocation from WIDE-JP country: JP admin-c: AA1-AP tech-c: BB1-AP mnt-by: MAINT-A (notify: contact-MAINT-C@email # if this is NLA2 record, we should add contact person at NLA2.) notify: contact-MAINT-B@email notify: contact-MAINT-A@email # if changes, then notify it. upd-to: contact-MAINT-A@email # if update error, then notify it. changed: someone@email 20000101 # who/when made this change source: APNIC password: MAINT-A's password After just minutes, APNIC db manager will reply the request messages automatically. And if subject is "SUCEED", you can't need to do else, but the subject is "FAILED", you should confirm your request again. 6.Reverse DNS delegation As there is little description about reverse DNS delegation in IPv6 policy draft,WIDE IPv6 registry define reverse DNS delegation rules. 1.WIDE IPv6 registry only can delegate reverse DNS zone after APNIC database are registerd. 2.All reverse DNS delegations are processed by WIDE IPv6 registry.Because WIDE IPv6 registry manages and registers APNIC DB.