Internet Registry allocation and assignment

1. Internet Registry allocation and assignment Policies

2. Overview of RIR Policies • Definitions • Background • Objectives • Environment • Allocation & Assignment Policies • Summary

3. Definition: Allocation and Assignment • Allocation • A block of address space held by an IR for subsequent allocation or assignment • Not yet used to address any networks • Assignment • A block of address space used to address an operational network • May be provided to LIR customers, or used for an LIR’s infrastructure (‘self-assignment’)

4. Definition: Allocation and Assignment RIR LIR Allocates IP addresses Assigns IP addresses LIR Customer

5. Definition: PI and PA • Provider Independent (Portable) • Customer holds addresses independent from ISP • Customer keeps addresses when changing ISP • Bad for size of routing tables • Bad for QOS: routes may be filtered, flap-dampened • Provider Aggregatable (Non-portable) • Customer uses ISP’s address space • Customer must renumber if changing ISP • Only way to effectively scale the Internet

6. But they cannot be relied on forever Projected routing table growth without CIDR Moore’s Law and CIDR made it work for a while DeploymentPeriod of CIDR RIR Policies - Background • Growth of Global Routing Table • Unaggregated Internet would exceed 200,000 routes! http://www.telstra.net/ops/bgptable.html

7. May-00 <16 16 Mar-00 17 18 Jan-00 19 20 21 Nov-99 22 23 Sep-99 24 >24 Jul-99 0 20000 40000 60000 80000 100000 Routing Table Prefix Distribution

8. RIR Policies - Objectives • Ensuring efficient use and conservation of resources • Through careful allocation and assignment policies • Limiting growth of routable prefixes • Through provider-based addressing • Fairness and consistency of procedures • Through neutrality and expertise of registry

9. RIR Allocation Policies • IP addresses not freehold property • Internet resources are public resources • ‘Ownership’ is contrary to management goals • Need to avoid the mistakes of the past • Assignments & allocations on lease basis • Routability not guaranteed • ISPs determine routability • Unpredictable growth rates • IPv4 deployment levels unanticipated • Routing table growth still poses a threat

10. RIR Allocation Policies • Varying levels of expertise • Growing technical challenge • Staff turnover throughout industry • Flexible policies to accommodate differences • Training programme to support LIRs • Confidentiality & security • RIR to observe and protect trust relationship • Non-disclosure agreement signed by staff

11. RIR Allocation Policies • Minimum practical allocation /20 • ‘Slow Start’ policy for new LIRs • Allocations as PA address space • Provider responsible for aggregation • Customer assignments must be non-portable • Allocations based on demonstrated need • Detailed documentation required • All address space held to be declared • Stockpiling not permitted

12. RIR Allocation Policies • Implement ‘Best current practice’ • Will change over time as technology changes • Static assignments discouraged • dial up • virtual hosts (ip based web hosting, should be name based) • Address conservation considered • implement ‘ip unnumbered’ • use private address space (rfc1918) • consider use of Network Address Translation (NAT)

13. Questions?