Whois Database Upgrade

Slides:

Advertisements

Similar presentations

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

Advertisements

NIR SIG Report Chairs: Izumi Okutani, David Chen.

Operational Policies for NIRs in the APNIC Region NIR Meeting APNIC14, Kitakyushu, Japan 4 Sept 2002.

Open action items Database SIG APNIC 18 Nadi, Fiji.

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

TWNIC RMS Update 16 th APNIC NIR SIG TWNIC Sheng Wei Kuo Aug, 2003.

Overarching Issues. Competing Legislation Legal requirement for mandatory QA of professional membership vs. personal privacy protection legislation Know.

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

Whois Database Clean Up Project Report Database SIG APNIC 16, 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,

Copyright (c) 2005 Japan Network Information Center JPNIC IPv6 registry service experience Toshiyuki Hosaka Japan Network Information Center (JPNIC) September.

Policy Documentation Adam Gosling APNIC 38 Policy SIG Meeting 18 September 2014.

A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E Database SIG APNIC Database Privacy Issues 1 March 2001 APRICOT, Malaysia Fabrina.

Desired IRR Operational Model ~IRR/Whois Interaction~ Kuniaki Kondo (JPNIC IRR Workshop/IIJ) Ikuo Nakagawa (Intec) Takashi Arano (Asia Global Crossing)

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

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.

KRNIC Update Mar. 1, 2006 Jin-man Kim KRNIC of NIDA.

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

JPNIC Open Policy Meeting Update Yuka Suzuki IP Department Japan Network Information Center (JPNIC) NIR Meeting Aug. 21st, 2003.

Windows Server 2003 La migrazione da Windows NT 4.0 a Windows Server 2003 Relatore: MCSE - MCT.

1 Discussion of the new DNS generation system DNS Operations SIG APNIC 18 2nd September 2004, Fiji.

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

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

Whois Database Upgrade Project Update APNIC-14 DB-SIG 4 September 2002

Chapter 4- Part3. 2 Implementing User Profiles A local user profile is automatically created at the local computer when you log on with an account for.

A S I A P A C I F I C N E T W O R K I N F O R M A T I O N C E N T R E APNIC Open Address Policy Meeting DSL/Cable Modem procedures/practices March 1st,

APNIC IRR Pilot Project Transition to Operating Service.

ARIN-prop-180 ISP Private Reassignment Yi Chu Sprint ARIN XXX, Dallas October 25, 2012.

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

APNIC abuse procedures Network abuse BOF. Types of abuse reported Spam Hacking Viruses Identity/credit card fraud Threats and stalking.

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

APNIC IPv6 Allocation Update IPv6 SIG APNIC 14, Kitakyushu, Japan 4 September 2002.

JPNIC UPDATE ~ Personal Data Protection in JPNIC WHOIS ~ Toshiyuki Hosaka Japan Network Information Center (JPNIC) September 7 th, 2005 NIR SIG APNIC

New Hire Packet Automation Factors for Decision Making.

1 [prop-037] Proposal to deprecate updates for APNIC registry and whois data Policy SIG 7 Sep 2006 APNIC 22, Kaohsiung, Taiwan Terry Manderson.

Ha Noi 07 Sept, 2005VNNIC1 VNNIC activities report and plan NIR SIG - APNIC 20 Presented by: Phan Thi Nhung

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.

Factors for Decision Making

Whois Data Privacy Issues in Japan

IPv6 Documentation Address Policy

IPv6 Allocation Status Report

IPv6 Subsequent Allocation

/48 assignment status report

RIPE Whois Database Software Recent Changes

A Proposal for IPv4 Essential Infrastructure

APNIC 29 Policy SIG report

Downstream Allocations by LIRs A Proposal

Business Register Redesign Technology Strategy Plan

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

MyAPNIC v.1.0 Launching Presentation APNIC-14 Open Policy Meeting

Sanjaya, Project Manager, APNIC Secretariat

APNIC 14 DB SIG Report Xing Li

Policy SIG Open Action Items

A Proposal to Protect Historical Records in APNIC Whois Database

DNS Operations SIG APNIC , Kyoto

Recovery of Unused Address Space prop-017-v001

IPv6 Allocation Status Update

Requirements for running a local WHOIS service

Proposal to Deprecate MAIL-FROM in Maintainer Object

Supporting Historical Resource Transfers

Privacy of Customer Assignment Records

Recovery of Historical Resources Status Update

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

Proposal to Clean Up Whois Database

Status Report on Policy Implementation at the APNIC Secretariat

Status Report on Policy Implementation at the APNIC Secretariat

Database SIG APNIC19 24 February 2005, Kyoto, Japan

IPv6 Policy Update ~ APNIC community ~

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

Presentation transcript:

Whois Database Upgrade Maintainer Administration APNIC Database SIG September 3rd, 2002 sanjaya@apnic.net

Maintainer Administration Whois v2 ‘mnt-by’ attribute optional in ‘inetnum’ object Many ‘inetnum’ objects have no maintainer These objects are unprotected and at risk of unauthorised change Whois v3 ‘mnt-by’ attribute is mandatory Upgrade from whois v2 to v3 creates need for database policy

Upgrade Status – Version 3 On all assignment and allocation ‘inetnum’ objects where no ‘mnt-by’ protection exists ‘maint-null’ has been inserted Offers no protection Temporary solution Affected objects (as of 25 Aug 02) 7,736 out of 135,141 (6%) scope problem When was the last update How many objects

Future Plan Add maintainers automatically to all unmaintained ‘inetnum’ objects Copy maintainer from encompassing object These maintainers may belong to ISPs (APNIC Members) or APNIC If unmaintained, take next level up Implement immediately

Decision Process inetnum object range Maintainer APNIC-HM MAINT-MEMBER APNIC range APNIC-HM last choice APNIC member range MAINT-MEMBER 1st choice customer range MAINT-NULL

Outcome Impact to APNIC Impact to APNIC Member Additional workload for APNIC Legal implications AUNIC and ERX has same implications Impact to APNIC Member APNIC member maintainer will be added to many customer assignment records Member will need to update customer records on behalf of the customer May make ongoing changes, or add new maintainers for customers

Questions?