Dear Colleagues, I am Satoru Tsurumaki from Japan Open Policy Forum Steering Team.
I would like to share key feedback in our community for prop-147, based on a meeting we organised on 15th Feb to discuss these proposals. Almost Japanese community members were expressed in favor of this proposal. (comment details) - I favor with this proposal, including the 12-month claim acceptance period. Regards, Satoru Tsurumaki / JPOPF Steering Team 2023年1月20日(金) 9:21 Bertrand Cherrier <[email protected]>: > > Dear SIG members, > > A new version of the proposal "prop-147: Historical Resources Management" > has been sent to the Policy SIG for review. > > It will be presented at the Open Policy Meeting (OPM) at APNIC 55 on > Wednesday, 1 March 2023. > > https://conference.apnic.net/55/program/schedule/#/day/10 > > We invite you to review and comment on the proposal on the mailing list > before the OPM. > > The comment period on the mailing list before the OPM is an important > part of the Policy Development Process (PDP). 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 appended below as well as available at: > > http://www.apnic.net/policy/proposals/prop-147 > > Regards, > Bertrand, Shaila, and Anupam > APNIC Policy SIG Chairs > > > --------------------------------------------------------------- > > prop-147-v003: Historical Resources Management > > ---------------------------------------------------------------- > > Proposer: Jordi Palet Martinez ([email protected]) > > > 1. Problem statement > -------------------- > Section 4.2.1 is outdated and only looking for very old non-routed > resources. > > The recent EC resolution (22nd February 2022), imply that historical > resource holders in the APNIC region would need to become Members or > Non-Members by 1st January 2023 in order to continue to receive > registration services. Failing this, historical resource registration > will no longer be published in the APNIC Whois Database and said > resources will be placed into reserved status. > > Per current policies, all current and historical resources that are > marked as reserved are automatically added to the AS0. > > Given the continued need for IPv4 addresses, it would seem illogical to > keep these unused historical resources in reserve indefinitely. > Alternatively, these resources can be used in a way that is sufficiently > justified in accordance with existing policies, allowing other > organizations to benefit from them during the IPv6 transition. > > > 2. Objective of policy change > ----------------------------- > Ensure that historical IPv4 resources are justified and claimed, or that > they are available for other organizations that require them. > > If the resources are marked as reserved, the original holders may > reclaim them with a valid justification, when APNIC failed to contact > them for whatever reason. > > One example of a valid justification is the case where an organization > is actually using them internally and there are valid reasons to instead > use RFC1918 space, however the space is not routed. > > To give the original resource holders more time to reclaim them, and > ensure that APNIC has no challenges in finalizing the work, we propose a > time-frame of 12 months. > > > 3. Situation in other regions > ----------------------------- > In other RIRs legacy resources lose their legacy status when the RSA is > signed (upon receiving other resources), so they become under the > regular monitoring. In other cases, there is nothing specified by policies. > > > 4. Proposed policy solution > --------------------------- > REMOVE: > 4.2.1. Recovery of unused historical resources > > To recover these globally un-routed resources and place them back in the > free pool for re-delegation, APNIC will contact networks responsible for > historical address space in the APNIC region that has not been globally > routed since 1 January 1998. To recover un-routed historical AS numbers, > APNIC will contact networks responsible for resources not globally used > for a reasonable period of time. > > ADD: > > 4.3. Historical Resources Management > > a) Historical resources currently marked as reserved. > The custodians can claim historical resources that have been marked as > reserved within 12 months of the date they were marked as reserved. > After 12 months, these resources will be placed in the free pool for > re-delegation. > > If the resources are no longer required and are returned to APNIC, they > can’t be reclaimed. > > b) Routed and Unrouted historical resources. > When APNIC deregisters an unclaimed historical resource, it is marked as > reserved. The custodians will be given another 12 months to claim their > resources. If the resources haven’t been claimed after 12 months, they > will be placed in the free pool for re-delegation. > > c) Account closures. > Any historical resources marked as reserved and/or reclaimed by APNIC > due to account closures will lose their “historical” status and become > “current” resources for re-delegation. > > > 5. Advantages / Disadvantages > ----------------------------- > Advantages: > Fulfilling the objective above indicated by allowing further 12 months > for reclaiming the historical resources. > Returning resources to RIR for reallocation providing additional number > of IPv4 resources to be allocated in the future. > > Disadvantages: > None. > > > 6. Impact on resource holders > ----------------------------- > None. > > > 7. References > ------------- > None. > > > _______________________________________________ > sig-policy - https://mailman.apnic.net/[email protected]/ > To unsubscribe send an email to [email protected] _______________________________________________ sig-policy - https://mailman.apnic.net/[email protected]/ To unsubscribe send an email to [email protected]
