Details
|
AFPUB-2018-GEN-004-DRAFT02 |
Version: 2.0 Status: Withdrawn Obsoletes: |
Authors:
|
|
Amends: CPM 9.0 |
||
|
Submitted: 18 April 2019 |
Proposal
1.0 Summary of the problem being addressed by this proposal
With IPv4 exhaustion coming, IPv4 resource assignments need better management because of scarcity. For instance, what happens if some entities request a /20 worth of IPv4 for temporary usage during Soft Landing phase 2? With the current IPv6 evolution, we think entities requesting temporary resources should deploy more IPv6 than IPv4 space.
2.0 Summary of how this proposal addresses the problem
This proposal aims to restrict the size of IPv4 resource requests for temporary use such as for conferences and meetings, to /22. In addition, the proposal encourages IPv6 usage for those purposes on the premise that IPv6 is now mature enough to be deployed for this kind of usage.
Any IPv4 space requested for temporary usage should not be more than /22 - especially for meetings and events. The requesting entity should use IPv6-only on their networks and deploy an IPv6 transition mechanism such as 464XLAT if necessary.
Lastly, the title of this section of the CPM should reflect exactly the fact that we are dealing with PI Assignments only and not PA allocations.
3.0 Proposal
CPM 9.0 to be modified as follows:
|
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:
|
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:
|
|
|
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 |
4.0 References
Policy Implementation Experience Report presented during AFRINIC 27 - 30 Nov 2017:
https://youtu.be/YZq7pvUwWk0?t=35799
Revision History
Revision History
|
Date |
Details |
|
13 Dec 2018 |
Version 1: AFPUB-2018-GEN-004-DRAFT01 |
|
18 Apr 2019 |
Version 2: AFPUB-2018-GEN-004-DRAFT02
|
