Problem of AS number database registration Toshio TACHIBANA Ani&Company Inc. Presenter: Kuniaki KONDO/INTEC NetCore Inc.

Slides:

Advertisements

Similar presentations

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 Network Abuse: The APNIC perspective Network Abuse BOF APNIC 12 th Open Policy Meeting.

Advertisements

20th APNIC Open Policy Meeting SIG: DB Thursday 8 September 2005 Hanoi, Vietnam Chair: Xing Li.

1 MyAPNIC Project update Database SIG APNIC 23, Bali 28 February 2007.

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

RTÉ eCommissioning A Guide to the Supplier Registration Process.

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

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 Address Policy SIG October 26th, Brisbane.

IPv6 deployment metrics using.JP domain APNIC February 2004 Kenichi Kanayama Intec NetCore, Inc.

NetScanTools ® LE Law Enforcement Version of NetScanTools ® from Northwest Performance Software, Inc. netscantools.com.

Handling Internet Network Abuse Reports at APNIC 21 October 2010 LAP-CNSA Workshop, Melbourne George Kuo.

How do Networks work – Really The purposes of set of slides is to show networks really work. Most people (including technical people) don’t know Many people.

APNIC Internet Routing Registry An introduction to the IRR TWNIC Meeting, 3 December 2003 Nurani Nimpuno, APNIC.

Guide to admin procedures on the internet infrastructure William Tevie.

Copyright (c) 2003 Intec NetCore, Inc. All rights Reserved. 1 Proposal: NIR Operated IRR Kuniaki KONDO Intec NetCore, Inc. JPNIC IRR Planning Team Chair.

Thinking about GIS applications and your projects.

Providing A Subset of Whois Data Via DNS Shuang Zhu Xing Li CERNET Center.

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.

Scaling IXPs Scalable Infrastructure Workshop. Objectives  To explain scaling options within the IXP  To introduce the Internet Routing Registry at.

Policy Proposal 109 Standardize IP Reassignment Registration Requirements ARIN XXV 18 April, 2010 – Toronto, Ontario Chris Grundemann.

Prepared by The Regional Internet Registries [APNIC, ARIN, LACNIC and RIPE NCC]

What is WHOIS?. 2  Internet Protocol you can use to search registry and registrar databases and discover who registered a domain name or IP address 

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

Building Your Linkedin Network to 500 connections.

Java Naming and Directory Interfaces. A naming service is an entity that performs the following tasks:  It associates names with objects. Similar to.

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

APNIC Internet Routing Registry An introduction to the IRR TWNIC Meeting, 3 December 2003 Nurani Nimpuno, APNIC.

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

Global Name Registry Proposal to Modify Appendix O: WHOIS Data Access.

Phishing Lab. Lab 9: Phishing ● Step 1: Acquire Some Data ● Open the Phishing_Evidence document. This is the original in its initial format as.

CORDIS Partners Service cordis.europa.eu/partners Magdolna Zsivnovszki.

What is WHOIS?. 2  Internet Protocol you can use to search registry and registrar databases and discover who registered a domain name or IP address 

1 To Insert AS Origin field into APNIC IP address database Xing Li Shuang Zhu CERNET

Izumi Okutani JPNIC IP Department NIR Meeting Feb 2004 JPNIC Open Policy Meeting Update.

TCOM Information Assurance Management Casing the Establishment.

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

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

CA’ FOSCARI UNIVERSITY OF VENICE INTERNATIONAL CAREER SERVICES.

Whois & Data Accuracy Across the RIRs. Terms ISP – An Internet Service Provider is allocated address space by an RIR for the purpose of providing connectivity.

I-NAMES Corporation Database Privacy Policy Database Policy SIG, APNIC Meeting at Taipei, Taiwan Lee, Seung-Min.

Mail Merge in Ms-Word 2010 Mail merge is a software function describing the production of multiple (and potentially large numbers of) documents from a.

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.

Keeping local stuff local

Implementation of ARIN's Lame DNS Delegation Policy

IRR BoF 25+ attendees 2 presentations Discussion item

Whois Data Privacy Issues in Japan

D-link Router Support Website: support/index.htmlhttp://callpcexperts.com/d-link-router- support/index.html Contact.

D-Link router tech support phone number provides the technical support for client issue concerning to d-link as there’s a team of specialist that are.

AFRINIC Services Update

The practice report format

Measuring routing (in)security

/48 assignment status report

APNIC 29 Policy SIG report

NIR SIG, 18th APNIC Meeting

Sanjaya, Project Manager, APNIC Secretariat

Manual Water Ski Directory

APNIC 14 DB SIG Report Xing Li

A week in the life of (IRT address)

A Proposal to Protect Historical Records in APNIC Whois Database

IPv6 Allocation Status Update

Private Information Handling at APNIC Database

IPv6 Allocation Status Report

Proposal to Deprecate MAIL-FROM in Maintainer Object

Kuniaki Kondo IRR Workshop Chair, JPNIC IIJ

Report of Open NIR Meeting

Proposal to Clean Up Whois Database

IPv6 Policy Update ~ APNIC community ~

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

By Keessun Fokeerah Member Services(MS) Team

Connect WG, RIPE78 Bijal Sanghani & Jesse Sowell

Presentation transcript:

Problem of AS number database registration Toshio TACHIBANA Ani&Company Inc. Presenter: Kuniaki KONDO/INTEC NetCore Inc.

Reasons for disclosing registry information by Whois database. Preceding network users are… They accept responsibility. And they use their experiences. Whois database provides information to help them with troubleshooting.

Enough information for troubleshooting Requirement Anybody can search for contact information. They contact the target organization based on that information. Examples Organization name Person name in the organization address Telephone number…etc. It is same to disclose AS number information.

AS Object Same as RPLS Same as IRR Objects aut-num: AS18146 as-name: InetCore descr: Intec Netcore, Inc. import: from AS accept ANY import: from AS accept ANY import: from AS accept ANY export: to AS17685 announce AS18146 export: to AS7682 announce AS18146 export: to AS17686 announce AS18146 country: JP admin-c: IN011JP tech-c: RH005JP This object includes too much information which is “import”/”export”, not only “Contact Information”.

Is “import”/”export” registry information? “import”/”export” fields describe “connectivity information”. NOT “registry information” Most company never disclose “connectivity information”. Because, it includes… Business plan Private peering… This information should NOT be disclosed by whois database.

“import”/”export” are needed? What is happen, if “import”/”export” field disappear. Whois database aut-num object format is same as IRR database. Some operators might use whois database instead of IRR database for making route filters. –These users might have some trouble. “import”/”export” are important information for network operation. HOWEVER, those information should be managed by IRR database, NOT a whois database.

Proposal(1) The “import”/”export” fields MUST NOT be disclosed by whois database. Whois database means registry information, not “IRR information”. Route administration information should be disclosed by IRR databse.

Proposal(2) APNIC is planning to merge whois and IRR database system to 1 system using RIPEv3. Merging database is a good idea. One aut-num object in RIPEv3 has two aspects of registry database and IRR which are separate things. It is confusing. We propose that APNIC should define a new object for managing AS number assignment.

Thank you Toshio Kuniaki