Asia Pacific Network Information Centre (APNIC) 17 Meeting Report

 

Author：David Shi-Wei Chen

 

Purposes

 

APNIC 17 was held successfully as one of the tutorial and conference tracks at APRICOT 2004 in Kuala Lumpur, Malaysia between 23-27 February. The meeting included APNIC training, tutorials, Special Interest Groups (SIGs), Birds of Feather sessions (BOFs), hostmaster consultations, the APNIC Member Meeting, and a social event. The purposes of attendance were to deliver the latest Taiwan Internet resource management status to public, discuss new proposal of resource management and policy, receive new technical information, as well as to establish further strong relationship with APNIC and NIRs.

 

Conference and SIG discussion

 

I attended many sessions such as NIR system BOF, NIR workshop, hostmaster consultations, IPv6 SIG, Policy SIG, Database SIG, Member Meeting and social event.

 

NIR System BOF:

The meeting was held on Monday, February 23rd, at 16:00 - 17:30    Room: Majestic I. We discussed two issues, one is IPv4 direct allocation and DNS setting, the other is the requirements for data exchange between APNIC system and NIR system.

 

TWNIC has not implemented IPv4 direct allocation yet since the policy announced on Dec 2002. But we still concerned about the impact after setting reverse DNS flow changed. I also suggested that APNIC need to cross check the reverse DNS zone file in a period of time such as everyday or 3 days or one week. NIRs would provide their own reverse DNS zone file to APNIC depending on the frequency of cross checking.

 

APNIC will provide a client program to NIRs for data exchange between APNIC and NIRs. This program will base on XML and client/server structure. It will deliver on Q3 2004. I required that APNIC need to retain the email parser function for original update.

     

NIR Workshop:

The meeting was held on Monday, February 23rd, at 17:30 - 19:00    Room: Majestic I. The meeting comprised two presentations which were provided by KRNIC and JPNIC. We discussed on IRR structure and how hostmater implement APNIC policy. We shared the experience of Internet resource management with NIRs.

     

Hostmaster Consultation:

The consultation was held on Tuesday, February 24th, at 10:00 – 17:00 Room: Conference V. I consulted with APNIC MHs and Son regarding when TWNIC will allocate /21 to TWNIC’s member after min allocation size proposal be made consensus at OPM.

 

Son said that we have to wait 3 months after the policy announced. Don’t implement now, but you could negotiate with customer after this meeting to prepare in advance.

 

SIGs:

In Policy SIG, One of TWNIC’ member, SeedNet, proposed an amendment which is to modify subsequence allocation criteria in IPv4 allocation policy guide line. This proposal has made a consensus to form a working group for guide line reviewing.

 

       In Database SIG, we discussed about Protecting Historical Records in APNIC Whois Database. I gave one point of my view in the meeting. That is if the marked records is belong to NIRs’ member, APNIC should list these record to NIRs for reference.
 
       In NIR SIG, JPNIC gave two presentations. One is JPNIC OPM updated, the other is JPNIC status updated. I also prepared one presentation whose topic is TWNIC first OPM updated and answered two questions regarding the policy making processing flow and how to encourage participants to join the discussing mailing list.
Each NIR reported their country operation status in NIR SIG.

 

Suggestions

I suggested that TWNIC could encourage IPv6 project division to submit proposal or informational presentation in IPv6 SIG and promote TWNIC’s member to join each SIG discussion or publish papers.

TWNIC should set a long term strategy of APNIC attendance in the future.

TWNIC should announce and follow up APNIC17 policy which made consensus on APNIC 17 Open Policy Meeting to TWNIC’s members after these policies have been reported to TWNIC IP COMMITTEE.