<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Are you asking why the proposed policy doesn’t effect this change to current staff action, or are you asking why staff action didn’t change when they started accepting 8.2-based inter-RIR transfers without a policy change?<div class=""><br class=""></div><div class="">Owen</div><div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Sep 30, 2019, at 11:45 , David Farmer <<a href="mailto:farmer@umn.edu" class="">farmer@umn.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class="">I have a question regarding the Staff Understating of the policy from the Staff and Legal Assessment of the policy, which says the following; <br clear="all" class=""><div class=""><br class=""></div>Staff understands the intent of the draft policy is to clarify handling of mergers and acquisition transfer processing between RIRs who have compatible transfer policies. The proposed change would not be a change from present practice but the policy change would make our implementation of the current policy clearer. It is understood that IPv6 would be excluded since this refers to Inter-RIR transfers in which IPv6 is not permitted to be part of the transfer.</div><div dir="ltr" class=""><br class=""></div><div class="">Where the new policy text says;</div><div class=""><br class=""></div>When merger, acquisition, or reorganization activity results in surviving legal entity that is incorporated outside the ARIN service region, or focused outside the ARIN service region, or is merging with an organization that already has a relationship with another RIR, then resources may be moved to another RIR in accordance with the receiving RIR’s policies.</div><div dir="ltr" class=""><div class=""><br class=""></div><div class="">So my question is;</div><div class=""><br class=""></div><div class="">What in the new policy text justifies the exclusion of transfers of IPv6 resources for Inter-RiR M&A transfers? The new policy text doesn't directly reference section 8.4 which clearly doesn't include IPv6. However, nothing explicitly includes IPv6 in section 8.2 for the current Intra-region M&A transfers, so what excludes them for Inter-RIR M&A transfers?</div><div class=""><br class=""></div><div class="">While I agree a segment of the community doesn't want there to be inter-RIR M&A transfers of IPv6, I don't believe that is what this policy text says. If the community's intent is to clarify the status quo then and not allow inter-RIR M&A transfers of IPV6, then I believe there needs to be an explicit exclusion for IPv6 in Internet-RIR M&A transfers. Otherwise, I believe the text as written includes IPv6 inter-RIR M&A transfers.</div><div class=""><br class=""></div><div class="">I cannot support this policy as written, either the policy statement needs to be updated to explicitly exclude IPv6 from inter-RIR M&A or the staff understating needs to updated to include IPv6 for inter-RIR M&A, because as it stands, I believe the staff undressing and the policy text are inconsistent with each other.</div><div class=""><br class=""></div><div class="">Thank you. </div><div dir="ltr" class=""><br class=""></div><div dir="ltr" class="">-- <br class=""><div dir="ltr" class="gmail_signature">===============================================<br class="">David Farmer <a href="mailto:Email%3Afarmer@umn.edu" target="_blank" class="">Email:farmer@umn.edu</a><br class="">Networking & Telecommunication Services<br class="">Office of Information Technology<br class="">University of Minnesota <br class="">2218 University Ave SE Phone: 612-626-0815<br class="">Minneapolis, MN 55414-3029 Cell: 612-812-9952<br class="">=============================================== </div></div></div></div></div>
_______________________________________________<br class="">ARIN-PPML<br class="">You are receiving this message because you are subscribed to<br class="">the ARIN Public Policy Mailing List (<a href="mailto:ARIN-PPML@arin.net" class="">ARIN-PPML@arin.net</a>).<br class="">Unsubscribe or manage your mailing list subscription at:<br class=""><a href="https://lists.arin.net/mailman/listinfo/arin-ppml" class="">https://lists.arin.net/mailman/listinfo/arin-ppml</a><br class="">Please contact info@arin.net if you experience any issues.<br class=""></div></blockquote></div><br class=""></div></body></html>