Mar 27, 2015
The Regional Internet Registry System
RIR 101
November 2002 LACNIC III Ciudad de México
Overview
• Evolution
• Structure
• Activities and Functions
• IP Address Space Management
• Policy Development Process
November 2002 LACNIC III Ciudad de México
Pre 1992
RFC 10201987
RFC 7901981
RFC 12611991
“The assignment of numbers is also handled by Jon. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, or network number please contact Jon to receive a number assignment.”
November 2002 LACNIC III Ciudad de México
1992
RFC 1366Geographic Allocations
November 2002 LACNIC III Ciudad de México
1993
RFC 14661993
November 2002 LACNIC III Ciudad de México
1996
RFC 20501996
November 2002 LACNIC III Ciudad de México
1997
November 2002 LACNIC III Ciudad de México
1998
ICANN / ASO MoU1999
November 2002 LACNIC III Ciudad de México
2002
November 2002 LACNIC III Ciudad de México
Emerging RIR
November 2002 LACNIC III Ciudad de México
Structure
• Not For Profit Membership Organization– Membership Open to All Interested Parties– Membership Elects Executive Board– Membership Approves Activities & Budget– Neutral and Impartial
• Funding– Annual service fee– No charge per IP address– Open Financial Reporting
• Policies Developed by Industry Through Bottom-Up Open Policy Processes
November 2002 LACNIC III Ciudad de México
Activities & Functions
Activities
• ASO Support
• Outreach
• Coordination
Functions• Address Space
Management• Policy Development• Reverse DNS
November 2002 LACNIC III Ciudad de México
Outreach Coordination
ASO
Support
Activities
• ASO Secretariat • ASO AC Support • General Assembly
• Meetings and Presentations
– Government representatives
– Industry groups
– IPv6 Forum
• Training Programs
• Registration Services
• Policy
• Documentation
• Engineering
• Outreach
• Presentations
November 2002 LACNIC III Ciudad de México
Policy
DevelopmentReverse DNS
Address Space
Management
Functions
• Conservation
• Aggregation
• Registration
• Open
• Transparent
• Documented
• Developed Bottom-UP
• in-addr.arpa
• ip6.arpa
• /8
November 2002 LACNIC III Ciudad de México
IP Addressing
• What is an IP Address?• How is IP Address Space Managed?• How is IP Address Space Policy Developed?
November 2002 LACNIC III Ciudad de México
What is an IP Address?
• A Number Used for Routing
• Not Dependent on DNS
• A Finite Public Resource
• Not Owned
• IP Does Not Mean “Intellectual Property”
November 2002 LACNIC III Ciudad de México
How is IP Address Space Managed
• Address Space Management Objectives
• Implementation of Policy
November 2002 LACNIC III Ciudad de México
Aggregation Registration
Conservation
Address Management Objectives
• Efficient Use of Resources
• Based on Need
• Limit Routing Table Growth
• Support Provider-Based Routing Policies
• Ensure Uniqueness
• Trouble Shooting
November 2002 LACNIC III Ciudad de México
Policy Implementation[ Industry Self-Regulation ]
• RIR Staffs• Service Providers
November 2002 LACNIC III Ciudad de México
How is IP Address Policy Developed?
• According to Policy Development Principles• In a Cyclical Manner
November 2002 LACNIC III Ciudad de México
Policy Development Principles
• Open– Anyone Can Participate
– Policy Fora
– Mail Lists
• Transparent
– Mail List Archives
– Minutes
• Policy Fora
• RIR Boards
• Documented– Formal Policy
Documents– Implementation
Procedures
• Developed Bottom-Up– Internet Community– Stakeholders– Technology Changes– IETF
November 2002 LACNIC III Ciudad de México
Consensus
Need
Discuss
Evaluate
Implement
Policy
Development
Cycle
OPEN TRANSPARENT
DEVELOPEDBOTTOM UP
DOCUMENTED
November 2002 LACNIC III Ciudad de México
Recent Open Policy Meetings• APNIC (2 per year)
3 - 6 Sep ** APNIC 12 - Kita-Kyushu, Fukuoka, JP
• RIPE NCC (3 per year)9 - 13 Sep ** RIPE 43 - Rhodes, GR
• ARIN (2 per year)30 Oct – 1 Nov ** ARIN X – Eugene, Oregon, US
• LACNIC (2 per year)11 – 12 Nov ** Mexico City, MX
November 2002 LACNIC III Ciudad de México
Thank You Gracias
Obrigado