![Tutorial - IPv6 Address Management Paul Wilson Director General, APNIC [email_address]](https://image.slidesharecdn.com/apnicv6tutorialdistribution-12825054711096-phpapp02/85/Apnic-V6-Tutorial-Distribution-1-320.jpg)
![The boom years: 1992 – 2001 “ It has become clear that … these problems are likely to become critical within the next one to three years.” (RFC1366) “… it is [now] desirable to consider delegating the registration function to an organization in each of those geographic areas.” (RFC 1338) 1992:](https://image.slidesharecdn.com/apnicv6tutorialdistribution-12825054711096-phpapp02/85/Apnic-V6-Tutorial-Distribution-8-320.jpg)
![Questions? Paul Wilson Director General, APNIC [email_address]](https://image.slidesharecdn.com/apnicv6tutorialdistribution-12825054711096-phpapp02/85/Apnic-V6-Tutorial-Distribution-69-320.jpg)
Apnic V6 Tutorial Distribution
- 1. Tutorial - IPv6 Address Management Paul Wilson Director General, APNIC [email_address]
- 2. Tutorial Overview Introduction to IP Address Management Rationale for IPv6 IPv6 Addressing IPv6 Policies & Procedures References
- 4. The early years: 1981 – 1992 “ The assignment of numbers is also handled by Jon. If you are developing a protocol or application that will require the use of a link, socket, port, protocol, or network number please contact Jon to receive a number assignment .” (RFC 790) 1981:
- 6. Global Routing Table: ’88 - ’92
- 7. Global Routing Table: ’88 - ’92
- 8. The boom years: 1992 – 2001 “ It has become clear that … these problems are likely to become critical within the next one to three years.” (RFC1366) “… it is [now] desirable to consider delegating the registration function to an organization in each of those geographic areas.” (RFC 1338) 1992:
- 10. Global routing table http://bgp.potaroo.net/as1221/bgp-active.html CIDR deployment “ Dot-Com” boom Projected routing table growth without CIDR Sustainable growth?
- 11. Recent years: 2002 – 2005 2004: Establishment of the Number Resource Organisation
- 12. IPv4 Distribution – Global
- 13. IPv4 Distribution – Regional
- 14. IPv4 Allocations – Global top 10
- 16. What are RIRs? Regional Internet Registries Service organisations Industry self-regulatory structures Non-profit, neutral and independent Open membership-based bodies Representative of ISPs globally First established in early 1990’s Voluntarily by consensus of community To satisfy emerging technical/admin needs In the “Internet Tradition” Consensus-based, open and transparent
- 17. What do RIRs do? Internet resource allocation Primarily, IP addresses – IPv4 and IPv6 Receive resources from IANA/ICANN, and redistribute to ISPs on a regional basis Registration services (“whois”) Policy development and coordination Open Policy Meetings and processes Training and outreach Training courses, seminars, conferences… Liaison: IETF, ITU, APT, PITA, APEC… Publications Newsletters, reports, web site…
- 18. How do RIRs do it? Open and transparent processes Decision-making Policy development Open participation Democratic, bottom-up processes Membership structure 100% self-funded through membership fees National Internet Registries (APNIC) Community support (APNIC) Training R&D fund Fellowships – funding received and given Open source software contribution (GPL)
- 19. RIR Policy Coordination OPEN TRANSPARENT ‘ BOTTOM UP’ Anyone can participate All decisions & policies documented & freely available to anyone Internet community proposes and approves policy Need Discuss Evaluate Implement Consensus
- 21. IPv4 Lifetime http://bgp.potaroo.net/ipv4 IANA allocations RIR allocations Addresses routed Historical Data Projection Reclamation?
- 22. Rationale for IPv6 IPv4 address space consumption Now ~10 years free space remaining Up to 17 if unused addresses reclaimed These are today’s projections – reality will be different Loss of “end to end” connectivity Widespread use of NAT due to ISP policies and marketing Additional complexity and performance degradation
- 23. The NAT “Problem” 10.0.0.1 ..2 ..3 ..4 *AKA home router, ICS, firewall NAT* 61.100.32.128 R 61.100.32.0/25 61.100.32.1 ..2 ..3 ..4 ISP 61.100.0.0/16 The Internet
- 24. The NAT “Problem” ? Internet 10.0.0.1 61.100.32.128 NAT Extn 10 Phone Network 10 4567 9876 PABX
- 25. NAT implications Breaks end-to-end network model Some applications cannot work through NATs Breaks end-end security (IPsec) Requires application-level gateway (ALG) When new application is not NAT-aware, ALG device must be upgraded ALGs are slow and do not scale Merging of separate private networks is difficult Due to address clashes See RFC2993 Architectural Implications of NAT
- 26. Features of IPv6
- 27. IPv6 feature summary Increased size of address space Header simplification Autoconfiguration Stateless (RFC 2462) or stateful (DHCPv6) Facilitates renumbering QoS Integrated services (int-serv), Differentiated services (diff-serv and RFC2998) RFC 3697 IPSec As for IPv4 Transition techniques Dual stack Tunnelling
- 28. IPv6 addressing model Unicast Single interface Anycast Any one of several Multicast All of a group of interfaces Replaces IPv4 “broadcast” See RFC 3513
- 29. IPv4 vs IPv6 IPv4: 32 bits 2 32 addresses = 4,294,967,296 addresses = 4 billion addresses IPv6: 128 bits 2 128 addresses? = 340,282,366,920,938,463,463,374,607,431,770,000,000 = 340 billion billion billion billion addresses? No, due to IPv6 address structure…
- 30. IPv6 header IPv6 header is simpler than IPv4 IPv4: 14 fields, variable length (20 bytes +) IPv6: 8 fields, fixed length (40 bytes) Header fields eliminated in IPv6 Header Length Identification Flag Fragmentation Offset Checksum Header fields enhanced in IPv6 Traffic Class Flow Label
- 31. IPv6 transition Dual stack hosts Two TCP/IP stacks co-exists on one host Supporting IPv4 and IPv6 Client uses whichever protocol it wishes IPv4 IPv6 www.apnic.net ? ? IPv4 TCP/UDP Application IPv6 Link
- 32. IPv6 tunnel over IPv4 IPv6 transition IPv4 Network IPv6 IPv6 IPv6 Header Data IPv4 Header IPv6 Header Data IPv6 Header Data tunnel
- 33. IPv6 Addressing
- 34. How much IPv6? 128 bits 2 48 site addresses = 281,474,976,710,656 = 281 thousand billion site addresses 2 64 “subnet” addresses = 18,446,744,073,709,551,616 = 18 billion billion subnet addresses Topological Interface /0 /64 /128 Infrastructure Site /0 /64 /48
- 35. IPv6 address format 8 groups of 4 hexadecimal digits Each group represents 16 bits Separator is “:” Case-independent 128 bits 2001:0DA8:E800:0000:0260:3EFF:FE47:0001
- 36. IPv6 address format 2001:0DA8:E800:0000:0000:0000:0000:0001 2001:0DA8:E800:0000:0260:3EFF:FE47:0001 2001: 0 DA8:E800: 0000:0000:0000:0000:000 1 2001: 0 DA8:E800: 000 0: 0 260:3EFF:FE47: 000 1 2001:DA8:E800:0:260:3EFF:FE47:1 2001:DA8:E800::1
- 38. IPv6 address structure Each site address is /48 Providing 2 16 = 65,536 subnet addresses Current ISP allocation (min) is /32 Providing 2 16 = 65,536 customer site addresses ISP allocation can be larger and can increase Infrastructure Site /0 /64 /48 Infrastructure Customer ISP /0 /48 /32
- 39. Every ISP receives a /32 (or more) Providing 65,536 site addresses (/48) IPv6 – ISP addressing /32 /32 /32
- 40. Every “site” receives a /48 Providing 65,536 /64 (LAN) addresses IPv6 – Site addressing /48
- 41. IPv6 – LAN addressing Every LAN segment receives a /64 Providing 2 64 interface addresses per LAN /64
- 42. IPv6 – Device addressing Every device interface receives a /128 May be EUI-64 (derived from interface MAC address), random number (RFC 3041), autoconfiguration, or manual configuration /128 /128 /128 /128
- 43. IPv6 Policy
- 44. IPv6 policy – Overview Policy background Addressing structure IPv6 utilisation – HD ratio Initial allocation criteria Subsequent allocation criteria Address assignment policies Other allocation conditions Other policies
- 45. IPv6 policy – History IPv6 policy is “Common Policy” of all RIRs The same policy has been adopted by all Regional adjustment is possible First policy published in 1999 “ Provisional IPv6 Policy” adopted by all RIRs Policy revised in 2002 After extensive review by all RIRs Next policy review Currently under discussion Public mailing lists and documentation See http:// www.apnic.net
- 46. IPv6 address space management RIR receives allocations from IANA Currently in /23 units (/16 proposed) RIR makes allocation to “ISP” (or “LIR”) ISP must demonstrate need for addresses Policies dictate how need can be demonstrated First allocation minimum is /32 Subsequent allocations as needed, when current allocation is fully utilised ISP makes assignment to customers Including downstream ISPs Provider-based addressing ISP should aggregate address announcement Customer addresses are not portable
- 47. IPv6 address structure Topological Interface 0 /64 127 001 TLA SLA NLA Sub-TLA 001 Infrastructure End Site 0 /3 /64 /48 /32
- 48. IPv6 utilisation – HD Ratio Under IPv4, address space utilisation measured as simple percentage: IPv4 utilisation requirement is 80% When 80% of address space has been assigned or allocated, LIR may receive more E.g. ISP has assigned 55,000 addresses from /16
- 49. IPv6 utilisation – HD Ratio Under new IPv6 policy utilisation is determined by HD-Ratio (RFC 3194): IPv6 utilisation requirement is HD=0.80 Measured according to end-site assignments only (intermediate allocations are ignored) E.g. ISP has assigned 10,000 addresses from /32
- 50. IPv6 utilisation (HD = 0.80) RFC3194 “The Host-Density Ratio for Address Assignment Efficiency” /32 10.9% 1.18% /16
- 51. IPv6 utilisation (HD = 0.80) Percentage utilisation calculation 0.4 % 68719476736 35184372088832 45 /3 0.4 % 4294967296 1099511627776 40 /8 1.2 % 50859008 4294967296 32 /16 3.6 % 602249 16777216 24 /24 7.3 % 37641 524288 19 /29 10.9 % 7132 65536 16 /32 16.5 % 1351 8192 13 /35 18.9 % 776 4096 12 /36 43.5 % 28 64 6 /42 Utilisation % Threshold (HD ratio 0.8) Total site address in /48s Site Address Bits IPv6 Prefix
- 52. IPv6 initial allocation criteria Initial allocation size is /32 Allocated to any IPv6 LIR (ISP) planning to connect 200 End Sites within 2 years Need not be connected to the Internet This is the default initial allocation to “new” ISPs (“slow start” policy) Larger initial allocations can be made if justified according to: IPv6 network infrastructure plan Existing IPv4 infrastructure and customer base
- 53. IPv6 allocation to existing network Existing ISP infrastructure (IPv4) Policy assumes that transition is inevitable Large IPv4 ISPs will receive IPv6 allocations consistent with the scale of existing networks IPv4 IPv6
- 54. IPv6 allocation to existing network Allocation size calculated from existing IPv4 network infrastructure and customers: 1 IPv6 /48 per customer 1 IPv6 /48 per POP Total allocation according to HD-ratio utilisation requirement Eg if 500,000 /48s are required then /24 can be allocated
- 55. IPv6 assignments Default assignment /48 for all “End Sites” Providing /16 bits of space for subnets Each end site can have 65,536 subnets “ End Site” defined as an end user of an ISP where: The ISP assigns address space to the end user The ISP provides Internet transit service to the end user The ISP advertises an aggregate prefix route that contains the end user's assignment Multiple subnets are required Examples Home, small office, large office, mobile devices? ISP POPs are also defined as End Sites
- 56. IPv6 assignments Larger assignments: Multiple /48s Some end sites will need more than one /48 Requests to be reviewed at RIR level Smaller assignments: /64 Single subnet devices should receive /64 only e.g. simple mobile phone Smaller assignments: /128 Devices with no subnets should receive /128 only E.g. remote sensor See RFC3177 (Sep 2001)
- 57. IPv6 assignments IPv6 assignments to End Sites are used to determine utilisation of IPv6 address blocks According to HD-Ratio Intermediate allocation hierarchy (ie downstream ISP) not considered All assignments must be registered Utilisation is determined from total number of registrations Intermediate allocation and assignment practices are the responsibility of the LIR Downstream ISPs must be carefully managed
- 58. IPv6 registration LIR is responsible for all registrations RIR/NIR LIR/NIR ISP Assignment Allocation Allocation Assignment Registration
- 59. Subsequent IPv6 allocation Subsequent allocation can be made when ISP’s existing address space reaches required utilisation level i.e. HD >= 0.80 Other address management policies must also be met Correct registrations Correct assignment practices etc (eg RFC 3177) Subsequent allocation size is at least double Resulting IPv6 Prefix is at least 1 bit shorter Or sufficient for at least 2 years requirement
- 60. Other allocation conditions License model of allocation Allocations are not considered permanent, but always subject to review and reclamation Licenses renewed automatically while addresses in use, consistent with policies Existing /35 allocations A number of /35s have been assigned under previous “provisional” IPv6 policy Holders of /35s are eligible to request /32
- 61. IPv6 IXP assignments Available to Internet Exchange Points as defined Must demonstrate ‘open peering policy’ 3 or more peers Portable assignment size: /48 Not to be announced A ll other needs should be met through normal processes Previous /64 holders can “upgrade” to /48
- 62. IPv6 critical infrastructure Available to facilities defined as “critical infrastructure” Root servers RIRs and NIRs ccTLD registries Assignment size: /32
- 63. IPv6 experimental allocation Available for experimental purposes Public experiments only Legitimate experiments documented by RFC, I-D or other formal process APNIC may seek independent expert advice Allocation size: /32 May be larger if required Address space must be returned after 1 year
- 64. IPv6 policy – Current issues Size of IANA allocation to RIRs Currently under review Size of initial allocation /32 for normal allocations HD-ratio applied for allocation to existing IPv4 infrastructure HD-ratio Is 0.8 the appropriate value? Assignments under RFC 3177 No experience yet All issues can be reviewed through APNIC open policy process
- 65. IPv6 Policy – Summary IPv6 address space is easily available Criteria may be hardened in future Policy is subject to review Policies evolve as experience is gained Any member of the community may propose changes, alternatives Public mailing lists and documentation http://www.apnic.net/
- 66. References
- 67. APNIC References APNIC website http:// www.apnic.net APNIC IPv6 Resource Guide http://www.apnic.net/services/ipv6_guide.html Includes: Policy documents Request forms FAQs
- 68. Other References IPv6 Forum http://www.ipv6forum.org 6Bone http://www.6bone.net “ The case for IPv6” http://www.6bone.net/misc/case-for-ipv6.html
- 69. Questions? Paul Wilson Director General, APNIC [email_address]
Editor's Notes
- #3: References: “ The case for IPv6” http://www.6bone.net/misc/case-for-ipv6.html IPv6 FAQ http://www.apnic.net/info/faq/IPv6-FAQ.html IPv6 Allocation & Assignment policy http://www.apnic.net/docs/policy/ipv6-address-policy.html IPv6 request form http://ftp.apnic.net/apnic/docs/ipv6-alloc-request
- #6: References: The CIDR report http://www.cidr-report.org/ The BGP Routing Table http://bgp.potaroo.net/as1221/bgp-active.html
- #7: At this rate of growth the internet could not have been maintained as a single global network. Many addresses would become unreachable and unused.
- #8: At this rate of growth the internet could not have been maintained as a single global network. Many addresses would become unreachable and unused.
- #10: References: The CIDR report http://www.cidr-report.org/ The BGP Routing Table http://bgp.potaroo.net/as1221/bgp-active.html
- #11: References: The CIDR report http://www.cidr-report.org/ The BGP Routing Table http://bgp.potaroo.net/as1221/bgp-active.html
- #62: IXP Assignment policy Internet Exchange Points are eligible to receive a portable assignment from APNIC for use on their IXP transit LAN. A special condition of all assignments made under these terms is that the IXP must not announce the address space to the global Internet routing table. All IXP who received a /64 from previous policy can receive a /48 in return for their /64. (They can do this through simply sending a mail to APNIC or their respective NIR.) References: IPv6 portable assignment request form: http://ftp.apnic.net/apnic/docs/portable-assign-request.txt
- #63: IXP Assignment policy Internet Exchange Points are eligible to receive a portable assignment from APNIC for use on their IXP transit LAN. A special condition of all assignments made under these terms is that the IXP must not announce the address space to the global Internet routing table. All IXP who received a /64 from previous policy can receive a /48 in return for their /64. (They can do this through simply sending a mail to APNIC or their respective NIR.) References: IPv6 portable assignment request form: http://ftp.apnic.net/apnic/docs/portable-assign-request.txt
- #64: IXP Assignment policy Internet Exchange Points are eligible to receive a portable assignment from APNIC for use on their IXP transit LAN. A special condition of all assignments made under these terms is that the IXP must not announce the address space to the global Internet routing table. All IXP who received a /64 from previous policy can receive a /48 in return for their /64. (They can do this through simply sending a mail to APNIC or their respective NIR.) References: IPv6 portable assignment request form: http://ftp.apnic.net/apnic/docs/portable-assign-request.txt