prop-135: Documentation

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.

n/a

ARIN: Does not seem to have definitive documentation. Reference Link: https://www.arin.net/participate/policy/nrpm/

RIPE NCC: Does not seem to have a consolidated document Reference Link: https://www.ripe.net/publications/docs/ripe-policies?b_start:int=0

LACNIC mentions: 2.3.2.5.Documentation 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: https://www.lacnic.net/innovaportal/file/680/1/manual-politicas-en-2-14.pdf

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: https://afrinic.net/policy/manual