Madison, WI 9 September 2014

Transcription

1 1 Madison, WI 9 September 2014

2 2 Part 1 IPv4 Depletion Leslie Nobile Director, Registration Services

3 3 ARIN s IPv4 Inventory As of 2 Sept 2014, ARIN has 0.76 /8 equivalents of IPv4 addresses remaining IPv4 inventory published on ARIN s website: Updated 8PM ET

4 4 Prefix Length Breakdown

5 5 IPv4 Churn IPv4 addresses go back into ARIN s free pool 4 ways Return = voluntary Revoke = for cause (usually nonpayment) Reclaimed = fraud or business dissolution IANA issued per global policy for post exhaustion IPv4 allocation mechanism by IANA 3.54 /8s recovered since 2005 /8 equivalent returned to IANA in 2012 /11(May 2104) & /12 (Sept 2014) issued by IANA

6 6 Burn Rate vs. Churn Rate # /24s issued # /24s received back

7 7 IPv4 Annual Burn Rate /8 Equivalents Issued

8 8 ARIN s IPv4 Free Pool /8 Equivalents in ARIN Free Pool

9 9 Linear Depletion Projection /8 Equivalents in ARIN Free Pool

10 10 Run On The Bank Projection /8 Equivalents in ARIN Free Pool

11 11 Which Projection is More Likely? Probably somewhere in the middle, but it only takes one unexpected very large request (e.g. /10) to change things completely Policy requirement to only fill requests with one block will prevent large ISPS from depleting all of the small blocks

12 12 IPv4 Countdown Plan Phase 4 Started at 1 /8 equivalent left All IPv4 requests team-reviewed and processed on a first in, first out basis Org has 60 days from approval to complete payment and RSA IPv4 hold period drops to 2 months

13 13 Part 2 Obtaining IPv4 and IPv6 from ARIN Leslie Nobile Director, Registration Services

14 14 New IPv4 Policy Reduce All Minimum Allocation/ Assignment Units to /24 Will be implemented on 17 Sept 2014 /24 minimum allocation/assignment No longer a multi-homed requirement

15 15 Minimum Requirements for IPv4 - ISPs ISPs qualify for a /24 by having one /24 reassigned and efficiently used Allocations > /24 based on demonstrated utilization history and renumbering (if applicable) Allocation size not based on predicted customer base (see Slow Start policy NRPM ) 3 month supply per policy

16 16 IPv4 ISP Data Typically Requested Static: Mapping of static IPs/subnets to customer names and street addresses Dynamic: List of all dynamic pools with prefix/range assigned, area served (location), peak util % Internal Infrastructure: Mapping of internal subnets with description and # IPs used

17 Example 17

18 18 Other IPv4 ISP Data Requested Typically ask for: Customer justification data If necessary, may ask for: Customer contact information and proof of customer payments Proof of equipment lease/purchase

19 19 Minimum Requirements for IPv4 End Users /24 minimum assignment size Show 25% immediate utilization rate (within 30 days) and 50% projected one-year utilization rate If requesting additional assignment, must show that each previous assignment is 80% utilized

20 20 IPv4 End User Data Requested Subnet mapping for previous ARIN assignments Each subnet with description and # IPs currently used Planned subnet mapping for requested block Each subnet with description, # IPs used within 30 days, # IPs used within one year

21 Example 21

22 22 The Bottom Line ARIN has v4 space today, but can t guarantee future availability Plan appropriately to ensure continued growth of your network Waiting List Specified Recipient Transfers IPv6

23 23 Qualifying for IPv6 - ISPs Have a previous v4 allocation from ARIN OR Intend to multi-home OR Provide a technical justification which details at least 50 assignments made within 5 years

24 24 IPv6 ISP Data Typically Requested If requesting more than a /32, a spreadsheet/text file with # of serving sites (PoPs, datacenters) # of customers served by largest serving site Block size to be assigned to each customer (/48 typical)

25 25 Qualifying for IPv6 End Users Have a v4 direct assignment OR Intend to multi-home OR Show how you will use 2000 IPv6 addresses or 200 IPv6 subnets within a year OR Technical justification as to why provider-assigned IPs are unsuitable

26 26 IPv6 End Users Data Requested List of sites in your network Site = distinct geographic location Street address for each Campus may count as multiple sites Technical justification showing how they re configured like geographically separate sites

27 27 ISP Members with IPv4 and IPv6 100% 90% 80% 70% 60% 50% 40% 30% 20% 10% 0% 2010Q3 2011Q3 2012Q3 2013Q3 2014Q3 % IPv4 Only 75% 66% 62% 59% 58% % IPv4 and IPv6 25% 34% 38% 41% 42% *4,818 total members IPv4- only and IPv4+v6 ISPs

28 Q&A 28