The document summarizes discussions from RIPE60 about IPv6 policies across different regional internet registries (RIRs). It outlines ARIN's criteria for issuing provider independent (PI) IPv6 assignments of up to a /48 based on IPv4 assignments, multihoming, or deployment plans. It also discusses LACNIC's policies around assigning critical infrastructure like internet exchange points a minimum of a /48. Finally, it notes RIRs are removing routing requirements and simplifying criteria to increase IPv6 deployment incentives.

1. RIPE Network Coordination Centre
IPv6 WorldWide Policy Review
Filiz Yilmaz RIPE60, May 2010, Praha http://www.ripe.net 1

2. RIPE Network Coordination Centre
IPv6 talking regions
• ARIN, APNIC, RIPE, LACNIC
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 2

3. RIPE Network Coordination Centre
ARIN
• Criteria for PI
- have IPv4 PI or,
- Be IPv6 multihomed or intend to be or
- Plan of the deployment in 1, 2 5 yrs and reason for PI
• Receive upto /48 for each site
- Site = Location, not organisation
- What is a site really?
• More discussion to come
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 3

4. RIPE Network Coordination Centre
ARIN
• Criteria for allocations
- Have IPv4 allocation or
- Be IPv6 multihomed or intend to be or
- Plan to make 50 assignments to others in 5 yrs
• “50” a good number?
• In Last Call
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 4

5. RIPE Network Coordination Centre
ARIN
• Simplified IPv6 Policy
• Different allocation/assignment sizes
- X-Small /48, Small /40, Medium /32, Large /28
- X-Large /24, XX-Large > /24
• “Classful” addressing
• Abandoned
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 5

6. RIPE Network Coordination Centre
LACNIC
• Assignments for Critical Infrastructure
- Prove IXP/NAP capacity, have at least 3 members
- Justify need
- Min /48, max /32
• End Users with “critical” infrastructure
- Not to be routed globally
- Min /48, max /40
• Under discussion
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 6

7. RIPE Network Coordination Centre
LACNIC + APNIC
• Removing Routing Requirement
• LACNIC discussing
• APNIC reached consensus
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 7

8. RIPE Network Coordination Centre
Conclusion
• Operational matters coming to surface
- “Site” definition
- Routing practices
• Simplified criteria
- Increased incentives for deployment
Filiz Yilmaz RIPE 60, May 2010, Praha http://www.ripe.net 8

9. RIPE Network Coordination Centre
Questions?
NameName event/date http://www.ripe.net 3