[arin-ppml] LAST CALL: Recommended Draft Policy ARIN-2013-7: NRPM 4 (IPv4) Policy Cleanup

Owen DeLong owen at delong.com
Wed May 28 03:42:27 EDT 2014


Marla,

The policy as written with the word OR is an inclusive OR, not an exclusive OR. Further, 8.3 and 8.4 are not related to acquisitions. 8.3 is a specified transfer within the ARIN region. 8.4 is a specified transfer to or from an entity served by another RIR.

Acquisitions and Mergers are handled under 8.2 and are not subject to the restrictions in 4.2.4.3.

Given that, does your objection still stand? If so, please clarify.

Owen

On May 27, 2014, at 4:27 PM, Azinger, Marla <Marla.Azinger at FTR.com> wrote:

> What happened to the And vs OR wording?  Seriously this is a problem.  I understand some people didn't follow the linguistics of this, but as someone who has dealt with this type of thing already, if you don't change the wording you will mess up companies. 
> 
> John Sweeting I know you understood this point.  Could you please way in here with AC and BOT before this is passed?  I don't see the added sentence changing this issue as long as the other sentence is included as is.
> 
> -Replace and retitle section 4.2.4.3 Subscriber Members Less Than One Year   
> If you fix the wording this change is okay.  This needs to say AND not OR.  
> A business can purchase a business set in the same year they need to do a market transfer of addresses.  this should not be limited 
> to either or as that is ignorant of how organizations can function.  Replace with: (4.2.4.3 Request size)
> 
> needed change in wording:  "ISPs may request up to a 3-month supply of IPv4 addresses from ARIN, or a 24-month supply via 8.3 "AND" 8.4 transfer."
> 
> Thank you
> Marla
> 
> -----Original Message-----
> From: arin-ppml-bounces at arin.net [mailto:arin-ppml-bounces at arin.net] On Behalf Of ARIN
> Sent: Friday, May 16, 2014 1:22 PM
> To: arin-ppml at arin.net
> Subject: [arin-ppml] LAST CALL: Recommended Draft Policy ARIN-2013-7: NRPM 4 (IPv4) Policy Cleanup
> 
> The ARIN Advisory Council (AC) met on 15 May 2014 and decided to send the following to last call:
> 
>   Recommended Draft Policy ARIN-2013-7: NRPM 4 (IPv4) Policy Cleanup
> 
> 2013-7 was revised. The following sentence was added to 4.2.4.3:
> "Determination of the appropriate allocation to be issued is based on efficient utilization of space within this time frame, consistent with the principles in 4.2.1."
> 
> Feedback is encouraged during the last call period. All comments should be provided to the Public Policy Mailing List. This last call will expire on 2 June 2014. After last call the AC will conduct their last call review.
> 
> The draft policy text is below and available at:
> https://www.arin.net/policy/proposals/
> 
> The ARIN Policy Development Process is available at:
> https://www.arin.net/policy/pdp.html
> 
> Regards,
> 
> Communications and Member Services
> American Registry for Internet Numbers (ARIN)
> 
> 
> ## * ##
> 
> 
> Recommended Draft Policy ARIN-2013-7
> NRPM 4 (IPv4) Policy Cleanup
> 
> Date: 16 May 2014
> 
> AC's assessment of conformance with the Principles of Internet Number Resource Policy:
> 
> "ARIN-2013-7: "NRPM 4 (IPv4) Policy Cleanup" enables fair and impartial number resource administration by removing no-longer-relevant sections of the NRPM, and clarifying other sections. All of the remaining changes in this draft policy have proven uncontroversial thus far."
> 
> Problem Statement: Parts of NRPM 4 are irrelevant, especially after IPv4 run-out, and should be cleaned up for clarity.
> 
> Policy statement:
> 
> Short list of changes with details explained below.
> 
> Remove section 4.1.1 Routability
> 
> Update section 4.1.5 Determination of resource requests
> 
> Remove section 4.1.7 RFC2050
> 
> Remove section 4.1.9 Returned IPv4 Addresses
> 
> Replace and retitle section 4.2.4.3 Subscriber Members Less Than One Year
> 
> Remove section 4.2.4.4. Subscriber Members After One Year
> 
> Details:
> 
> Remove section 4.1.1 Routability
> 
> It is no longer necessary for the NRPM to suggest where an organization obtains resources from.
> 
> Retitle and rewrite section (4.1.5 Determination of IP address allocation size)
> 
> Remove: "Determination of IP address allocation size is the responsibility of ARIN."
> 
> Replace with: (4.1.5 Resource request size) "Determining the validity of the amount of requested IP address resources is the responsibility of ARIN."
> 
> Rationale: Clarify that it is the validity of the request that is more the focus than the amount of resources requested. This does not prevent ARIN from suggesting that a smaller block would be justified where a larger one would not, but also does not suggest that it is ARIN's sole discretion to judge the size of the blocks needed.
> 
> Remove section 4.1.7 RFC2050
> 
> Now that RFC2050 has been replaced with RFC 7020 and ARIN-2013-4 RIR Principles has been adopted, this section is no longer needed.
> 
> Remove section 4.2.4.3 Subscriber Members Less Than One Year and 4.2.4.4. Subscriber Members After One Year
> 
> Replace with: (4.2.4.3 Request size) "ISPs may request up to a 3-month supply of IPv4 addresses from ARIN, or a 24-month supply via 8.3 or 8.4 transfer. Determination of the appropriate allocation to be issued is based on efficient utilization of space within this time frame, consistent with the principles in 4.2.1."
> 
> Rationale: Since ARIN received its last /8, by IANA implementing section 10.4.2.2, this is now a distinction without a difference.
> 
> Timetable for implementation: Immediate
> _______________________________________________
> 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.
> _______________________________________________
> 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.




More information about the ARIN-PPML mailing list