Scott, Asking me to do the work the AC is supposed to do is like asking a nun to certify their virginity.
I made my point and I feel zero need to defend what is completely obvious and on the record. As I explained to our "CEO and President", feel free to demonstrate otherwise. Best, Martin > On Jun 30, 2014, at 19:38, Scott Leibrand <[email protected]> wrote: > > Martin, > > I felt the objections raised at previous meetings were addressed, not > ignored. Can you clarify how you feel that this policy would make it harder > for a recipient to qualify to receive space via transfer? The intent here is > to allow organizations to create new discrete networks and qualify for space > from them. If you think it will do the opposite, it's worth detailing how and > why. > > It's also worth noting that, by documenting the basic requirements for such > networks, it also reduces ARIN staff's discretion and provides additional > policy certainty. > > Scott > >> On Jun 30, 2014, at 3:58 PM, Martin Hannigan <[email protected]> wrote: >> >> Objection, with the majority of the community from the previous ARIN >> meeting, recent NANOG PPC and other comments and fora discussion. >> >> But don't let that stop the ARIN AC from moving it forward in its obsession >> with controlling v4 markets. >> >> Best, >> >> -M< >> >> >>> On Jun 30, 2014, at 17:34, CJ Aronson <[email protected]> wrote: >>> >>> Hi everyone >>> >>> Does anyone have comments on this recommended draft policy? >>> >>> Thanks! >>> ----Cathy >>> >>> >>>> On Tue, Jun 24, 2014 at 2:16 PM, ARIN <[email protected]> wrote: >>>> The ARIN Advisory Council (AC) met on 19 June 2014 and decided to >>>> send the following to last call: >>>> >>>> Recommended Draft Policy ARIN-2013-8: Subsequent Allocations for New >>>> Multiple Discrete Networks >>>> >>>> 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 8 July 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-8 >>>> Subsequent Allocations for New Multiple Discrete Networks >>>> >>>> Date: 16 May 2014 >>>> >>>> AC's assessment of conformance with the Principles of Internet Number >>>> Resource Policy: >>>> >>>> This proposal enables fair and impartial number resource administration by >>>> documenting how to get a new block for a new discrete network. Previous >>>> versions of the policy did have this information and over time it has been >>>> removed. >>>> >>>> This proposal is technically sound. There is a need for discrete networks >>>> and an organization should have a policy that would allow it to create a >>>> new discrete network. >>>> >>>> This proposal is supported by the community. There has been some concern >>>> about the criterial that will be used and this version has been updated >>>> with the current thinking on the criteria. >>>> >>>> Policy Statement: >>>> >>>> IPv4: >>>> Add the following statement to section 4.5.4. >>>> Upon verification that the organization has shown evidence of deployment >>>> of the new discrete network site, the new network(s) shall be allocated >>>> the minimum allocation size under section 4.2.1.5 unless the organization >>>> can demonstrate additional need using the immediate need criteria >>>> (4.2.1.6). >>>> >>>> IPv6: >>>> Add an additional reference to section 6.11.5.b such that it references >>>> both the initial allocation and subsequent allocation sections of the IPv6 >>>> LIR policy. >>>> "Each network will be judged against the existing utilization criteria >>>> specified in 6.5.2 and 6.5.3 as if it were a separate organization..." >>>> >>>> Comments: >>>> a. Timetable for implementation: immediate >>>> b. This policy is being proposed based upon the Policy Implementation & >>>> Experience Report from ARIN 32. >>>> https://www.arin.net/participate/meetings/reports/ARIN_32/PDF/thursday/nobile-policy.pdf >>>> c: Older versions of the MDN policy did contain new network criteria. This >>>> criteria appears to have been dropped during subsequent rewrites of the >>>> MDN policy. "The organization must not allocate a CIDR block larger than >>>> the current minimum assignment size of the RIR (currently /20 for ARIN) to >>>> a new network." (https://www.arin.net/policy/archive/nrpm_20041015.pdf) >>>> _______________________________________________ >>>> 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. >>> >>> _______________________________________________ >>> 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. >> _______________________________________________ >> 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.
_______________________________________________ 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.
