<div dir="ltr">Jordi,<br><br>No problem, what I'm asking the community is if people support the use-cases you brought up. If they do, it seems like those use-cases need to be added to the problem statement. In my opinion, the current problem statement seems overly focused on the RPKI issue even to the point where it could be implying RPKI is the only reason you might want to transfer IPv6 resources to another region.<br><br>I'd propose the following rewrite of the problem statement;<br><br><blockquote style="margin:0 0 0 40px;border:none;padding:0px">There are operational reasons to allow transfers of IPv6 resources between RIRs with an equivalent transfer policy.<br> <br>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.<br><br>Apart from RPKI, an organization may wish to consolidate or manage the entirety of their resources, including IPv6, via a single RIR. For example, after acquiring an entity in another region or being acquired by an entity based in another region.<br><br>Or, an organization may wish to move its resources, including IPv6, to more accurately reflect where their resources are now in use. For example, if the organization is no longer operating within the ARIN region, it seems reasonable to move its resources to a region where they continue to operate.</blockquote><br><div dir="ltr"><div dir="ltr"><div dir="ltr"><div>Comments or suggestions, please.</div><div><br></div><div>Thanks</div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Mar 27, 2019 at 3:28 AM JORDI PALET MARTINEZ via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</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"><div lang="ES"><div class="m_-6037783478922324314gmail-m_-408116280212808513gmail-m_-3493981174514970092gmail-m_-7554962697085583753WordSection1"><p class="MsoNormal"><span class="m_-6037783478922324314gmail-m_-408116280212808513gmail-m_-3493981174514970092gmail-m_-7554962697085583753EstiloCorreo18"><span style="font-size:12pt">Hi David,<u></u><u></u></span></span></p><p class="MsoNormal"><span class="m_-6037783478922324314gmail-m_-408116280212808513gmail-m_-3493981174514970092gmail-m_-7554962697085583753EstiloCorreo18"><span style="font-size:12pt"><u></u> <u></u></span></span></p><p class="MsoNormal"><span class="m_-6037783478922324314gmail-m_-408116280212808513gmail-m_-3493981174514970092gmail-m_-7554962697085583753EstiloCorreo18"><span lang="EN-US" style="font-size:12pt">Sorry if somehow my input was “miss procedural” … the reason for that is because I’ve proposed an equivalent policy in several RIRs (in terms the final result: allowing IPv6 transfers), and this was one of the examples I’ve used.<u></u><u></u></span></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt">And just to make it clear, I also support the policy proposal for the reasons indicated in the actual proposal text.<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt">Here is a message about that with some other examples:<u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><a href="https://mailman.apnic.net/mailing-lists/sig-policy/archive/2019/03/msg00003.html" target="_blank"><span lang="EN-US">https://mailman.apnic.net/mailing-lists/sig-policy/archive/2019/03/msg00003.html</span></a><span lang="EN-US"><u></u><u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><div><p class="MsoNormal"><span lang="EN-US" style="font-size:10.5pt;color:black">Regarsds,<u></u><u></u></span></p><p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US" style="font-size:10.5pt;color:black">Jordi<u></u><u></u></span></p><p class="MsoNormal" style="margin-bottom:12pt"><span lang="EN-US" style="font-size:10.5pt;color:black"><u></u> <u></u></span></p></div><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><p class="MsoNormal"><span lang="EN-US" style="font-size:12pt"><u></u> <u></u></span></p><div><div><p class="MsoNormal" style="margin-left:35.4pt">El 27/3/19 2:40, "David Farmer" <<a href="mailto:farmer@umn.edu" target="_blank">farmer@umn.edu</a>> escribió:<u></u><u></u></p></div></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><div><div><div><p class="MsoNormal" style="margin-left:35.4pt">As one of the shepherds for this policy, beyond support for the policy as written, I'm interested to hear if there is support for the use case Jordi describes? <u></u><u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><div><p class="MsoNormal" style="margin-left:35.4pt">The use case Jordi describes seems meaningfully different than the use case described in the original problem statement. It seems plausible that there are resolutions, other than the transfer of IPv6, to the RPKI issues described in the current problem statement. However, for the use case that Jordi describes, some kind of the inter-RIR M&A transfer, the transfer of IPv6 resources seems like it could be reasonable, even if the RPKI issues are resolved by means other than this policy.<u></u><u></u></p></div></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><div><p class="MsoNormal" style="margin-left:35.4pt">So, should Jordi's use case be included in addition to the current problem statement?<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">Are there other use cases for the inter-RIR transfer of IPv6 resources that should be considered in the problem statement as well?<u></u><u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><div><p class="MsoNormal" style="margin-left:35.4pt">Thanks.<u></u><u></u></p></div></div><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div></div></div></div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p><div><div><p class="MsoNormal" style="margin-left:35.4pt">On Tue, Mar 26, 2019 at 4:46 PM JORDI PALET MARTINEZ via ARIN-PPML <<a href="mailto:arin-ppml@arin.net" target="_blank">arin-ppml@arin.net</a>> wrote:<u></u><u></u></p></div><blockquote style="border-top:none;border-right:none;border-bottom:none;border-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm"><p class="MsoNormal" style="margin-left:35.4pt">In favor of the proposal.<br><br>My point of view is on the other way around.<br><br>This policy is needed, because if there is a company under an M&A or reorganization, it seems clear that then it is transferred IPv4, IPv6, ASN. But there may be cases where is not entirely failing into that category.<br><br>For example, a "relocation". A company having VMs in data centers, in Europe (with resources from RIPE NCC) and moving to US (for whatever reasons). I don't expect they will renumber the VMs, they will just copy & synchronize the VMs and switch off the old VMs.<br><br>It will not make sense to tell them "you can transfer" your IPv4 resources, but you need to renumber IPv6.<br><br>There may be other cases which similar needs.<br><br>Regards,<br>Jordi<br><br><br><br>El 26/3/19 22:35, "ARIN-PPML en nombre de John Santos" <<a href="mailto:arin-ppml-bounces@arin.net" target="_blank">arin-ppml-bounces@arin.net</a> en nombre de <a href="mailto:john@egh.com" target="_blank">john@egh.com</a>> escribió:<br><br><br> On 3/26/2019 3:52 PM, ARIN wrote:<br> > There is an operational need to allow RIR transfers of IPv6 resources <br> > between RIRs with an equivalent transfer policy. ARIN’s RPKI Trust <br> > Anchor (TA) is measurably less widely deployed than TAs from other <br> > RIRs. As a consequence, RPKI ROAs published through ARIN offer less <br> > value. Operators seeking to extract the most value from their <br> > investment in IPv6 would benefit from the ability to transfer IPv6 <br> > resources to RIRs with more widely deployed RPKI Trust Anchors.<br> Wouldn't it make more sense to increase the deployment of RPKI in the <br> ARIN region than to open this can of worms?<br><br> -- <br> John Santos<br> Evans Griffiths & Hart, Inc.<br> 781-861-0670 ext 539<br><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" 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><br><br><br><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br><a href="http://www.theipv6company.com" target="_blank">http://www.theipv6company.com</a><br>The IPv6 Company<br><br>This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br><br><br><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" 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.<u></u><u></u></p></blockquote></div><p class="MsoNormal" style="margin-left:35.4pt"><br clear="all"><u></u><u></u></p><div><p class="MsoNormal" style="margin-left:35.4pt"><u></u> <u></u></p></div><p class="MsoNormal" style="margin-left:35.4pt">-- <u></u><u></u></p><div><p class="MsoNormal" style="margin-left:35.4pt">===============================================<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>=============================================== <u></u><u></u></p></div></div><br>**********************************************<br>IPv4 is over<br>Are you ready for the new Internet ?<br>
<a href="http://www.theipv6company.com" target="_blank">http://www.theipv6company.com</a><br>The IPv6 Company<br>
<br>This electronic message contains information which may be privileged or confidential. The information is intended to be for the exclusive use of the individual(s) named above and further non-explicilty authorized disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited and will be considered a criminal offense. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, even if partially, including attached files, is strictly prohibited, will be considered a criminal offense, so you must reply to the original sender to inform about this communication and delete it.<br>
<br>
</div>_______________________________________________<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_-6037783478922324314gmail-m_-408116280212808513gmail-m_-3493981174514970092gmail_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></div></div></div>