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

ARIN Policies and GuidelinesAn Introduction

Presented by

Richard JimmersonDirector of Operations

NANOG 22 Scottsdale, AZ


Overview

• About ARIN

• Registry Activities

• Open Policy Process

• Current Policies

• Using ARIN Services

• Top 10 Questions About ARIN


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


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


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


Area Members

North America 1,384

South America 43

Southern Africa 16

Outside Region 13

Total 1,456

95%

3% 1%

1%

ARIN Membership


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


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

AFRINIC?

LACNIC?


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


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


RIR Activities

• Address space management

• Registration

• Policy development

• Outreach


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


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


Registration

• IPv4 and IPv6 Numbers Registration

• AS Number Registration

• Registration Call Center

• Reverse Delegation

• WHOIS Directory Service

• Routing Registry Service


IPv4 Allocation Rate in 2000

RIPE NCC

ARIN

APNIC (1.5 /8)(1.28 /8)

(2.0 /8)


IPv4 Unallocated

Currently 38% of all IPv4 address

space has not been allocated

(Reserved by the IANA)


IPv6 Allocations

• Allocations since 1999• A total of 75 IPv6 address blocks (/35s)

allocated collectively

– APNIC: 26

– ARIN: 15

– RIPE NCC: 34


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


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


New Policy Life-Cycle

PolicyProposed

Recommendation by Community

Reviewed by Advisory Council

Recommendation Forwarded to BOT

BOT ApprovesNew Policy

ARIN Staff Acton New Policy

Community Discussion

ARIN posts proposal on mailing list at least 30 days

before meetings

Proposal declared emergency by

Board?

1. Statement of policy2. Arguments and discussion summary3. Proposed timetable

Submit policy proposal at least6 weeks before

meetings

no

yes

Discussions are held at Public Policy Meetings

no

No action taken

no

Further action considered?

yes

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?


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


Mailing List Discussions

• IPv6 Working Group ([email protected])

– IPv6 allocations for exchange points

– IPv6 reassignment policy (/48)

• Public Policy ([email protected])

– Single organizations with multi-homed, discrete networks

• Virtual Web Hosting Working Group ([email protected])

– Name-based web hosting policy

• Database Working Group ([email protected])

– Reassignment options

– Database redesign


• 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)


• 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)


• 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 AddressesEnd-Users


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


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


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


• 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 forAS Numbers


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?


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?


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?


Top 10 Questions

• What is the difference between an assignment and

allocation?

• How long does it take for ARIN to look at my request?


Top 10 Questions

• Does ARIN prefer SWIP or RWHOIS as a reassignment

option?

• Does ARIN accept credit cards for registration fees?


Common Misconceptions

• ARIN staff make up the “rules” as

they go along.

• ARIN is difficult to deal with.

• ARIN is the “Internet police.”


Contact Information

• Help Desk

– (703)227-0660

– Monday – Friday

7 AM – 7 PM US Eastern time

• Hostmaster Email

– [email protected]

– Ticketing system for request/inquiry tracking

• www.arin.net

Questions?
