------------------------------------------------------- prop-135-v001: Documentation ------------------------------------------------------- Proposer: Amrita Choudhury (amritachoudhury@ccaoi.in) Simon Sohel Baroi (sbaroi@gmail.com) 1. Problem statement -------------------- It has been observed that the Sections 5.6 and 5.6.1 are repetitive in the Resource Request Supportive Document. 2. Objective of policy change ----------------------------- The objective of the policy change is to make the policy simple and easier for the community to understand and adopt and remove duplication if any. 3. Situation in other regions ----------------------------- 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 4. Proposed policy solution --------------------------- To avoid duplication, the proposal is to remove 5.6.1 and include any additional requirements into 5.6. Currently the two sections are as follows: Section 5.6. General requirements All requests for address space must be supported by documentation describing: ·The network infrastructure of the organization making the request, ·Any address space currently held by that organization (including Historical address space), ·Previous assignments made by that organization (including assignments made from Historical address allocations), and ·The intended use for the address space requested. In addition to this general requirement, more specific documentation may also be requested, as outlined below. Section 5.6.1. Documentation states To properly evaluate requests, IRs must carefully examine all relevant documentation relating to the networks in question. This documentation may include: ·Network engineering plans ·Subnetting plans ·Descriptions of network topology ·Descriptions of network routing plans ·Equipment invoices and purchase orders ·Other relevant documents All documentation should conform to a consistent standard and any estimates and predictions that are documented must be realistic and justifiable. Ref link: https://www.apnic.net/community/policy/resources#5.6.-General-requirements-for-requests What we propose is: 5.6 General Requirements: In order to properly evaluate requests, APNIC 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 the network routing plans. Further, based on request the following information may be requested such as equipment invoices and purchase orders, any address space currently held by that organization (including Historical address space), previous assignments made by that organization (including assignments made from Historical address allocations), and the intended use for the address space requested. All documentation should conform to a consistent standard and any estimates and predictions that are documented must be realistic and justifiable. 5. Advantages / Disadvantages ------------------------------------------------------- Advantages: The advantage of the proposal is that it removes duplication and makes the document more precise. Disadvantages: There are no disadvantages. 6. Impact on resource holders ------------------------------------------------------- There is no impact on resource holders. Rather, it simplifies the process for them. 7. References ------------------------------------------------------- None.