Search RPD Archives
[rpd] new version of policy proposal AFPUB-2019-IPv4-002-DRAFT02
owen at delong.com
Thu Nov 7 17:52:22 UTC 2019
Comments on specific sections:
First, this policy should apply to all organizations with justified needs. There’s no reason
to exclude organizations who could get resources from AfriNIC from using the transfer
policy if they so choose. Further, the application should be to both recipient organizations
(as stated) and source organizations (excluded by present language).
Recommended alternate language:
This policy applies to organizations with a justified need for IPv4 resources
(recipients) and organizations with IPv4 resources that are no longer needed by
the organization (sources).
Policy should set source criteria only if the source is within the AfriNIC region. Source
criteria for sources outside of AfriNIC should be set by the source RIR. Further, a
source organization should not be permanently barred from acquiring additional
resources, so I have added a suggestion to allow them to acquire resources via
transfer 24 months after acting as a source.
Recommended alternate language:
5.7.2 — as is
188.8.131.52 A source must be validated by the applicable source RIR according to their
policies and procedures. A source within the AfriNIC region must be in good
standing (all invoices paid) and must be the rightful registrant of the resources
to be transferred and there must be no dispute as to the status of said resources.
184.108.40.206 Source entities will not be eligible to receive any further IPv4 address allocations
or assignments from AfriNIC. Source entities may, if they can show justified
need receive resources via transfer after a period of not less than 24 months
has elapsed from their last outbound transfer.
220.127.116.11 An organization which has received resources in the AfriNIC registry within the
preceding twelve months will not be approved as a transfer source.
18.104.22.168 is a bit vaguely worded. Suggest:
22.214.171.124 Recipient organizations within the AfriNIC service region must be approved
by AfriNIC staff using the same policies and procedures as if the request
were being satisfied from the AfriNIC free pool.
126.96.36.199 is also a bit convoluted. Suggest:
188.8.131.52 Recipients in other RIRs must be approved by the staff in that RIR according
to that RIR’s policies and procedures.
184.108.40.206 is unnecessary and incorrect in some cases. Many organizations that receive
resources in the ARIN region are not members, for example. Any intended effect
in 220.127.116.11 is a subset of the requirements already expressed in 18.104.22.168 and I presume
that the unintended effects do not need to be preserved. Suggest striking 22.214.171.124
5.7.4 — I think there is a better way to express the actual intent here… Suggest:
5.7.4 Transfer of ASN with resources
In the case where the majority of an operating network, including the
addresses and the physical infrastructure are being transferred, any
applicable ASN(s) may also be transferred at the same time in order
to preserve operational integrity and expedience.
5.7.5 — This doesn’t belong in the policy text and should be provided instead as
guidance to the board and staff for scheduled implementation of the policy.
Leaving this in the policy text results in a policy manual which contains an
ever growing set of anachronisms.
5.7.6 Who determines what information is or is not confidential? Policy should
specify exactly what is required to be disclosed and if it wishes to make
additional disclosures optional, it should state what those are and that
they should be published if disclosed. The list in the existing proposal
is a good start on the minimum mandatory information. If we want that
as the extent of the policy, suggested rewording:
5.7.6 Required Disclosures for Transfers
Parties shall be required to disclose and AfriNIC shall publish
in a specific location, a history of all completed transfers including
at least the following information about each transfer:
+ Date of the Transfer
+ Identification/description of the Resources Transferred (e.g. 192.168.48.0/20, AS3223959)
+ Source RIR
+ Source ORG-ID
+ Recipient RIR
+ Recipient ORG-ID
> On Nov 7, 2019, at 07:50 , JORDI PALET MARTINEZ via RPD <rpd at afrinic.net> wrote:
> Hi all,
> As I've indicated last Monday, during the weekend I've updated the policy proposal AFPUB-2019-IPv4-002-DRAFT02 "IPv4 Inter-RIR Resource Transfers (Comprehensive Scope)" and I'm attaching it here in PDF, so all can read even if not yet published in the website.
> This update tries to address:
> 1) All the issues and inputs from the RPD List and the previous meeting.
> 2) The staff impact analysis.
> At the same time, as it was clear that the community is not interested in a "legacy" only policy proposal (I also expressed myself my concern about that during the meeting, but I wanted to offer "both" choices, just in case), I'm formally withdrawing the proposal AFPUB-2019-IPv4-001-DRAFT01 "IPv4 Inter-RIR Legacy Resource Transfers".
> Thanks in advance for reading and contributing!
> IPv4 is over
> Are you ready for the new Internet ?
> 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.
> RPD mailing list
> RPD at afrinic.net
More information about the RPD