APNIC Home
APNIC Meeting MenuMeeting Results
APNIC Meeting MenuSIGs
APNIC Meeting MenuBOFs
APNIC Meeting MenuProgramme
APNIC Meeting MenuAMM
APNIC Meeting MenuHM Consultation
APNIC Meeting MenuAC Election
APNIC Meeting MenuSponsors
APNIC Meeting MenuSocial Event
APNIC Meeting MenuPast meetings
APNIC Meeting MenuAPNIC 12 Home
APNIC Meeting MenuAPNIC Home
   

12th APNIC Open Policy Meeting

SIG: Reverse DNS

Thursday 30 August, Grand Hotel, Taipei
minutes

Meeting commenced: 11.10

Chair: Paul Gampe

The Chair introduced the SIG and explained the agenda.

Contents

Presentations

  1. IN-ADDR nameserver hosting status report
  2. Ray Plzak, ARIN

    This presentation outlined the difficulties currently experienced with IN-ADDR delegations smaller than /8 and the project underway to streamline the process. Legacy space delegations are to be administered by the RIR that has most of that space registered in its database.

    Questions and discussion

    No questions.

    Top

  3. AUNIC legacy in-addr transition status report
  4. George Michaelson, APNIC

    This presentation outlined the transition of AUNIC IP address records to the APNIC database. The transition required the creation of APNIC nic-handles based on the AUNIC nic-handles, for improved maintainer security. One fifth of the contacts were no longer valid, and valid contacts needed reassurance about the status of their records after the transfer. Historical allocations predate APNIC policy and so must have different standards applied to them. The process for resolving address ownership disputes is still to be fully determined.

    Questions and discussion

    There was discussion about similar transitions performed in the past, which have been similar in nature, although the allocation sizes were different.

    There was discussion of the difference between the AUNIC migration and the upcoming swamp migration.

    There was a discussion of the problem of notifying address holders whose contacts are invalid. It was explained that during the AUNIC migration, a decision was made turn maintenance rights from invalid contacts to APNIC.

    It was suggested that the most significant issue resulting from the AUNIC transition is the question of ownership, and that a decision is needed on who is legally liable to resolve ownership disputes. It was noted that in a recent case in the ARIN region, the court declined to take responsibility and returned the responsibility of decision making to ARIN.

    A question was raised as to whether it was valid for APNIC to take on liability for the allocation decisions made by AUNIC that may be in dispute at any time in the future.

    Top

  5. Bind-9 status report
  6. Bill Manning, Nominium

    This presentation outlined BIND-9 development, including multilingual DNS and what will be gained by upgrading to BIND-9.

    Questions and discussion

    There was a discussion about when BIND-9 may be usable for APNIC production of rDNS.

    It was noted that BIND-8 libraries would still be available in BIND-9.

    There was a question raised about the memory costs of combining zone transfer into the main daemon. It was explained that this decision was taken in BIND-9 because memory is cheap.

    It was noted that BIND-9 does not yet have the performance needed to deal with extremely high query levels.

    Top

  7. Operational testing of new DNS RR types (and features)
  8. Bill Manning

    This presentation outlined the creation of a testbed for proposed new DNS features, to counter the disadvantages in lab environments. Any proposed features must first be approved by ICANN and tests are conducted for a specified amount of time.

    Questions and discussion

    No questions.

    Top

  9. APNIC Reverse DNS Status
  10. Bruce Campbell, APNIC

    This presentation outlined APNIC-registered in-addr.arpa delegations and the associated object limitations.

    Questions and discussion

    It was noted that BIND-9 is able to process 9000 queries per second.

    It was explained that that when first making a new delegation, the delegation may fail the automatic processing due to the update checklist, but it will be manually processed by APNIC staff. Once these objects are created and then modified, they will be processed smoothly.

    Top

  11. General discussion
  12. The Chair noted that to date, the reverse DNS SIG has been reactive rather than proactive. He suggested that changes in procedure and service need to be announced before they are implemented (in particular DNSSEC, IPv6, and multilingual domain names).

Meeting closed: 12:20

Minuted by: Sam Dickinson


Last modified: | © 1999 - APNIC Pty. Ltd.
Contact us | Privacy statement