prop-135: Documentation

Proposal textprop-135-v001

This proposal suggests to simply the supporting documentation required for resource requests and to remove duplication if any. In the current policy document, Sections 5.6 and 5.6.1 are repetitive in the Resource Request Supportive Document.

Current statusTo be discussed at APNIC 52
AuthorAmrita Choudhury and Simon Sohel Baroi
Relevant forumPolicy SIG
Previous versions


Status at other RIRs

ARIN: Does not seem to have definitive documentation. Reference Link:

RIPE NCC: Does not seem to have a consolidated document Reference Link:

LACNIC mentions: Internet Registries shall use the IPv4 addresses they have been allocated in an efficient manner. To this end, IRs shall document the justification for each IPv4 address assignment. At the request of LACNIC, the corresponding IR shall make this information available. LACNIC shall not make complementary allocations to those Internet Registries that have not properly documented the use of the blocks already allocated. In these cases, existing allocations may also be reviewed. The documentation LACNIC may require includes: • Engineering plans. • Subnetting and aggregation plan. • Description of network topology. • Description of network routing plans. • Receipts documenting investments (equipment). • Other relevant documents Reference Link:

AFRINIC: Policy document mentions: 5.2.3 Documentation In order to properly evaluate requests, an RIR must carefully examine all relevant documentation relating to the networks in question. Such documentation may include network engineering plans, sub-netting plans, descriptions of network topology, and descriptions of network routing plans. All documentation should conform to a consistent standard and any estimates and predictions that are documented must be realistic and justifiable. Reference Link:

Secretariat impact assessmentprop-135-v001:

This proposal appears to be straightforward. APNIC notes the removal of duplication in the policy manual for “Documentation” required to evaluate resource request, and it is unlikely to change current practices for evaluating requests.

This proposal would not require any changes to the registration system.

If this proposal reaches consensus, implementation can be completed within 3 months.
Proposal history
13 August 2021Version 1 posted to the Policy SIG mailing list for discussion and community development.