This policy seems to have been overrun by events, the discussion by the community regarding the general issues involved in this policy seems to have moved to ARIN-2019-10: Inter-RIR M&A; https://www.arin.net/participate/policy/drafts/2019_10/
ARIN-2019-10 seem to have a better formulation of the issues involved. However, if you think this policy has a better formulation of the issues involved in the discussion between this policy and ARIN-2019-10, please explain why and the AC will consider your arguments. Otherwise, in order to help simplify and focus the discussion on ARIN-2019-10 at the upcoming ARIN 44 meeting, in my role as an AC shepherd for this policy, I plan to make a motion to abandon this policy on the next Advisory Council call. Your feedback is appreciated. Thank you. On Tue, Mar 26, 2019 at 2:52 PM ARIN <[email protected]> wrote: > On 21 March 2019, the ARIN Advisory Council (AC) accepted > "ARIN-prop-263: Allow Inter-regional IPv6 Resource Transfers" as a Draft > Policy. > > The Draft Policy text is below and can be found at: > https://www.arin.net/participate/policy/drafts/2019_4/ > > You are encouraged to discuss all Draft Policies on PPML. 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 Policy Development Process (PDP). Specifically, these > principles are: > > * Enabling Fair and Impartial Number Resource Administration > * Technically Sound > * Supported by the Community > > The PDP can be found at: > https://www.arin.net/participate/policy/pdp/ > > Draft Policies and Proposals under discussion can be found at: > https://www.arin.net/participate/policy/drafts/ > > Regards, > > Sean Hopkins > Policy Analyst > American Registry for Internet Numbers (ARIN) > > > > Draft Policy ARIN-2019-4: Allow Inter-regional IPv6 Resource Transfers > > Problem Statement: > > There is an operational need to allow RIR transfers of IPv6 resources > between RIRs with an equivalent transfer policy. ARIN’s RPKI Trust > Anchor (TA) is measurably less widely deployed than TAs from other RIRs. > As a consequence, RPKI ROAs published through ARIN offer less value. > Operators seeking to extract the most value from their investment in > IPv6 would benefit from the ability to transfer IPv6 resources to RIRs > with more widely deployed RPKI Trust Anchors. > > Policy Statement: > > Change the first sentence in section 8.4 from: > > “Inter-regional transfers of IPv4 number resources and ASNs may take > place only via RIRs who agree to the transfer and share reciprocal, > compatible needs-based policies.” > > To: > > “Inter-regional transfers of Internet number resources may take place > only via RIRs who agree to the transfer and share reciprocal, compatible > needs-based policies.” > > Comments: > > Timetable for implementation: Immediate > _______________________________________________ > ARIN-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: > https://lists.arin.net/mailman/listinfo/arin-ppml > Please contact [email protected] if you experience any issues. > -- =============================================== David Farmer Email:[email protected] Networking & Telecommunication Services Office of Information Technology University of Minnesota 2218 University Ave SE Phone: 612-626-0815 Minneapolis, MN 55414-3029 Cell: 612-812-9952 ===============================================
_______________________________________________ ARIN-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: https://lists.arin.net/mailman/listinfo/arin-ppml Please contact [email protected] if you experience any issues.
