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 & Internet Address Policy in the Asia Pacific NZ Internet Industry Forum Auckland,

Slides:



Advertisements
Similar presentations
ARIN IP Address Stewardship 3 February About ARIN Regional Internet Registry (RIR) – Established December 1997 by Internet community 100% community.
Advertisements

1 Overview of policy proposals Policy SIG Wednesday 26 August 2009 Beijing, China.
IPv6: The Future of the Internet? July 27th, 1999 Auug.
IPv6 Addressing – Status and Policy Report Paul Wilson Director General, APNIC.
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 Overview AFRINIC Meeting Accra, Ghana, May 13th 2001 Anne Lord Asia Pacific.
IPv6 Address Allocation Policies & Procedures Champika Wijayatunga, APNIC 1 st ASEAN IPv6 Summit Oct 20-22, 2003 – Kuala Lumpur, Malaysia.
1. 2 Information Document 22-E ITU-T Study Group 2 May 2003 Question:1/2 Source:TSB Title:IPv6 Address Management – Past, Present and Future (by Anne.
IP Address Management The RIR System & IP policy
1 The Geography and Governance of Internet Addresses Paul Wilson APNIC.
ARIN Policies and Guidelines An Introduction Presented by Richard Jimmerson Director of Operations NANOG 22Scottsdale, AZ.
AussieISP Fall ‘99 Sydney, 9 April 1999 Overview and Status Report.
Mirjam Kühne 1 ETO, Oct The Internet Registry System presented by Mirjam Kühne.
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 Introduction and Overview ITU/PITA Joint Workshop Brisbane, October 2001.
Internet Addressing and the RIR system 11 February 2004 Phnom Penh, Cambodia Paul Wilson, APNIC.
1 APNIC support for Internet development APT/PITA Regional Meeting on ICT for the Pacific August 2004, Nadi, Fiji Paul Wilson
APNIC Update Paul Wilson Director General. APNIC RIR for Asia Pacific –IP address allocation and management –Open policy development Support for Internet.
APNIC Update RIPE 59 October Overview APNIC Services Update APNIC 28 policy outcomes APNIC Members and Stakeholder Survey Next APNIC Meetings.
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 Internet Registry allocation and assignment Policies.
APNIC Policy Update 1 st TWNIC IP Open Policy Meeting 3 December, 2003 Taipei, Taiwan.
ARIN Update June 2000 NANOG 19Albuquerque NANOG 19Albuquerque Overview Organization & Staff Activities Regional News Membership Statistics Regional Policy.
APNIC Policy Update 1 st TWNIC Open Policy Meeting 3 December, 2003 Taipei, Taiwan.
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 Update RIPE 40 Prague, 1-5 October, 2001.
APNIC Update AfriNIC 12 May 2010 Sanjaya Services Director, APNIC.
Internet Addressing and the RIR system (part 2) 12 February 2004 Phnom Penh, Cambodia Paul Wilson, APNIC.
APNIC Depletion of the IPv4 free address pool – IPv6 deployment The day after!! 8 August 2008 Queenstown, New Zealand In conjunction with APAN Cecil Goldstein,
1 APNIC allocation and policy update JPNIC OPM July 17, Tokyo, Japan Guangliang Pan.
RIR Status Report RIR Status Report IEPG August 2001.
Regional Internet Registries Statistics & Activities IETF 55 Atlanta Prepared By APNIC, ARIN, LACNIC, RIPE NCC.
A proposal to lower the IPv4 minimum allocation size and initial criteria in the AP region prop-014-v001 Policy SIG APNIC17/APRICOT 2004 Feb
APNIC Annual Members’ Meeting Singapore, 6 March 1999 APNIC - Annual Report.
IP Policy in APNIC and What about TWNIC ? Kuo-Wei Wu.
Mirjam Kühne 1 EC, Oct Policy Development in RIPE & the RIPE NCC Mirjam Kühne RIPE NCC.
APNIC Update ARIN IX Las Vegas, Nevada 7-10 April, 2002.
17 March 2002IEPG - Minneapolis RIR Update A Joint Presentation Prepared By APNIC, ARIN, RIPE NCC.
1 IPv4 Addressing in China CNNOG April 2006, Beijing Guangliang Pan.
Anne Lord & Mirjam Kühne. AfNOG Workshop, 10 May IP Address Management AfNOG Workshop, 11 May 2001 Accra, Ghana presented by:
July 2002IEPG, Yokohama, Japan RIR Co-ordination and Joint Statistics IEPG, Yokohama, Japan Prepared By APNIC, ARIN, RIPE NCC.
1 Challenges in IPv6 Address Management Paul Wilson Director General APNIC.
1 IPv6 Allocation Policy and Procedure Global IPv6 Summit in China 2007 April 13, 2007 Gerard Ross and Guangliang Pan.
1 IP Addresses, Addressing and Address Management Paul Wilson APNIC.
APNIC Report RIPE 43 Rhodes, Greece 9-13 September 2002.
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 Status Report ARIN VI Public Policy Meeting 2-4 October 2000.
APNIC Internet Resource Management and Internet Infrastructure Support PITA Members Meeting 10 January 2004 Honolulu, Hawaii Save Vocea, APNIC.
APNIC Security Update APSIRCC 2002 Tokyo, 25 March 2002.
Management of Internet Resources ITU Workshop on Developing a Policy and Regulatory Framework for Developing Economies of the Pacific 1 December 2003 Suva,
IP Addressing and ICT Development in the Pacific Islands Anne Lord and Save Vocea, APNIC ICT Workshop, Fiji, November, 2002.
Securing Future Growth: Getting Ready for IPv6 NOW! ccTLD Workshop, 8 th April 2011 Noumea, New Caledonia Miwa Fujii, Senior IPv6 Program Specialist, APNIC.
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 History and Overview AfriNIC Meeting Cape Town, May 2000.
IP addresses and address management Miwa Fujii APNIC, Training Officer.
30 April 2003 ITU SG2, Geneva, Switzerland Axel Pawlik, RIPE NCC Information Document 21-E ITU-T Study Group 2 May 2003 Question:1/2 Source:TSB Title:The.
Internet Protocol Addresses What are they like and how are the managed? Paul Wilson APNIC.
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 Emerging Registry Criteria ASO General Assembly Budapest, 19 May 2000.
IEPG November 1999 APNIC Status Report. Membership Resource Status Recent Developments Future Plans Questions?
Current Policy Topics Emilio Madaio RIPE NCC RIPE November 2010, Rome.
AFRINIC Update Madhvi Gokool Registration Service Manager RIPE66 meeting, Dublin May 2013.
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 Update, Structure and Policies Yokohama, December 2001.
1 The Internet Registry System Mirjam Kühne RIPE NCC EC-POP Brussels 5 July 1999.
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 IP Addresses: A critical resource for Asia-Pacific Internet development China Inet.
1 IPv6 Allocation and Policy Update Global IPv6 Summit in China 2007 April 12, 2007 Guangliang Pan.
IP Address Management The RIR System Nurani Nimpuno APNIC.
Axel Pawlik. Regional Symposium on E-gov’t and IP, 24 November 2004, Dubai. Busting Internet Myths An Introduction to the RIPE NCC.
Regional Internet Registries An Overview
IEPG Minneapolis, March 1999
RIR Co-ordination and Joint Statistics
RIPE 41 Amsterdam, January, 2002
KRNIC Member Workshop November 2001 Seoul, Korea
IPv6 Address Allocation APNIC
Status of IPv6 Addresses and Address Management
A Proposal for IPv4 Essential Infrastructure
IPv6 distribution and policy update
Presentation transcript:

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 & Internet Address Policy in the Asia Pacific NZ Internet Industry Forum Auckland, 29 November 2001 Anne Lord, APNIC

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 Overview  Introduction to APNIC  Policy Development  Address Management  APNIC Update  Questions

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 What is APNIC?  Regional Internet Registry (RIR) for the Asia Pacific Region  Regional authority for Internet Resource distribution  IP addresses (IPv4 and IPv6), AS numbers, in-addr.arpa delegation  Established 1993  Operating within ICANN (IANA) structure  Pilot project of APNG in Tokyo, Japan  Relocated to Brisbane, Australia in 1998

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 What is APNIC?  Industry self-regulatory body  Consensus-based, open and transparent  Non-profit, neutral and independent  Membership-based structure  Open to any interested party  Provides formal structure for cost recovery, election of representatives etc  Is NOT  Standards body like IETF, or a network operator  Domain name registry or registrar

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 Region

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 Delegated Hierarchy

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 What does APNIC do? Critical Internet administrative services  Internet resource management  IP address allocation and assignment  AS number assignments  Resource registration  Authoritative registration server: whois  DNS management  Delegate reverse DNS zones/domains  Authoritative DNS server: in-addr.arpa

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 What else does APNIC do?  Policy development  Open Policy Meetings: SIGs, WGs, BOFs  Mailing list discussions  Training and Seminars  2 training courses per month in 2002  Seminars with AP Outreach  Publication & Information  Newsletter, web and ftp site  Joint RIR statistics

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 What else does APNIC do?  Co-ordination & Representation  Extensive liaison with development, industry communities  IETF, IEPG, IPv6 Directorate, GSM-A, IPv6 Forum, ISOC  Asia Pacific peak bodies in Internet industry, technology, policy and law  APNG, APIA, APAN, APTLD, APRICOT  Other RIRs and ICANN  ARIN, RIPE-NCC, LACNIC, AFRINIC  ICANN, IANA and ASO

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 Policy Development Processes

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 Address Management - Problems By the end of 1992  Address space depletion  IPv4 address space is finite  Historically, many wasteful allocations  Routing chaos  Legacy routing structure, router overload  Increasing instability of routing structure  Inequitable management  Early adopters received more address space than many countries have today!

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 Goals of the Registry System  Conservation  ensuring efficient use of resources, and allocation policies based on demonstrated need  Aggregation  limiting growth of routable prefixes, through provider- based addressing policies  Registration  ensuring that resource use is registered and that resources are allocated or assigned uniquely  Fairness and Consistency  In the interests of regional and global communities

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 Open Policy Development  Policy development processes (regional & global)  Open - anyone can participate  Within self-regulatory environment  Must be adaptive and flexible to meet changing requirements of industry  New challenges posed to address management eg. G3 phones, GPRS, cable  Global policy  ASO responsible for coordination within ICANN framework  ASO formed by RIRs (ASO MoU) with reliance on existing and proven regional policy structures

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 Open Policy Development Consensus of community Discussions in RIR community Policy meetings & SIGs, mailing lists etc mailing lists etc Liaison with other RIRs By RIRs and community Policy is implemented RegionalPolicyVariations Global Consensus GlobalPolicies/ ASO coordination

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’s Open Policy Forum  APNIC Open Policy Meeting  2 meetings a year, open to all  Many ‘special interest groups’  Open public forum to discuss topics of interest to APNIC and the Internet community in the region  Document Revision  Documents posted for public comment  Via web sites and mailing lists  Translated documents available  Training & Education  Delivered across the region  Feedback into policy discussions

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 Address Management Policies

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 Address Management Policies  Allocations as ‘Provider Aggregatable’ address space  Provider responsible for aggregation  Customer assignments must be non-portable  Allocations based on demonstrated need  Detailed documentation required  All address space held to be declared  Address space to be obtained from one source  Routing considerations may apply  Stockpiling not permitted

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 Address Management Policies  “Slow start”  All organisations receive minimum allocation initially, regardless of initial requirement  Minimum allocation is currently a /20  Request more address space when consumed  Assignment of address space  “Assignment Window” limits the size of “autonomous” assignments  “Second Opinion” must be requested when larger assignment is required

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 Address Management Policies  Criteria for initial minimum address allocation  Must have a /22 or demonstrate immediate need for a /22 and a plan for a /21 in one year  Including customer projections & infrastructure equipment  Applicants may be required to show purchase receipts  And agree to renumber within one year  Demonstrate efficient usage of IP addresses  Implementing criteria follows global trend

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 Address Management Policies NEW policies  Small multihoming portable assignment  Multihomed or have a plan to within 1 month  Agree to renumber  Demonstrate need to use 25% of requested space immediately and 50% within 1 year (rfc2050)  IX address space requests  /64 for IPv6, /24 for IPv4  Must have more than 3 peers  Demonstrate ‘open’ peering policy  Reserved block for IXes  /16

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 Address Management Policies  IP addresses are not considered property  “Licensed” allocations  Internet resources are public resources  ‘Ownership’ is contrary to management goals  Need to avoid the mistakes of the past  Transfer of license requires approval from the registry  ‘Automatic’ if policies are followed  Address registration – whois database  Not considered valid unless registered  Reverse DNS – in-addr  Not mandatory but strongly encouraged  APNIC maintains authoritative servers for address space

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 Current Policy Discussions  IPv6  Rough consensus on need for different initial allocation size - /32 suggested  Flexible utilisation measure needed  Global mailing list to further discuss   RFC2050  Global effort to evaluate rfc2050 to see if relevant to today’s Internet  Mailing list   To subscribe  To subscribe

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 New APNIC Membership Structure  Implementation:  1 December 2001 for new member  1 March 2002 for existing members PrefixCategoryNew FeeVotes > /10X-large$40,00064 <= /10V-large$20,00032 <= /13Large$10,00016 <= /16Medium$5,0008 <= /19Small$2,5004 <= /22V-small$1,2502 n/a Assoc$6251

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 Update Statistics and Security

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 IANA Delegations (Apr 2001) Unallocated Other Orgs. (pre-RIR) ARIN APNIC RIPE NCC

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 Where are the IPv4 Allocations?

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 IPv4 Addresses Allocated in AP

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 IPv6 Allocations in the AP Region

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 Security of APNIC Services  No change after Sept 11  Security is always under constant review  Increased public awareness  Security measures consistent with “Medium” security site  Backups with secure off site storage  Secured entry and alarm systems  Backup power – UPS with generator provisions  Redundant servers hardware, RAID etc  Distributed architecture (DNS, and more planned…)  Security provisions implemented with diligence

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 Security of APNIC Services  ‘whois’  Brief outages not regarded as critical  But ‘highly available’  External machines separate from internal  DNS (in-addr.arpa)  Zone authority for address blocks delegated to APNIC  Essential service – requires 24x7 availability  Secondaries at Japan POP and other sites (eg RIRs)  RIR co-operation  Engineers liaise frequently to address issues of redundancy and backup  Mirror servers deployment planned at ARIN & RIPE NCC

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 Future Plans  Distributed POP architecture  Providing all essential services  ‘whois’, DNS, web,  With dynamic load distribution  Deployment  Existing WIDE/NSPIXP site to be upgraded  First new site early probably HKIX  More planned in region  DNSsec  Testing currently underway

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 Future Plans  Certification Authority  Response to member concerns on security  , website auth* and privacy  Industry-standard X.509 certificates  Trial certificates being issued now (still?)  “MyAPNIC” website  Access to members’ private information  Use of certificates for secured access  Prototype/demonstration development…

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 Future Plans

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 Questions?