Clarification on temporary resource usage v2

Current

Proposed

9.0  Temporary Resource Allocations & Assignments

9.0 Temporary Resource Assignments

9.1 Documenting the temporary activity

The activity requiring temporary IP resources should be publicly documented and available, preferably on a website. Entities requiring such IP resources are expected to demonstrate an understanding that when the activity or experiment for which they require the IP resources ends, the IP resources will be returned to AFRINIC.

A "publicly accessible document" is a document that is publicly and openly available free of charge and free of any constraints of disclosure.

AFRINIC will not recognize any activity under this policy if such an activity cannot be publicly disclosed.

9.1 Documenting the temporary activity

The activity requiring temporary IP resources should be publicly documented and available on a website reachable at least from the time of submission of the resource request and during the entire period of the event. A "publicly accessible document" is a document that is publicly and openly available free of charge and free of any constraints of disclosure. AFRINIC will not recognize any activity under this policy if such an activity cannot be publicly disclosed.

Entities requiring such IP resources are expected to demonstrate an understanding that when the activity or experiment for which they require the IP resources ends, the IP resources will be returned to AFRINIC.

9.2  Assignments of IP resources 

Resources are assigned on a lease basis for a period of one month. The assignment can be renewed on application to AFRINIC providing the necessary information. The size of the assigned IP resource will be determined from the plan submitted by the requesting entity.

9.2.1 Required Documentation:

The requesting organisation should contact AFRINIC with the following information:

1. Details of Organisation: Legal Organisation name, Country Where Registered, Postal Address, Physical Address, Telephone and Fax Numbers, website (this is a must).
2. Details of activity requiring the temporary assignment: Website detailing the activity or Website with a link to similar previous activities, Links from other (relevant) sites about this activity, and the date when the above activity ends.
3. The planned use of these IP resources: List subnet size required, and for what it will be used plus any AS numbers and reverse delegation, if required.
4. The intended date of return of the IP resources above.

9.2 Assignments of IP resources

a.  Resources are assigned on a lease basis for a maximum period of one month. The assignment can be renewed on application to AFRINIC providing the necessary information.

b.  The size of the IP resource to be assigned will be determined from the plan submitted by the requesting entity, but will not exceed /22. The requesting entity is instead advised to use IPv6-only on their networks and deploy an IPv6 transition mechanism such as 464XLAT if necessary.

9.2.1 Required Documentation:

The requesting organisation should contact AFRINIC at least 3 months before the event with the following information:

1. Details of Organisation: Legal Organisation name, Country Where Registered, Postal Address, Physical Address, Telephone and Fax Numbers, website (this is a must).
2. Details of activity requiring the temporary assignment: Website detailing the activity or Website with a link to similar previous activities, Links from other (relevant) sites about this activity, and the date when the above activity ends.
3. The planned use of these IP resources: List subnet size required, and for what it will be used plus any AS numbers and reverse delegation, if required.
4. The intended date of return of the IP resources above.

9.3 Technical recommendations

a. The requesting entity is encouraged to deploy IPv6-only networks and a transition mechanism such as 464XLAT if necessary.

b. The requesting entity could base its architecture from some RFCs such as:

i. [rfc3750] (INFORMATIONAL) Unmanaged Networks for IPv6 Transition Scenarios

ii. [rfc4213] (Standards Track) Basic Transition Mechanisms for IPv6 Hosts and Routers

iii. [rfc6180] (INFORMATIONAL) Guidelines for Using IPv6 Transition Mechanisms during IPv6 Deployment