ARIN Policies and Guidelines An Introduction Presented by Richard Jimmerson Director of Operations NANOG 22Scottsdale, AZ
NANOG 22Scottsdale, AZ Overview About ARIN Registry Activities Open Policy Process Current Policies Using ARIN Services Top 10 Questions About ARIN
NANOG 22Scottsdale, AZ RIR Basis Proposed by IETF in early 1990’s –RFC 1174 (1990) “IAB Recommended Policy on Distributing Internet Identifier Assignment…” –RFC1366 (1992) “Guidelines for Management of IP Address Space” Released with RFC1367 (CIDR) Documents provided rationale for RIRs –Criteria for establishment –Operating guidelines
NANOG 22Scottsdale, AZ ARIN American Registry for Internet Numbers –Founded in 1993, as division of “InterNIC” –Independent association since 1997 –1,317 members Service Region: North & South America, the Caribbean, Africa south of equator –70 countries Located in Chantilly, Virginia, US
NANOG 22Scottsdale, AZ Other RIRs APNIC –Service Region: Asia, Oceania and Western Pacific –Located in Brisbane, Australia RIPE NCC –Service Region: Europe, Middle East, Central Asia, Africa north of equator –Located in Amsterdam, the Netherlands Emerging RIRs –LACNIC Proposed Region: Latin America www.lacnic.org –AFRINIC Proposed Region: Continental Africa www.afrinic.org
NANOG 22Scottsdale, AZ RIR Model - Structure Bottom-up, industry, self-regulatory structure Open and transparent Neutral and impartial Not for profit organizations Membership open to all interested parties Membership elects Board of Trustees and Advisory Council Membership approves activities & budget RIRs do NOT register domain names
NANOG 22Scottsdale, AZ Formation of ICANN US Government decision to end USG management of the global Internet Internet Corporation for Assigned Names and Numbers (ICANN) formed as the industry self-regulatory body
NANOG 22Scottsdale, AZ ICANN ASO Formed by RIRs based on existing and proven regional policy structures Responsible for global policy coordination within ICANN framework Advisory Council elected by RIR communities
NANOG 22Scottsdale, AZ Role of the AC...is to be a catalyst in the policy process, –not to develop policy, –but to oversee and coordinate the policy development process facilitated by the RIRs Make recommendations to the ICANN board on addressing issues Elect three members of the ICANN Board of Directors
NANOG 22Scottsdale, AZ RIR Activities Address space management Registration Policy development Outreach
NANOG 22Scottsdale, AZ Address Management Challenges Address space depletion –IPv4 address space is finite –Historically, many wasteful allocations Routing chaos –Legacy routing structure, router overload –CIDR & aggregation are now vital Inequitable management –Unstructured and wasteful address space distribution
NANOG 22Scottsdale, AZ Address Management Objectives Conservation –efficient use of resources –allocation based on demonstrated need Aggregation –Limiting growth of routing table –provider-based addressing policies Registration –Ensuring uniqueness –Troubleshooting Fairness and Consistency –In the interests of regional and global communities
NANOG 22Scottsdale, AZ Registration IPv4 and IPv6 Numbers Registration AS Number Registration Registration Call Center Reverse Delegation WHOIS Directory Service Routing Registry Service
NANOG 22Scottsdale, AZ IPv4 Allocation Rate in 2000 RIPE NCC ARIN APNIC (1.5 /8) (1.28 /8) (2.0 /8)
NANOG 22Scottsdale, AZ IPv4 Unallocated Currently 38% of all IPv4 address space has not been allocated (Reserved by the IANA)
NANOG 22Scottsdale, AZ IPv6 Allocations Allocations since 1999 A total of 75 IPv6 address blocks (/35s) allocated collectively –APNIC: 26 –ARIN: 15 –RIPE NCC: 34
NANOG 22Scottsdale, AZ Outreach Training and Education –Registration help desk –Standardized registration training programs –Attendance at local (state) ISP association meetings Information dissemination –News agencies –Industry specific meetings (like the GSMNA) –Government Advisory Committee to the ICANN
NANOG 22Scottsdale, AZ Policy Development Developed in open policy forums –within industry self-regulatory framework –with consensus of community –Participation open to everyone Responsive policy development –fair to all –changing requirements of industry –new technology (G3 phones, GPRS, cable) –evolution of process Technical challenges –high level of planning and expertise required –meeting demands of a changing environment
NANOG 22Scottsdale, AZ New Policy Life-Cycle Policy Proposed Recommendation by Community Reviewed by Advisory Council Recommendation Forwarded to BOT BOT Approves New Policy ARIN Staff Act on New Policy Community Discussion
ARIN posts proposal on mailing list at least 30 days before meetings Proposal declared emergency by Board? 1. Statement of policy 2. Arguments and discussion summary 3. Proposed timetable Submit policy proposal at least 6 weeks before meetings no yes Discussions are held at Public Policy Meetings no No action taken no Further action considered? yes ARIN posts to mailing lists for no less than 10 working days for discussion Return proposal to AC for revision Enact policy and post announcement Final proposal with comments presented to Board Board reviews proposal no yes Ratified? AC evaluates then posts final proposal to mailing lists for no less than 10 working days Community / Member consensus reached?
NANOG 22Scottsdale, AZ Public Mailing Lists ARIN Public Mailing Lists –ARIN Public Policy Mailing List –IP Allocation Policy Mailing List –Virtual Webhosting Committee –IPv6 Working Group –Database Implementation Working Group –Community Learning and Education Working Group (CLEW) –Routing Table Measurement and Analysis Visit http://www.arin.net/members/mailing.htm to participate
NANOG 22Scottsdale, AZ Mailing List Discussions IPv6 Working Group (email@example.com) –IPv6 allocations for exchange points –IPv6 reassignment policy (/48) Public Policy (firstname.lastname@example.org) –Single organizations with multi-homed, discrete networks Virtual Web Hosting Working Group (email@example.com) –Name-based web hosting policy Database Working Group (firstname.lastname@example.org) –Reassignment options –Database redesign
NANOG 22Scottsdale, AZ ARIN’s Minimum Assignment Size is a /20 Demonstrate Efficient Utilization of a /20 from Upstream –Report reassignment information via SWIP or RWHOIS –Share utilization information for Dial-up, Virtual Web Hosting, and like services Multi-homed Policy –Demonstrate Efficient Utilization of a /21 and Renumber Use ISP Network Template to Request IP Addresses Request Criteria for IPv4 Address Space (ISPs)
NANOG 22Scottsdale, AZ Demonstrate Prior Allocations from ARIN 80% Efficiently Utilized –SWIP or RWHOIS server for reassignment information –Internal utilization detail Adhere to any Agreed to Renumbering Indicate 3-month Need for IP Address Space Use ISP Network Template to Request Additional IP Addresses Request Criteria for Additional IPv4 Addresses (ISPs)
NANOG 22Scottsdale, AZ The following information must be provided with request: –Immediate and 1 Year addressing plans –Description of network topology –Description of network routing plans Must demonstrate immediate need for 25% and a 1 year need for 50% of the netblock being requested. Request Criteria for IPv4 Addresses End-Users
NANOG 22Scottsdale, AZ IPv6 Policy Phases Bootstrap Phase –Transitional and temporary –Concludes After first 100 sub-TLA IDs (/29s) have been allocated worldwide, or After ARIN has allocated 60 sub-TLA IDs General Phase
NANOG 22Scottsdale, AZ Bootstrap Phase Criteria 1.BGP peering relationships with at least three other public ASes in IPv4 default- free zone 2.Must demonstrate production IPv6 within 12 months and either 3.Must be IPv4 provider to 40 sites that merit /48 IPv6 allocations or 4.3 months of 6bone pTLA experience in overall 6-month 6bone
NANOG 22Scottsdale, AZ General Phase Criteria 1.BGP peering relationships with 3 other IPv6 networks with sub-TLA IDs and either 2.Requesting organization must have reassigned addresses from upstream providers to 40 SLA customer sites or 3.Requesting organization must demonstrate a clear intent to provide IPv6 within 12 months
NANOG 22Scottsdale, AZ Unique Routing Policy –Must demonstrate that routing policies are different from border gateway peers Multi-homed Site –Must be multi-homed or will immediately become multi-homed, and must describe: Exterior gateway protocol to be used IP network addresses that will make up the AS Technical POC information for each upstream provider/peer, including… –Full name –Email address Request Criteria for AS Numbers
NANOG 22Scottsdale, AZ Top 10 Questions Can I have a copy of ARIN’s database? How do I change the organization name on my network (or AS) registration?
NANOG 22Scottsdale, AZ Top 10 Questions How do I add in-addr servers to my network? The criteria do not apply to me. Can the ARIN staff change the policy to accommodate my need?
NANOG 22Scottsdale, AZ Top 10 Questions Can ARIN stop somebody from sending spam? … announcing a bogus route? … pinging my network? What can ARIN do if I have routing difficulties with the CIDR prefix ARIN allocates/assigns my network?
NANOG 22Scottsdale, AZ Top 10 Questions What is the difference between an assignment and allocation? How long does it take for ARIN to look at my request?
NANOG 22Scottsdale, AZ Top 10 Questions Does ARIN prefer SWIP or RWHOIS as a reassignment option? Does ARIN accept credit cards for registration fees?
NANOG 22Scottsdale, AZ Common Misconceptions ARIN staff make up the “rules” as they go along. ARIN is difficult to deal with. ARIN is the “Internet police.”
NANOG 22Scottsdale, AZ Contact Information Help Desk –(703)227-0660 –Monday – Friday 7 AM – 7 PM US Eastern time Hostmaster Email –Hostmaster@arin.net –Ticketing system for request/inquiry tracking www.arin.net