Hi Sunny, all, I fully understand the difficulties that you mention, but those difficulties, to me look like the same as per existing policy.
Any transfer requires checking documents, which may be in different languages. Any transfer requires coordination among NIRs or RIRs, etc. So, I do not see it as different to what it happened with previous transfer policies (whatever is the reason). Of course, I also fully understand that the implementation time depends on coordination with the other RIRs and their systems, but this is also true for existing Inter-RIR policies. Just want to make sure that I'm not missing anything and your assessment is just a reminder about that, not indicating any real and unsolvable issues. Regards, Jordi @jordipalet El 17/2/21 7:04, "Srinivas (Sunny) Chendi" <[email protected] en nombre de [email protected]> escribió: Dear all, Here is the Secretariat impact assessment for proposal "prop-130-v003: Modification of transfer policies". Possible difficulties in verifying mergers, acquisition, reorganization, or relocation from out of APNIC region due to unfamiliarity of languages and legal systems. May require cross RIR coordination. Partial IPv6 transfers may result in registration of IPv6 allocations that are more specific than /32. APNIC’s current systems are not configured to handle inter-RIR IPv6 reverse DNS. This will need to be developed. APNIC cannot predict when other RIRs will support IPv6 reverse DNS fragments incoming to their systems. Implementation: 3 months, except inter-RIR IPv6 reverse DNS (rDNS). Regards Sunny On 2/02/2021 2:25 pm, chku wrote: > Dear SIG members, > > A new version of the proposal "prop-130: Modification of transfer policies" > has been sent to the Policy SIG for review. > > It will be presented during the Open Policy Meeting at APRICOT2021/APNIC 51 > online-only conference on Wednesday, 03 February 2021. > > We invite you to review and comment on the proposal on the mailing list > before the meeting. > > The comment period on the mailing list before an APNIC conference is an > important part of the policy development process. We encourage you to > express your views on the proposal: > > - Do you support or oppose this proposal? > - Does this proposal solve a problem you are experiencing? If so, > tell the community about your situation. > - Do you see any disadvantages in this proposal? > - Is there anything in the proposal that is not clear? > - What changes could be made to this proposal to make it more > effective? > > Information about this proposal is available at: > https://aus01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apnic.net%2Fpolicy%2Fproposals%2Fprop-130&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=CsjZK2dQEUNWNP6Z5zdhzNiiZzC0sXfCesvMgnEbye4%3D&reserved=0 > > Regards, > Bertrand and Ching-Heng > APNIC Policy SIG Chairs > > > ------------------------------------------------------- > > prop-130-v003: Modification of transfer policies > > ------------------------------------------------------- > > Proposer: Jordi Palet Martnez > [email protected] > > > 1. Problem statement > -------------------- > > Existing transfer policies for IPv4, IPv6 and ASN resources have some > differences among what is allowed and what not, if in the case of > intra-RIR and inter-RIR, and it is not clear if in case of merger and > acquisitions it is referring to a complete company, part of it, or even > if in case of a company reorganization or relocation, the policy is > supportive to that case. > > In some regions, this may not be a policy, but an administrative > procedure, but this may change in the future by means of a policy proposal. > > In the caser of inter-RIR, the counterpart RIR need to have a reciprocal > policy or procedure that allows it. > > Finally, there should not be differences from the APNIC perspective, on > the considerations of an M&A for different type of resources, because > there is no reason for allowing, for example, IPv4 resources to be > transferred, and instead IPv6 ones not. For example, an organization may > be hosting services in a Data Center, by means of Virtual Machines and > moving to a different DC in another region. It is ridiculous to allow to > keep the IPv4 addresses (so not renumber the VMs) and instead ask to > renumber IPv6. It is a big and unnecessary disruptive complexity. > > > 2. Objective of policy change > ------------------------------ > To ensure that the policy text is clarified, if those cases are > supported by the community. > > It will also facilitate companies or business units, moving or being > established in other regions. > > It will minimize legal issues in case an acquisition claiming their > rights over the acquired company and their existing assets (resources). > > > 3. Situation in other regions > ------------------------------ > There is a variety of support of all those cases in different regions. > The one more open is RIPE, followed by ARIN and LACNIC. A similar policy > proposal is being discussed in AFRINIC. > > > 4. Proposed policy solution > ---------------------------- > Actual Text > 8.4. Mergers & acquisitions > APNIC will process and record the transfer of IPv4 resources as the > result of merger or acquisition. > > 11.0. Transfer of IPv6 resources > APNIC will only recognize the transfer or IPv6 addresses as the result > of Merger & Acquisition activity. The following conditions and > consequences apply. > > 13.3. Mergers & acquisitions > APNIC will recognize the transfer of ASNs as the result of merger or > acquisition. > > > Proposed Text > 8.4. Mergers, acquisitions and relocations > APNIC will recognize the transfer of IPv4 resources resulting from a > partial or complete merger, acquisition, reorganization or relocation. > > In the case of inter-RIR, the counterpart RIR need to have a reciprocal > policy/procedure that allows it. > > > 11.0. Transfer of IPv6 resources > APNIC will recognize the transfer or IPv6 resources resulting from a > partial or complete merger, acquisition, reorganization or relocation. > > In the case of inter-RIR, the counterpart RIR need to have a reciprocal > policy/procedure that allows it. > > > 13.3. Mergers, acquisitions and relocations > APNIC will recognize the transfer of ASNs resulting from a partial or > complete merger, acquisition, reorganization or relocation. > > In the case of inter-RIR, the counterpart RIR need to have a reciprocal > policy/procedure that allows it. > > > 5. Advantages / Disadvantages > ----------------------------- > Advantages: > Fulfilling the objectives above indicated and ensuring clarity on what > is allowed and what not. > > The proposal makes clear that this may only happen, in case of Inter-RIR > cases, when both RIRs have a reciprocal policy. > > Minimizing possible legal issues. > > > Disadvantages: > It could be considered that it can create further disaggregation, > especially in IPv6, however, those cases are rare and only happening > from time to time, so the impact is negligible, and justified by the > documentation provided when the transfer is requested. > > In the Inter-RIR cases, coordination with the counter-part RIR is > needed, but this is already an ongoing activity because all the regions > (with the exception of AFRINIC), already have those mechanisms in place > (for both, administrative and technical aspects). > > > 6. Impact on resource holders > ------------------------------ > None. > > > 7. References > -------------- > RIPE NCC: > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.ripe.net%2Fpublications%2Fdocs%2Fripe-682&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=JAbtrqd3xeoSGq5DdUVH%2BnO7or0cnTm%2FEJwtJhUhU20%3D&reserved=0 > > ARIN: > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.arin.net%2Fpolicy%2Fnrpm.html%23eight2&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=EdnQQbJOHozySGwTM%2Be86nap0MqoZnMCWXBgfhAzt58%3D&reserved=0 > > LACNIC: > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpoliticas.lacnic.net%2Fpoliticas%2Fdetail%2Fid%2FLAC-2019-4%2Flanguage%2Fen&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=Cmk0xriAuykrCI%2FPiU3rs%2Fiy%2BmQNarXaw4kgJPETcDA%3D&reserved=0 > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpoliticas.lacnic.net%2Fpoliticas%2Fdetail%2Fid%2FLAC-2019-3%2Flanguage%2Fen&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=17c7U5lQoRRLw80b76qfuixiNwHw4wwS9Sh5yLa9DT8%3D&reserved=0 > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpoliticas.lacnic.net%2Fpoliticas%2Fdetail%2Fid%2FLAC-2019-2%2Flanguage%2Fen&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=avvN5mBY1IMZtAFl3ks0Svvc1e6dz1u7GiLLcoJznN4%3D&reserved=0 > _______________________________________________ > * sig-policy: APNIC SIG on resource management policy * > _______________________________________________ > sig-policy mailing list > [email protected] > https://aus01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fmailman.apnic.net%2Fmailman%2Flistinfo%2Fsig-policy&data=04%7C01%7C%7C4fa1eb6f23ac419a95e508d8c7329f44%7C127d8d0d7ccf473dab096e44ad752ded%7C0%7C0%7C637478367555653423%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C1000&sdata=0CJgHiZp3aCM7bUAhT3BPLHSULwEKpcH1BouBAAR5MQ%3D&reserved=0 * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/sig-policy ********************************************** IPv4 is over Are you ready for the new Internet ? http://www.theipv6company.com The IPv6 Company 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. * sig-policy: APNIC SIG on resource management policy * _______________________________________________ sig-policy mailing list [email protected] https://mailman.apnic.net/mailman/listinfo/sig-policy
