Proposal to Clean Up Whois Database

Slides:

Advertisements

Similar presentations

Technical Aspects of the Transitional Process Mexico City, 11/12 Nov 2002 Frederico A C Neves.

Advertisements

Database SIG Summary Report Chair – Xing Li APNIC Annual Member Meeting Bangkok, March

Open action items Database SIG APNIC 18 Nadi, Fiji.

Protecting Resource Records in APNIC Whois Database Database SIG APNIC-16, Seoul August 2003 Sanjaya

Technical Services Report March 6th, 1999 Singapore.

APNIC DB SIG Report Taipei 2003 Xing Li

APNIC Internet Routing Registry Routing SIG APNIC-15, Taipei 26 February 2003.

January 6. January 7 January 8 January 9 January 10.

Whois Database Clean Up Project Report Database SIG APNIC 16, Seoul, Korea 20 August 2003.

Database Update Kaveh Ranjbar Database Department Manager, RIPE NCC.

Sweeping lame DNS reverse delegations APNIC16 – DNS Operations SIG Seoul, Korea, 20 August 2003.

1 prop-018-v001 Protecting historical records in the APNIC Whois Database Project Update DB SIG APNIC18 2 September 2004 Nadi, Fiji Sanjaya, Project Manager,

Software Compliance: Are we there yet? Looking back and moving forward.

Database Update Paul Palse Database Manager, RIPE NCC.

Database Update Kaveh Ranjbar Database Department Manager, RIPE NCC.

Regional Internet Registries Statistics & Activities IETF 55 Atlanta Prepared By APNIC, ARIN, LACNIC, RIPE NCC.

1 Use role objects …to maintain your contacts in APNIC whois.

Status report on Lame Delegations (work in progress) George Michaelson DB SIG APNIC17/APRICOT 2004 Feb KL, Malaysia.

1 APNIC Status Report SANOG VI July 2005, Thimpu, Bangladesh Kapil Chawla, APNIC.

18th APNIC Open Policy Meeting SIG: DB Thursday 2 September 2004 Nadi, Fiji Chair: Xing Li.

APNIC Status Report ARIN X Eugene, Oregon Oct 30-Nov 1, 2002.

Consultation on Policy Documentation Adam Gosling APNIC 40 Policy SIG 10 September 2015.

Prop-007-v001 Privacy of customer assignment records Project Update DB SIG APNIC 18 1 September 2004 Nadi, Fiji Sanjaya, Project Manager, APNIC Secretariat.

Olaf Kolkman. APNIC 15, February 2003, Taipei. 1 RIPE Database Operations Update Olaf Kolkman RIPE NCC.

Network Abuse Update Frank Salanitri Project & Systems Services Manager, APNIC.

Sweeping Lame DNS Delegations A Proposal DNS OPS SIG APNIC 15, Taipei, Taiwan 26 February 2003.

Whois Domain Object Authorisation APNIC18 – DB SIG Nadi, Fiji 2 September 2004.

Andrei Robachevsky. 12th APNIC Open Plicy Meeting, August 2001, Taipei, Taiwan. 1 New Version of the RIPE Database Andrei Robachevsky.

Update of WHOIS Data Privacy in JP Izumi Okutani Japan Network Information Center (JPNIC) DB SIG APNIC Indonesia.

SunSatFriThursWedTuesMon January

APNIC IRR Pilot Project Transition to Operating Service.

1 Lame delegation status report DNS Operations SIG APNIC , Hanoi.

APNIC Feb., 2004 Copyright (c) 2004 Japan Network Information Center. All Rights Reserved.1 NIR System BoF report for NIR SIG Shin Yamasaki Engineering.

Engineering Update Key Projects –IPV6 Registration function is completed, tested, and ready for production IPV6 WHOIS completed, tested, and ready for.

Prop-007-v001 Privacy of customer assignment records Project Update DB SIG APNIC February 2005 Kyoto, Japan Sanjaya, Project Manager, APNIC Secretariat.

Whois Update Guangliang Pan. Overview Differences between APNIC and RIPE Whois Databases Change mnt-by from member’s maintainer to APNIC-HM for aut-num.

Implementation of ARIN's Lame DNS Delegation Policy

Whois Data Privacy Issues in Japan

Lame DNS Server Sweeping

LACNIC IV Santiago, Chile April, 2003

AFRINIC Services Update

RPPP Policy and Procedures Update

RIPE Whois Database Software Recent Changes

APNIC 29 Policy SIG report

Joint IPv6 Forum/IPv6 SIG APNIC 15, Taipei, Taiwan 26 February 2003

NIR SIG, 18th APNIC Meeting

Sanjaya, Project Manager, APNIC Secretariat

APNIC 14 DB SIG Report Xing Li

Strategic Planning Timeline Overview

Policy SIG Chair Report

A week in the life of (IRT address)

A Proposal to Protect Historical Records in APNIC Whois Database

February 2007 Note: Source:.

MyAPNIC Project Update

Updating Databases With Open SQL

Timeline Overview Planned Timescales

Requirements for running a local WHOIS service

Proposal to Deprecate MAIL-FROM in Maintainer Object

Overview of policy proposals

Privacy of Customer Assignment Records

Recovery of Historical Resources Status Update

IPv6 technical SIG 27 February 2008 APNIC 25, Taipei Anna Mulingbayan

Status Report on Policy Implementation at the APNIC Secretariat

Database SIG APNIC19 24 February 2005, Kyoto, Japan

Whois Database Upgrade

Status on “Proposal for the whois database query”

Updating Databases With Open SQL

prop-025-v001 Proposal on IPv6 IRR service at APNIC

2015 January February March April May June July August September

By Keessun Fokeerah Member Services(MS) Team

Presentation transcript:

Proposal to Clean Up Whois Database Database SIG APNIC 15, Taipei 26 February 2003

Proposal Remove whois records that are not related to actual resource information Remove resources information that are not in APNIC range Modify records that are not RPSL compliant Notes: Removals/modification will be made after 60 days notice to the record holders Activities reported regularly in DB-SIG and AMM

Source of error Historical data Data conversion error when upgrading from Whois v2 to Whois v3 Records not being properly maintained

Current Statistics As of 31st January 2003 Unused Maintainer: 21 Unused Person/Role: 27,554 Inetnum outside of APNIC range: 116 RPSL errors: aut-num: 15 mntner: 206 inetnum: 413 inet6num: 0

Motivation Quality Performance Usability APNIC db must contain correct data Performance Unused objects creates unnecessary burden on the server Usability Non-conformance historical data cannot be updated (wrong admin-c, nic-hdl, maintainer etc)

Objects Affected To be removed: To be corrected: Unused maintainers Unused person/role objects inetnum/domain outside of APNIC range To be corrected: autnum inetnum mntner A total of 28,000+ objects

Implementation Proposed Timeline 7 April 2003: Public announcement mails to contacts of affected objects project information and list of the affected objects in APNIC website 9 June 2003: Delete unused objects 7 July 2003: Correct RPSL non-compliance records Correction to data conversion error: as soon as possible

Discussion Consensus from DB SIG to proceed with this proposal?