Search RPD Archives
Limit search to: Subject & Body Subject Author
Sort by:

[rpd] Implementation of transfer policy AFPUB-2016-V4-003

Alan Barrett alan.barrett at
Wed Aug 16 14:50:08 UTC 2017

Dear community,

As you are aware, the policy proposal AFPUB-2016-V4-003-DRAFT03
"IPv4 Resources transfer within the AFRINIC Region” was ratified by
the Board on 19 April 2017.

In-line with article 3.4.5 of the Consolidated Policy Manual, a ratified policy proposal should usually be implemented within 6 months after the end of last call -  which is 16 August 2017 (6 months after the last call date of 16 Feb 2017).

AFRINIC staff have requested an extension until 31 October 2017, and the Board has approved the extension.

Implementing this policy requires at least the following work:

## RSA modifications

The existing Registration Service agreement (RSA) prohibits transfer of address space. A revised RSA addressing this and other small issues is being drafted and will shared with the community soon.

## Transfer Agreement

Staff have recommended that a new Transfer Agreement document be prepared.  It will establish the conditions of the transfer provide for handling any dispute regarding a resource transfer.  We envisage a document signed by both the source and recipient organisations.

## Authentication of requests from legacy resource holders

We anticipate that legacy address space may be the subject of a transfer.  Legacy resource holders are often not members of AFRINIC, and legacy address space has a higher than averge risk of being used by unauthorised parties (“hijacked”).  AFRINIC will have to develop due diligence processes to verify that any requests for transfers of legacy address space are legitimate.

## Automation of error-prone tasks

Transfers will often require an address block (“prefix”) to be sub-divided into several smaller blocks, with some of the smaller blocks being transferred and some remaining with the previous holder.  This will require complex and error-prone changes to the WHOIS and related databases.  The transfer policy also imposes requirements that the source organisation must not have received address space from AFRINIC in the past 12 months, and will not be eligible to receive address space for the next 12 months. Enforcing such requirements manually will be error-prone.  Software will be developed to help with the complex tasks.

## New member registration portal (NMRP)

The web portal that new members use to apply for membership and apply for their first resource allocation or assignment will need to be updated, to allow for the possibility that the first allocation or assignment is the result of a transfer.

## Process review

Several internal processes used by the Registration Services team will need to be updated.

## Documentation and training materials

At least the following materials will need to be updated:

* Training material for INRM (Internet number resource management)
* “How to” guides
* The consolidated policy manual
* Policy interpretation guides
* Web pages relating to resource applications


Alan Barrett

More information about the RPD mailing list