<div dir="ltr"><div dir="ltr">Thanks for clarifying the policy you were referring to.<div><br></div><div>In ARIN Transfer Policy there are significant differences between IPv4, ASNs, and IPv6, are you suggesting all these differences should be eliminated? Or are you suggesting an equivalent mechanism to transfer IPv6 resources inter-regionally is needed to the one that exists for transferring IPv6 within the ARIN region? </div><div><br></div><div>Currently, ARIN Transfer Policy allows;</div><div><br></div><div>A. All resource types to be transferred within the ARIN region as part of a Merger, Acquisition, or Reorganization (Section 8.2).</div><div><br></div><div>B. Only IPv4 and ASNs to be transferred to unrelated organizations (a designated organization) within the region or to another region (Sections 8.3, 8.4, and 8.5).</div><div><br></div><div>Option A has been the case for a long time, whereas option B is more recent and mostly a result of IPv4 runout and the approaching runout of 16-bit ASNs. Further, there are differences in how a transfer is justified between the two options; in option A, legal documentation justifies the transfer, whereas in option B the need of the recipient organization justifies the transfer. </div><div><br></div><div>There are two different ways to modify the current policy to accomplish inter-regional transfers of IPv6 resource; </div><div><br></div><div>1. Modify option A above to include inter-regional transfers.</div><div>2. Modify option B above to include IPv6.</div><div><br></div><div>By my read of the community, there are strong objections to option #2, expanding option B to include IPv6. Whereas there seems to be some acknowledgment that option #1, expanding Option A to include transfers to other regions, could be reasonable.</div><div><br></div><div>Put another way, the greatest objections seems to be allowing IPv6 transfers to unrelated organizations either within the region or to other regions, and far fewer objections to allowing IPv6 transfers to related organizations in another region.</div><div><br></div><div>I think for the community to evaluate these two options it needs to understand the use-cases people have for inter-region IPv6 transfers. The use-cases brought up by Jordi and the problem statement seems to fall within expanding option A to include inter-region transfers. So unless someone else has use-cases that need option B to be expanded to include IPv6, then expanding option A to include inter-region transfers seems less controversial and more likely to gain consensus.</div><div><br></div><div><div>So looking for what seems possible; I suggest we focus on option #1, expanding option A to include inter-region transfers, rather than option #2, expanding option B to include IPv6.</div></div><div><br></div><div>Comments and suggestions, please.</div><div><br></div><div><br></div></div><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Apr 3, 2019 at 3:33 PM Tal, Guy <<a href="mailto:guy.tal@centurylink.com" target="_blank">guy.tal@centurylink.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">What's the difference between an ipv4 address and an ipv6 address (other than a couple of bits)?<br>
<br>Guy<br>
<br>-----Original Message-----<br>From: Steven Ryerse <<a href="mailto:SRyerse@eclipse-networks.com" target="_blank">SRyerse@eclipse-networks.com</a>><br>Sent: Wednesday, April 3, 2019 1:15 PM<br>To: Tal, Guy <<a href="mailto:guy.tal@level3.com" target="_blank">guy.tal@level3.com</a>>; ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>>; <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>Subject: RE: [arin-ppml] Draft Policy ARIN-2019-4: Allow Inter-regional IPv6 Resource Transfers<br>
<br>Although I agree conceptually, I'm not sure its practical to have all policies apply to both IP4 & IP6. They are different and the differences require polices that cover the differences.<br>
<br>
<br>Steven Ryerse<br>President<br>100 Ashford Center North, Suite 110, Atlanta, GA 30338<br>770.656.1460 - Cell<br>770.399.9099 - Office<br>770.392.0076 - Fax<br>
<br>℠ Eclipse Networks, Inc.<br> Conquering Complex Networks℠<br>
<br>-----Original Message-----<br>From: ARIN-PPML <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a>> On Behalf Of Tal, Guy<br>Sent: Wednesday, April 3, 2019 3:47 PM<br>To: ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>>; <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>Subject: Re: [arin-ppml] Draft Policy ARIN-2019-4: Allow Inter-regional IPv6 Resource Transfers<br>
<br>Sorry all, this is the thread I meant to throw my support behind, not ARIN-2018-5. I think we should treat v6 the same as v4, resource is resource.<br>
<br>Thanks,<br>Guy<br>
<br>-----Original Message-----<br>From: ARIN <<a href="mailto:info@arin.net" target="_blank">info@arin.net</a>><br>Sent: Tuesday, March 26, 2019 12:52 PM<br>To: <a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a><br>Subject: [arin-ppml] Draft Policy ARIN-2019-4: Allow Inter-regional IPv6 Resource Transfers<br>
<br>On 21 March 2019, the ARIN Advisory Council (AC) accepted<br>"ARIN-prop-263: Allow Inter-regional IPv6 Resource Transfers" as a Draft Policy.<br>
<br>The Draft Policy text is below and can be found at:<br>
<a href="https://www.arin.net/participate/policy/drafts/2019_4/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/2019_4/</a><br>
<br>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:<br>
<br>* Enabling Fair and Impartial Number Resource Administration<br>* Technically Sound<br>* Supported by the Community<br>
<br>The PDP can be found at:<br>
<a href="https://www.arin.net/participate/policy/pdp/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/pdp/</a><br>
<br>Draft Policies and Proposals under discussion can be found at:<br>
<a href="https://www.arin.net/participate/policy/drafts/" rel="noreferrer" target="_blank">https://www.arin.net/participate/policy/drafts/</a><br>
<br>Regards,<br>
<br>Sean Hopkins<br>Policy Analyst<br>American Registry for Internet Numbers (ARIN)<br>
<br>
<br>
<br>Draft Policy ARIN-2019-4: Allow Inter-regional IPv6 Resource Transfers<br>
<br>Problem Statement:<br>
<br>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.<br>As a consequence, RPKI ROAs published through ARIN offer less value.<br>Operators seeking to extract the most value from their investment in<br>IPv6 would benefit from the ability to transfer IPv6 resources to RIRs with more widely deployed RPKI Trust Anchors.<br>
<br>Policy Statement:<br>
<br>Change the first sentence in section 8.4 from:<br>
<br>“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.”<br>
<br>To:<br>
<br>“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.”<br>
<br>Comments:<br>
<br>Timetable for implementation: Immediate<br>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.<br>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.<br>_______________________________________________<br>ARIN-PPML<br>You are receiving this message because you are subscribed to<br>the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" target="_blank">ARIN-PPML@arin.net</a>).<br>Unsubscribe or manage your mailing list subscription at:<br>
<a href="https://lists.arin.net/mailman/listinfo/arin-ppml" rel="noreferrer" target="_blank">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br>Please contact <a href="mailto:info@arin.net" target="_blank">info@arin.net</a> if you experience any issues.<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="m_-6346617383134389985gmail-m_-4379435061001962305gmail_signature">===============================================<br>David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank">Email:farmer@umn.edu</a><br>Networking & Telecommunication Services<br>Office of Information Technology<br>University of Minnesota <br>2218 University Ave SE Phone: 612-626-0815<br>Minneapolis, MN 55414-3029 Cell: 612-812-9952<br>===============================================</div>
</div>