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

Slides:



Advertisements
Similar presentations
1 Technical Area highlights and priorities APNIC Member Meeting 29 February 2008 APNIC 25, Taipei George Michaelson.
Advertisements

Operational Policies for NIRs in the APNIC Region NIR Meeting APNIC14, Kitakyushu, Japan 4 Sept 2002.
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.
APNIC Member Services George Kuo. MyAPNIC 2 What is MyAPNIC A secure Member services website Internet resources management, for example: –Whois updates.
Handling Internet Network Abuse Reports at APNIC 21 October 2010 LAP-CNSA Workshop, Melbourne George Kuo.
Save Vocea/ Sanjaya - APNIC PacINET November 2002, Fiji APNIC Whois Tutorial.
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,
Reverse DNS.
APNIC Internet Routing Registry An introduction to the IRR TWNIC Meeting, 3 December 2003 Nurani Nimpuno, APNIC.
Reverse DNS. Overview Principles Creating reverse zones Setting up nameservers Reverse delegation procedures.
Anne Lord & Mirjam Kühne. AfNOG Workshop, 10 May The whois Database Introduction and Usage.
Providing A Subset of Whois Data Via DNS Shuang Zhu Xing Li CERNET Center.
NATO Advanced Networking Workshop. Ljubljana, 19 September “How to Run a Local Internet Registry” or all your IPs are belong.
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.
The APNIC Whois Database Introduction and Usage. whois.apnic.net whois.ripe.netwhois.arin.net Server Unix Client ‘X’ Client Command Prompt / Web Interface.
1 APNIC reverse DNS management roadmap DNS operations SIG, APNIC 21 2 March 2006.
Database Update Paul Palse Database Manager, RIPE NCC.
Part 2.
Welcome! APNIC Members Training Course Internet Resource Management Essentials 31 August 2004, Nadi, Fiji APNIC -18 Open Policy Meeting.
IP address Allocation & and Requests AfNOG Workshop, May 2004 Dakar, Senegal.
NATO Advanced Networking Workshop. Ljubljana, 19 September RIPE whois Database RIPE Network Coordination Centre.
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.
2016 Services Roadmap APNIC Services George Kuo 9 September 2015 Jakarta.
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.
Network Abuse Update Frank Salanitri Project & Systems Services Manager, APNIC.
REVERSE DNS Why and how AFRINIC-II Maputo,Mozambique 26 April 2005 Alain AINA.
Sweeping Lame DNS Delegations A Proposal DNS OPS SIG APNIC 15, Taipei, Taiwan 26 February 2003.
1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET
Andrei Robachevsky. APNIC/APRICOT2001, February 2001, Kuala Lumpur, Malaysia. 1 New Version of the RIPE Database Andrei Robachevsky.
1 Discussion of the new DNS generation system DNS Operations SIG APNIC 18 2nd September 2004, Fiji.
1 IPv6 Allocation Policy and Procedure Global IPv6 Summit in China 2007 April 13, 2007 Gerard Ross and Guangliang Pan.
MyAPNIC Survey 2015 What have we learned? APNIC Services Vivek Nigam 9 September 2015 Jakarta.
APNIC Security Update APSIRCC 2002 Tokyo, 25 March 2002.
Database Tutorial 3 September, Kitakyushu, Japan 14 th APNIC Open Policy meeting APNIC.
Horses for courses- like IPv6 profiles for german administration Constanze Bürger Bundesministerium des Innern.
Andrei Robachevsky. 12th APNIC Open Plicy Meeting, August 2001, Taipei, Taiwan. 1 New Version of the RIPE Database Andrei Robachevsky.
Local Internet Registries. RIPE 47 - IP Request Tutorial. 1 Welcome to the RIPE NCC IP Request Tutorial January 27, 2003 RIPE Network.
APNIC Internet Routing Registry Tutorial Seoul 19 August 2003.
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.
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 APNIC Reverse DNS October 26th, Brisbane Bruce.
17 th APNIC Open Policy Meeting APNIC IPv6 Address Guidelines Akira Nakagawa )/ POWEREDCOM Billy MH Cheon / KRNIC Toshiyuki.
Prop-007-v001 Privacy of customer assignment records Project Update DB SIG APNIC February 2005 Kyoto, Japan Sanjaya, Project Manager, APNIC Secretariat.
Services Area Report Sanjaya Services Area Director.
1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET
RIPE 47: IPv6 WG 27 January 2004 Hotel Krasnapolsky, Amsterdam Jeroen Massar IPv6 Golden Networks.
APNIC Update Elly Tawhai Senior Internet Resource Analyst/Liaison Officer, Pacific, APNIC AusNOG
I-NAMES Corporation Database Privacy Policy Database Policy SIG, APNIC Meeting at Taipei, Taiwan Lee, Seung-Min.
1 Welcome to the Policy SIG 6 Sep 2006 APNIC 22, Kaohsiung, Taiwan.
Research & Liaison Officer (Pacific)
Lame DNS Server Sweeping
IPv6 Allocation Status Report
/48 assignment status report
RIPE Whois Database Software Recent Changes
Sanjaya, Project Manager, APNIC Secretariat
A Proposal to Protect Historical Records in APNIC Whois Database
Proposal to Deprecate MAIL-FROM in Maintainer Object
Privacy of Customer Assignment Records
Proposal to Clean Up Whois Database
Status Report on Policy Implementation at the APNIC Secretariat
Status Report on Policy Implementation at the APNIC Secretariat
Whois Database Upgrade
IPv6 Policy Update ~ APNIC community ~
Presentation transcript:

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

Procedural Problem Whois database authorisation is hierarchical –APNIC maintainer is the mnt-lower for all APNIC /8 domains –All attempts by members to create /24 and /16 domains fail for non MyAPNIC users

Example Member XYZ has been allocated – (/20): inetnum: – netname: XYZ-NET descr: XYZ Broadband Networks descr: Suburbia country: AP admin-c: EG999-AP tech-c: EG999-AP mnt-by: APNIC-HM mnt-lower: MAINT-AP-EXAMPLE changed: status: ALLOCATED PORTABLE source: APNIC

Example continued Member XYZ now tries to create a /24 reverse delegation, in-addr.arpa: domain: in-addr.arpa descr: Reverse DNS Zone for /24 country: AP admin-c: EG999-AP tech-c: EG999-AP zone-c: EG999-AP nserver: ns1.foo.bar nserver: ns2.foo.bar mnt-by: MAINT-AP-EXAMPLE source: APNIC

Example continued They submit the domain object to but it fails  Why? –Authorisation is hierarchical, the parent object 202.in-addr.arpa contains: mnt-lower: MAINT-AP-DNS –Only new domain objects with mnt-by and password of MAINT-AP-DNS will succeed

Authorisation model problems Manual creation Inconvenient due to time delay Not providing best possible service

Procedural Solution - Allocation Compare mnt-by of domain template with mnt-lower of related inetnum object Maintainers match and correct password provided If conditions met then domain object is created

Example of Allocation Procedural Solution Inetnum object inetnum: netname: XYZ-NET descr: XYZ Broadband Networks descr: Suburbia country: AP admin-c: EG999-AP tech-c: EG999-AP mnt-by: APNIC-HM mnt-lower: MAINT-AP- EXAMPLE changed: status: ALLOCATED PORTABLE source: APNIC Domain template domain: in- addr.arpa netname: Reverse DNS for /24 country: AP admin-c: EG999-AP tech-c: EG999-AP nserver: ns1.foo.bar nserver: ns2.foo.bar mnt-by: MAINT-AP- EXAMPLE changed: source: APNIC

Procedural Solution - Assignment Compare mnt-by of domain template with mnt-routes of related inetnum object Encouraged use of mnt-routes attribute Maintainers match and correct password provided If conditions met then domain object is created

Example of Assigment Procedural Solution Inetnum object inetnum: netname: XYZ-NET descr: XYZ Broadband Networks descr: Suburbia country: AP admin-c: EG999-AP tech-c: EG999-AP mnt-by: APNIC-HM mnt-routes: MAINT-AP- EXAMPLE changed: status: ASSIGNED PORTABLE source: APNIC Domain template domain: in- addr.arpa netname: Reverse DNS for /24 country: AP admin-c: EG999-AP tech-c: EG999-AP nserver: ns1.foo.bar nserver: ns2.foo.bar mnt-by: MAINT-AP- EXAMPLE changed: source: APNIC

Exceptions Old allocations with no mnt-lower attribute. Assignments with no mnt-routes attribute. –Forward any domain templates which don’t meet the proposed solution to for manual intervention.

Statistics 622 new domain objects submitted for manual creation between January 1 and February (89%) would have succeeded through new algorithm

Implementation Schedule End of 2004

Questions? Thanks for your time!