[arin-ppml] Initial ISP Allocation Policy

Matthew Wilder Matthew.Wilder at telus.com
Thu Jul 18 12:16:34 EDT 2013

Hi David,

I think this is a great way of looking at.  NRPM could be so much simpler, but in a multi-stakeholder world, we all see the tendency for policy changes to complicate, not simplify NRPM.  The only way to simplify NRPM to a reasonable (sane) state is to start with a blank sheet of paper, as you say.  Our current NRPM is just shy of 15,000 words.  The sections which really need to be updated to accomplish your stated objective are section 4 and section 6, which combined contain 8,356 words.  In my mind a sane NRPM would have half that many words.  

If you constrain the efforts simply to merging any policy which distinguishes between End Users and ISPs, you will have around 4,000 words in scope.  I imagine the majority of challenge faced in this activity will be merging section 4.2 with 4.3, with several topics sure to create quite the discussion (3 month allocations for ISPs vs 12 months for End Users, Registration for downstream customers to name two).

The way I could imagine finding some success in the overarching ambitions is to define what sections of NRPM we are interested in transforming, and by contrast those which we believe should stand.  I believe that the majority of content outside section 4 and section 6 is reasonable enough.  I also believe that your intent is primarily to simplify the NRPM as it relates to allocation of IPv4 and IPv6 resources, so likely the energy should naturally focus on those 2 sections.

If the community is in support of re-writing those sections of NRPM, the two following topics should be considered for discussion (and possibly more I have not identified):  

1. Will three month allocations apply also to End-Users as it does to ISPs?  This is going to be the biggest bone of contention as I see it, and the big reason why many would still see value in a distinction between ISP and End-User, despite lines blurring as many have observed.  I work for an ISP, and I see the similarities of hotels, coffee shops, CDNs, cloud providers and so on.  To what set or subset of Orgs should the three month allocation apply?  Merging End-Users and ISPs in policy will be challenging here.

2. What reassignments need to be registered for the global community's benefit in a paradigm which no longer distinguishes between ISP and End-User?  I would suggest that static assignments of a certain size to entities outside the Organization specified as the resource holder should be registered.  This mean Starbucks and the Hyatt don't have to register their DHCP pools used by their customers (although maybe a record of that DHCP would be desirable).  In any case, this needs to be thought through at a higher level and then specifications laid out.

I am certainly interested in seeing what other have to say.  It may be very difficult to parse what can be reasonably removed from expectations of ISPs in order to align with End-Users, and conversely how happy End-Users will be to share the 3-month allocation policy with ISPs.  If the majority of value is seen by many in simple alignment of initial allocation and assignment (and to some degree subsequent allocation / assignment), I believe the policy changes will be much easier to manage and build consensus around.

Matthew Wilder

-----Original Message-----
From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of David Huberman
Sent: July 18, 2013 01:36 AM
To: arin-ppml at arin.net
Subject: Re: [arin-ppml] Initial ISP Allocation Policy

Hello everyone,

I would like to thank everyone for a very good discussion in this thread. First I'll give a very brief summary of the discussion so far, and then I have a solution to float to the list for feedback.

Myself, Dan, Bill, and Steven have posted in favor of the high level concept that the differentiation in ARIN policy between enterprise networks and provider networks is no longer productive or relevant.  Owen may agree in principle, but cautions us to be very careful with how we proceed.  He is concerned that an effective "one size fits all" solution may be very difficult to design. George offers us an alternative nomenclature to consider (NSP v. ISP).

I would like to now shift the discussion to how we approach potentially collapsing the two categories into one so that future interactions with ARIN are conducted under policy language which is relevant in 2014 and beyond.

I agree with Dan that a wholesale paradigm shift in ARIN policy can only be accomplished with multiple proposals. There would be quite a few sections to change (with each change requiring careful consideration by the community).  Moreover, I think we must be sensitive to ARIN's need to react to the possible impacts to both the financial and workflow modeling that would result from any changes we propose.  

At the same time, incremental change in NRPM is actually really hard. If this were 5 years ago, I would probably work very hard to help effect incremental change.  But I think ARIN and the community have together failed to react to changes in the market over the last 15 years, and it is time to consider very big change. Let's get NRPM into a sane state for 2014 and beyond.

In an effort to roll up sleeves and be productive, please indulge me while I lay out one potential vision for what a sane NRPM might look like.  I warn you, good reader, that some of what I propose is very radical.

- A section on obtaining initial IPv4 addresses from ARIN.  No distinction between end-users and ISPs.  No distinction between single-homed and multi-homed deployments (*if you don't understand why the difference has no virtue, ping me on or off list and I will show you the math as I see it).  Text might look something like:

	"In order to receive an initial allocation from ARIN, an organization must:
		- demonstrate they operate an IP network that requires 
		IPv4 addresses to deploy and/or grow; and

		- provide a numbering plan detailing how IPv4 addresses 
		will be used in the first 180 days upon receiving an allocation.

	ARIN will review and verify the data provided, and provide for the organization's 6 month need."

- A section on obtaining additional blocks, which still outlines the 80% rule. ("If you've efficiently used what you have, you can have more" is a technically sound concept that does not need much fixing.)  Platform differences which are already fleshed out in NRPM (e.g., residential market area provider networks with their different metrics than more common buildouts) can and should remain.  

- We would have to figure out what to do with the requirement to SWIP, as the requirement is predicated on the classification of "ISP" actually existing (which it would not).  That might need a working group to reconcile.

- A section on obtaining initial IPv6 addresses from ARIN. Given that IPv6 is still very much in its infancy, I really would like to see very simple NRPM text which allows requestors to self-select what size block they need. The only barrier to abuse or silliness would be the fee schedule.   It is arrogant and technically indefensible that ARIN policy today tries to dictate what a network does, and does not, justify as far as block size.  IPv6 is much too immature for ARIN policy to presume such wisdom.

- A section on obtaining additional IPv6 addresses from ARIN.  Existing text in 6.5.3 is probably good enough for today, as there are only a handful of networks in the world with any experience needing additional IPv6 addresses due to efficient use of an initial block.  Obtaining additional IPv6 addresses is a topic for many years from now, not today.

Do you think any of this has value?  Would it accomplish the overarching goal of improving ARIN policy to make it relevant to network operators in 2014 and beyond?  What would your sane NRPM look like?

With regards,

You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (ARIN-PPML at arin.net).
Unsubscribe or manage your mailing list subscription at:
Please contact info at arin.net if you experience any issues.

More information about the ARIN-PPML mailing list