We can work that out in operator groups. ARIN is a steward of numbers, not a regulator of operators and their routing policies.
Not adopting this will contribute another to the pile of existing reasons as to why the registry is hugely inaccurate. Best, -M< On Thu, Mar 20, 2014 at 4:30 PM, Aaron <[email protected]> wrote: > My issue with this proposal is that it might create an expectation that > operators will start routing that space. I just see a s**t storm when > Customer A gets a /29 and no one can reach it. I see it, in the long term, > generating a lot of problems. > > Aaron > > > On 3/20/2014 3:06 PM, Owen DeLong wrote: > > > On Mar 20, 2014, at 13:01 , Heather Schiller <[email protected]> > wrote: > > As a shepherd for this proposal, I would like to solicit community feedback > on the proposed text. > > Aside from the general support/against.. some things to consider: > > Do you concur with or have any comment on the problem statement? > > > I do not concur with the problem statement. > > If you support the problem statement, do you support removing section 8.2 as > the correct path for remediating this conflict? Do you have other > suggestions for how to handle this? > > > No. > > If you are opposed, what concerns do you have about implementing this > policy? > > > I have previously stated my concerns. IMHO, this is yet another attempt to > bypass the needs-basis and seeks to solve a problem which does not, in fact, > exist. > > Owen > > > Thanks, > --Heather > > > > On Tue, Mar 4, 2014 at 3:12 PM, ARIN <[email protected]> wrote: >> >> On 20 February 2014 the ARIN Advisory Council (AC) accepted >> "ARIN-prop-199 Resolve Conflict Between RSA and 8.2 Utilization >> Requirements" as a Draft Policy. >> >> Draft Policy ARIN-2014-9 is below and can be found at: >> https://www.arin.net/policy/proposals/2014_9.html >> >> You are encouraged to discuss the merits and your concerns of Draft >> Policy 2014-9 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-2014-9 >> Resolve Conflict Between RSA and 8.2 Utilization Requirements >> >> Date: 4 March 2014 >> >> Problem Statement: >> >> 8.2 transfer policy has utilization requirements at the time of the review >> of the transfer request. >> >> The RSA section 6 expressly forbids ARIN from de-registering blocks (in >> whole or in part) due to under-utilization or no-justification during >> transfer requests. >> >> This is a direct conflict. >> >> Return and aggregate are not done in collaboration; they are coerced by >> policy without the willing consent of the transfer parties. >> >> We should remove all utilization references from 8.2 language to ensure >> the policy is compliant with the RSA. >> >> Policy statement: >> >> Remove from 8.2: >> "In the event that number resources of the combined organizations are no >> longer justified under ARIN policy at the time ARIN becomes aware of the >> transaction, through a transfer request or otherwise, ARIN will work with >> the resource holder(s) to return, aggregate, transfer, or reclaim resources >> as needed to restore compliance via the processes outlined in current ARIN >> policy." >> >> Comments: >> a.Timetable for implementation: Immediate >> b.Anything else: >> >> >> >> >> >> _______________________________________________ >> 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. _______________________________________________ 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.
