Dear APNIC SIG-POLICY,

Hopefully this email finds you in good health!

Please see my comments below, inline...
Thanks.

Le jeudi 11 août 2022, chku <[email protected]> a écrit :

> Dear SIG members,
>
>
>

Hi Chku,
Thanks for your email.



>
> 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 54 on
> Thursday, 15 September 2022.
>
>     https://conference.apnic.net/54/program/schedule/#/day/8
>
> We invite you to review and comment on the proposal on the mailing list
> before the OPM.
>
>
>

...i went through the version 002 [1] of this policy
proposal and i picked the following part of text:

"Proposed text:

[Remove] Section 4.2.1 Recovery of unused historical resources

[Add] Section 4.3. Historical Resources Management

Historical resources that have not been claimed by the custodian will be
deleted from the APNIC Whois database after 1st January 2023, and marked as
reserved.

Historical resources marked as reserved have an additional twelve (12)
months to be claimed by their custodians. After that, APNIC will add these
resources to the free pool for re-delegation.

Furthermore, from 1st January 2023, all historical resources need to be
maintained in a current APNIC account. In the event of an account closure,
the historical resource will be placed in a quarantine period and then made
available for re-delegation similar to current resources."
__
[1]:
https://www.apnic.net/wp-content/uploads/2022/08/prop-147-v002.txt#:~:text=Proposed%20text%3A%0A%0A%5BRemove,to%20current%20resources
.



>
>
> 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:
>
>
>

Having read various interesting comments too, i suggest to add the
following additional text, in
order to "try" to address the concerns raised:

-.-
|1. Three months after started the campaign to
uniformize historical INRs, all those resources not yet successfully
claimed shall be tagged as "under uniformization";
|2. Any resource tagged "under uniformization" are
untagged when successfully claimed by its right
custodian;
|3. After one year AS0 ROAs are create for all resources still tagged
"under uniformization"
|4. Former custodian (with evidence) of any
historical INR resource assignment failed under
quarantine shall be prioritised if they suddently
request (before it has been already all allocated /
assigned) the INRs they was not able to
successfully claim holdering at time before.
|5. ...
_._



Shalom,
--sb.



>
>
>   - 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 Ching-Heng
> APNIC Policy SIG Chairs
>
>
>
> ---------------------------------------------------------------
>
> prop-147-v001: Historical Resources Management
>
> ----------------------------------------------------------------
>
> Proposer: Jordi Palet Martinez ([email protected])
>           Anupam Agrawal ([email protected])
>
> [...]
>
>

-- 

Best Regards !
__
baya.sylvain[AT cmNOG DOT cm]|<https://cmnog.cm/dokuwiki/Structure>
Subscribe to Mailing List: <https://lists.cmnog.cm/mailman/listinfo/cmnog/>
__
#‎LASAINTEBIBLE‬|#‎Romains15‬:33«Que LE ‪#‎DIEU‬ de ‪#‎Paix‬ soit avec vous
tous! ‪#‎Amen‬!»
‪#‎MaPrière‬ est que tu naisses de nouveau. #Chrétiennement‬
«Comme une biche soupire après des courants d’eau, ainsi mon âme soupire
après TOI, ô DIEU!»(#Psaumes42:2)
_______________________________________________
sig-policy - https://mailman.apnic.net/[email protected]/
To unsubscribe send an email to [email protected]

Reply via email to