I’m saying that the alternate text Scott proposed is actually harder to 
understand and has the additional negative potential for unintended 
consequences of accidental desynchronization.

Owen

> On Feb 22, 2017, at 12:00 PM, Jason Schiller <[email protected]> wrote:
> 
> Owen,
> 
> Just to be clear.  You think the text as written is better, more 
> understandable, and clearer, but you believe it will still operate the same 
> way regardless of the text, namely:
> 
> Once approved for a certain size block, you can complete multiple transfers 
> that add up to that size within a two year window.
> 
> ___Jason 
> 
> On Wed, Feb 22, 2017 at 2:15 PM, Owen DeLong <[email protected] 
> <mailto:[email protected]>> wrote:
> I disagree… First, I think it’s actually harder to understand. Second, I 
> think it is a bad idea to create multiple specifications or specification 
> points for the pre-authorization window because it creates a potential for 
> accidental desynchronization in future policy efforts.
> 
> Owen
> 
>> On Feb 22, 2017, at 10:48 , Jason Schiller <[email protected] 
>> <mailto:[email protected]>> wrote:
>> 
>> I got the impression from Scott that alternate text was more clear and 
>> preferred.
>> (note I'm not advocating for it, I believe it has no impact on 
>> implementation).
>> 
>> 8.5.7 Alternative Additional IPv4 Address Block Criteria
>> 
>> In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 
>> address blocks by demonstrating 80% utilization of their currently allocated 
>> space. If they do so, they are pre-authorized for a two year window to 
>> receive one or more transfers up to the total size of their current ARIN 
>> IPv4 address holdings, with a maximum size of /16.
>> 
>> An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 
>> 6 month period.
>> 
>> ___Jason
>> 
>> On Tue, Feb 21, 2017 at 2:57 PM, ARIN <[email protected] <mailto:[email protected]>> 
>> wrote:
>> On 16 February 2017 the ARIN Advisory Council (AC) advanced the following 
>> Draft Policy to Recommended Draft Policy status:
>> 
>> ARIN-2016-3: Alternative simplified criteria for justifying small IPv4 
>> transfers
>> 
>> The text of the Recommended Draft Policy is below, and may also be found at:
>> https://www.arin.net/policy/proposals/2016_3.html 
>> <https://www.arin.net/policy/proposals/2016_3.html>
>> 
>> You are encouraged to discuss all Recommended Draft Policies on PPML
>> prior to their presentation at the next ARIN Public Policy Meeting (PPM) or 
>> Public Policy Consultation (PPC). PPML and PPC discussions are invaluable to 
>> the AC when determining community consensus.
>> 
>> The PDP can be found at:
>> https://www.arin.net/policy/pdp.html <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 
>> <https://www.arin.net/policy/proposals/index.html>
>> 
>> Regards,
>> 
>> Sean Hopkins
>> Policy Analyst
>> American Registry for Internet Numbers (ARIN)
>> 
>> 
>> Recommended Draft Policy ARIN-2016-3: Alternative simplified criteria for 
>> justifying small IPv4 transfers
>> 
>> Version Date: 16 February 2017
>> 
>> AC's Statement of Conformance with ARIN's Principles of Internet Number 
>> Resource Policy
>> 
>> This proposal is technically sound and enables fair and impartial number 
>> policy by allowing transfers to specified recipients of blocks of a certain 
>> size to occur without a needs assessment performed by ARIN staff. The Staff 
>> and Legal Assessment raised no material issues, and there has been 
>> consistent support on both the mailing list and at the Dallas ARIN meeting 
>> for incorporating this mechanism into NRPM.
>> 
>> Problem Statement:
>> 
>> ARIN transfer policy currently inherits all its demonstrated need 
>> requirements for IPv4 transfers from NRPM sections 4. Because that section 
>> was written primarily to deal with free pool allocations, it is much more 
>> complicated than is really necessary for transfers.
>> 
>> This proposal allows organizations using 80% of their current space to 
>> double their current holdings via 8.3 or 8.4 specified transfers, up to a 
>> /16 equivalent.
>> 
>> Policy Statement:
>> 
>> Add a new section:
>> 
>> 8.5.7 Alternative Additional IPv4 Address Block Criteria
>> 
>> In lieu of 8.5.5 and 8.5.6, organizations may qualify for additional IPv4 
>> address blocks by demonstrating 80% utilization of their currently allocated 
>> space. If they do so, they qualify to receive one or more transfers up to 
>> the total size of their current ARIN IPv4 address holdings, with a maximum 
>> size of /16.
>> 
>> An organization may qualify via 8.5.7 for a total of a /16 equivalent in any 
>> 6 month period.
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected] 
>> <mailto:[email protected]>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml 
>> <http://lists.arin.net/mailman/listinfo/arin-ppml>
>> Please contact [email protected] <mailto:[email protected]> if you experience any 
>> issues.
>> 
>> 
>> 
>> -- 
>> _______________________________________________________
>> Jason Schiller|NetOps|[email protected] 
>> <mailto:[email protected]>|571-266-0006 <tel:(571)%20266-0006>
>> 
>> _______________________________________________
>> PPML
>> You are receiving this message because you are subscribed to
>> the ARIN Public Policy Mailing List ([email protected] 
>> <mailto:[email protected]>).
>> Unsubscribe or manage your mailing list subscription at:
>> http://lists.arin.net/mailman/listinfo/arin-ppml 
>> <http://lists.arin.net/mailman/listinfo/arin-ppml>
>> Please contact [email protected] <mailto:[email protected]> if you experience any 
>> issues.
> 
> 
> 
> 
> -- 
> _______________________________________________________
> Jason Schiller|NetOps|[email protected] 
> <mailto:[email protected]>|571-266-0006
> 

_______________________________________________
PPML
You are receiving this message because you are subscribed to
the ARIN Public Policy Mailing List ([email protected]).
Unsubscribe or manage your mailing list subscription at:
http://lists.arin.net/mailman/listinfo/arin-ppml
Please contact [email protected] if you experience any issues.

Reply via email to