MinutesDatabase SIGThursday 2 September 2004, Sheraton Nadi Resort, Nadi, FijiMeeting commenced: 11:10 am Chair: Xing Li The Chair introduced the session and explained the agenda. Review of previous open action items
Contents
Katsuyasu Toyama, NTT Presentation [pdf] This presentation noted that IPv6 is being allocated widely but is still not widely used. He reviewed routing statistics relating to current IPv6 use. He noted that 84 percent of prefixes are currently being 'correctly' advertised and that currently, unlike IPv4, the IPv6 space appears to be very clean. However, he suggested that wider deployment may change this situation. Therefore, the presenter proposed that APNIC establish a trusted IPv6 IRR that would be also be promoted to other RIRs, to contribute to the stable routing of the IPv6 network. The presentation contained a discussion of a possible architecture for the services, but recommended that this should be decided by further discussions in the community. Questions and discussion Action items Sanjaya, APNIC The presentation reviewed the progress of the project to implement privacy of customer assignments in the APNIC Whois Database. The presenter reviewed the background to the original proposal and noted that some technical issues had delayed the implementation. When systems are ready, all portable allocations and assignments will remain publicly visible, but all non-portable resources will be made invisible by default. Responsible custodians will then be able to choose whether to make the customer assignments visible again. The presenter noted that the work to implement this proposal is expected to be completed by 30 September. He outlined the migration schedule. He then provided a demonstration of the tools in MyAPNIC that will be available to account holders to manage the privacy of their customer assignments. The presenter noted that once the migration has happened, emails to auto-dbm will not be able to update private records. However, this functionality should be available in 2005 following APNIC's introduction of a new registry system. The presenter also noted that APNIC will perform a clean up of related objects that become affected. Questions and discussion Action items Sanjaya, APNIC The presentation reviewed the progress of the project to introduce protection of historical address space records. It was noted that unprotected historical registrations are subject to being used for abusive purposes. APNIC will apply the APNIC-HM maintainer to all unprotected historical inetnum and aut-num records. Custodians will still be able to use the resources. Those who wish to have their own maintainer (mnt-lower) applied to the resources will be required to verify their right to custodianship and open an account with APNIC, with an annual fee of $100 per year. The presenter outlined the technical and administrative steps that are required to complete implementation. Systems are expected to be completed by the end of October. Full implementation is expected by early December 2004 and will be reported on in APNIC 19. Questions and discussion Action items Elly Tawhai, APNIC The presenter discussed a current procedural problem for non-users of MyAPNIC submitting domain objects to whois. The hierarchical nature of authorisation can cause automatic submissions of domain objects to fail. Currently, such objects have to be manually created by APNIC hostmasters, which causes some delay. The presentation contains details of the procedural solutions for this problem. This new procedures are intended to be implemented by the end of 2004. Questions and discussion Action items Laura Cobley, RIPE NCC The presenter reviewed the most recent changes to the RIPE Whois software. The most recent changes are not yet available for download, but will be soon. Support for X.509 has been added to improve security features. The organisation object has been introduced to help track organisations which hold resources. Reverse DNS procedures have been completely overhauled. Domain and DNS records are no longer maintained separately and X.509 support has been added. Domain objects are now the sole source. NONE authentication has been deprecated and there are now no unprotected objects in the database. Other changes include use of CIDR notation to create inetnums; prefix range lists for mnt-routes; and overlapping inetnum objects are now longer able to be created. Questions and discussion Action items Meeting closed: 12:55 pm Minuted by: Gerard Ross Open action items
|
