ARIN Policies and Guidelines An Introduction Presented by Richard Jimmerson Director of Operations

2. ARIN Policies and Guidelines An Introduction Presented by Richard Jimmerson Director of Operations NANOG 22 Scottsdale, AZ

3. Overview • About ARIN • Registry Activities • Open Policy Process • Current Policies • Using ARIN Services • Top 10 Questions About ARIN

4. 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

5. 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

6. 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 Other RIRs

7. ARIN Membership 95% 1% 3% 1%

8. 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

9. 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

10. AFRINIC? LACNIC?

11. 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

12. 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

13. RIR Activities • Address space management • Registration • Policy development • Outreach

14. Address ManagementChallenges • 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

15. Address ManagementObjectives • 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

16. Registration • IPv4 and IPv6 Numbers Registration • AS Number Registration • Registration Call Center • Reverse Delegation • WHOIS Directory Service • Routing Registry Service

17. IPv4 Allocation Rate in 2000 (1.28 /8) (1.5 /8) APNIC RIPE NCC ARIN (2.0 /8)

18. IPv4 Unallocated Currently 38% of all IPv4 address space has not been allocated (Reserved by the IANA)

19. IPv6 Allocations • Allocations since 1999 • A total of 75 IPv6 address blocks (/35s) allocated collectively • APNIC: 26 • ARIN: 15 • RIPE NCC: 34

20. 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

21. 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

22. Community Discussion Recommendation by Community Reviewed by Advisory Council Recommendation Forwarded to BOT BOT ApprovesNew Policy ARIN Staff Acton New Policy New Policy Life-Cycle PolicyProposed

23. Submit policy proposal at least 6 weeks before meetings 1. Statement of policy 2. Arguments and discussion summary 3. Proposed timetable Proposal declared emergency by Board? yes no ARIN posts proposal on mailing list at least 30 days before meetings Discussions are held at Public Policy Meetings Final proposal with comments presented to Board yes Board reviews proposal no yes no Ratified? no yes ARIN posts to mailing lists for no less than 10 working days for discussion No action taken AC evaluates then posts final proposal to mailing lists for no less than 10 working days Further action considered? Enact policy and post announcement Community / Member consensus reached? Return proposal to AC for revision

24. 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

25. Mailing List Discussions • IPv6 Working Group (v6wg@arin.net) • IPv6 allocations for exchange points • IPv6 reassignment policy (/48) • Public Policy (ppml@arin.net) • Single organizations with multi-homed, discrete networks • Virtual Web Hosting Working Group (vwp@arin.net) • Name-based web hosting policy • Database Working Group (dbwg@arin.net) • Reassignment options • Database redesign

26. Request Criteria for IPv4 Address Space (ISPs) • 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

27. Request Criteria for Additional IPv4 Addresses (ISPs) • 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

28. Request Criteria for IPv4 AddressesEnd-Users • 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.

29. 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

30. Bootstrap Phase Criteria • BGP peering relationships with at least three other public ASes in IPv4 default-free zone • Must demonstrate production IPv6 within 12 months and either • Must be IPv4 provider to 40 sites that merit /48 IPv6 allocations or • 3 months of 6bone pTLA experience in overall 6-month 6bone

31. General Phase Criteria • BGP peering relationships with 3 other IPv6 networks with sub-TLA IDs and either • Requesting organization must have reassigned addresses from upstream providers to 40 SLA customer sites or • Requesting organization must demonstrate a clear intent to provide IPv6 within 12 months

32. Request Criteria forAS Numbers • 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

33. 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?

34. 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?

35. 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?

36. Top 10 Questions • What is the difference between an assignment and allocation? • How long does it take for ARIN to look at my request?

37. Top 10 Questions • Does ARIN prefer SWIP or RWHOIS as a reassignment option? • Does ARIN accept credit cards for registration fees?

38. Common Misconceptions • ARIN staff make up the “rules” as they go along. • ARIN is difficult to deal with. • ARIN is the “Internet police.”

39. Contact Information • Help Desk • (703)227-0660 • Monday – Friday7 AM – 7 PM US Eastern time • Hostmaster Email • Hostmaster@arin.net • Ticketing system for request/inquiry tracking • www.arin.net

40. Questions? NANOG 22 Scottsdale, AZ