[arin-ppml] Draft Policy ARIN-2015-8: Reassignment records for IPv4 End-Users

Tue Oct 6 15:14:28 EDT 2015

What about setting a limit on the amount of space that can be re-assigned, or the number of re-assignments?  Say 25% of the maximum possible reassignments using the current minimum reassignment size (/29), based on the upper bound of the fee category they're in (e.g., xx-small = /22 = 1024*.25/8 = 32 re-assignmentsl). Or up 50% of the assigned space?

It’s also worth noting that this only addresses IPv4 re-assignments under Section 4.  There should be parity for IPv6 (which I understand is currently a draft).   Doing them in tandem would give this more weight, IMHO.

End-users make up over 40% of the Orgs in the ARIN region. If a “single” policy is a desired outcome, then we should either make accommodations for End Users that starts to level the field, or create a middle-ground that’s acceptable should things stall.  Half-measure are often rebuked because they potentially leave you in an unenviable (or untenable) state.

-Chris

On Oct 5, 2015, at 3:39 PM, David Farmer <farmer at umn.edu> wrote:

> Marla,
> 
> From a strategic point of view I agree that we should move to a one policy for everyone model.
> 
> However, every time we try all-encompassing strategic changes, people say they are too big of a change all at once, and tell us to break them up.  When we brake them up into manageable size chunks, the individual changes don't get support because people don't want to see half-measures they want strategic level changes.
> 
> This is a catch 22. We need to find a way to move forward. How would you suggest we do that?
> 
> Thanks.
> 
> On 10/5/15 13:55 , Azinger, Marla wrote:
>> I don't support this based on what I see as a missed opportunity.  This policy calls attention to the fact that ARIN should consider removing any difference in policy between End Users and ISPs.  I agree this proposal has valid case use scenarios, however it just leaves me thinking only one "class" is needed and not two.  One policy for all.
>> 
>> Regards
>> Marla Azinger
>> 
>> -----Original Message-----
>> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of ARIN
>> Sent: Tuesday, August 25, 2015 12:12 PM
>> To: arin-ppml at arin.net
>> Subject: [arin-ppml] Draft Policy ARIN-2015-8: Reassignment records for IPv4 End-Users
>> 
>> Draft Policy ARIN-2015-8
>> Reassignment records for IPv4 End-Users
>> 
>> On 20 August 2015 the ARIN Advisory Council (AC) accepted "ARIN-prop-222 Reassignment records for IPv4 End-Users" as a Draft Policy.
>> 
>> Draft Policy ARIN-2015-8 is below and can be found at:
>> https://www.arin.net/policy/proposals/2015_8.html
>> 
>> You are encouraged to discuss the merits and your concerns of Draft Policy 2015-8 on the Public Policy Mailing List.
>> 
>> The AC will evaluate the discussion in order to assess the conformance of this draft policy with ARIN's Principles of Internet Number Resource Policy as stated in the PDP. Specifically, these principles are:
>> 
>>     * Enabling Fair and Impartial Number Resource Administration
>>     * Technically Sound
>>     * Supported by the Community
>> 
>> The ARIN Policy Development Process (PDP) can be found at:
>> https://www.arin.net/policy/pdp.html
>> 
>> Draft Policies and Proposals under discussion can be found at:
>> https://www.arin.net/policy/proposals/index.html
>> 
>> Regards,
>> 
>> Communications and Member Services
>> American Registry for Internet Numbers (ARIN)
>> 
>> 
>> ## * ##
>> 
>> 
>> Draft Policy ARIN-2015-8
>> Reassignment records for IPv4 End-Users
>> 
>> Date: 25 August 2015
>> 
>> Problem statement:
>> 
>> End-User Organizations do not have the ability to create reassignment records in the number resource database.
>> 
>> Reassignment records can be used for a number of different functions which could benefit the overall desire to increase database accuracy by allowing organizations to add additional details in the database.
>> 
>> The following reasons have been noted as positive reasons to allow the creation of additional records.
>> - Geolocation (allows an organization to specify a different location within the database which is used by organizations creating geo-location by IP address databases)
>> - Subsidiary reassignment (allows an organization to note that a portion of their netblock is in use by a different subsidiary entity)
>> - Assignment to contracted parties (some organizations have contracts with other organizations which are operating networks under agreements with the registrant, this allows the top-level organizations to accurately specify the organization operating the network in the number resource database)
>> - More specific contact information (some organizations operate large networks which don't necessarily have the same technical or abuse contact information)
>> 
>> Policy statement:
>> 
>> Create new section 4.3.x
>> 
>> End-user organizations which have an active registration services agreement shall be permitted to create reassignment records in the number resource database. Organizations shall use the guidelines outlined in section 4.2.3 when creating reassignment records.
>> 
>> Comments:
>> a. Timetable for implementation: immediately b. Anything else:
>> 
>> It is noted by the author of this policy proposal that one of the distinctions in the service between ISPs and End-Users has been the ability for an organization to create reassignment records.
>> 
>> This policy proposal stretches across responsibilities areas as it impacts number policy, ARIN operational practice, and fees.
>> 
>> Below we have noted the three areas and the different responsibilities:
>> 
>> A) Providing reassignment support for end-user assignments, for those who wish to use it
>> 
>> This is an ARIN Service issue - could be an suggestion/consultation process, so long as any implied additional workload/cost can be accommodated in budget and the community supports
>> 
>> B) New requirement on end-users to provide reassignment information in certain circumstances so that ARIN will treat their usage assertion credibly
>> 
>> This is a policy issue. These requirements should be vetted through the policy development process.
>> 
>> C) Fee Implications of ISPs moving to end-user category
>> 
>> This is Board issue, but first requires a community discussion or consultation to be held to solicit community input on desired outcome.
>> _______________________________________________
>> PPML
>> 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:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>> 
>> ________________________________
>> 
>> This communication is confidential. Frontier only sends and receives email on the basis of the terms set out at http://www.frontier.com/email_disclaimer.
>> _______________________________________________
>> PPML
>> 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:
>> http://lists.arin.net/mailman/listinfo/arin-ppml
>> Please contact info at arin.net if you experience any issues.
>> 
> 
> 
> -- 
> ================================================
> David Farmer               Email: farmer at umn.edu
> Office of Information Technology
> University of Minnesota
> 2218 University Ave SE     Phone: 1-612-626-0815
> Minneapolis, MN 55414-3029  Cell: 1-612-812-9952
> ================================================
> _______________________________________________
> PPML
> 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:
> http://lists.arin.net/mailman/listinfo/arin-ppml
> Please contact info at arin.net if you experience any issues.