Download - Apnic V6 Tutorial Distribution
![Page 2: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/2.jpg)
2
Tutorial Overview
• Introduction to IP Address Management
• Rationale for IPv6
• IPv6 Addressing
• IPv6 Policies & Procedures
• References
![Page 3: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/3.jpg)
3
IP Address Management
![Page 4: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/4.jpg)
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:
![Page 5: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/5.jpg)
5
IANA Address Consumption
1983 1984 1985 1986 1987 1988 1989 1990 1991
0
2
4
6
8
10
12
14
16
![Page 6: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/6.jpg)
6
Global Routing Table: ’88 - ’92
0
1000
2000
3000
4000
5000
6000
7000
8000
9000
Jul-88 Jan-89 Jul-89 Jan-90 Jul-90 Jan-91 Jul-91 Jan-92 Jul-92
![Page 7: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/7.jpg)
7
0
10000
20000
30000
40000
50000
60000
70000
80000
90000
100000
Jan-89 Jan-90 Jan-91 Jan-92 Jan-93 Jan-94 Jan-95 Jan-96
Global Routing Table: ’88 - ’92
![Page 8: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/8.jpg)
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:
![Page 9: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/9.jpg)
9
IANA Address Consumption
1983 1984 1985 1986 1987 1988 1989 1990 1991
0
2
4
6
8
10
12
14
16
19
83
19
84
19
85
19
86
19
87
19
88
19
89
19
90
19
91
19
92
19
93
19
94
19
95
19
96
19
97
19
98
19
99
20
00
20
01
20
02
20
03
20
04
20
05
0
2
4
6
8
10
12
14
16
various
assigned
ripencc
lacnic
arin
apnic
![Page 10: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/10.jpg)
10
Global routing table
http://bgp.potaroo.net/as1221/bgp-active.html
CIDR deployment
“Dot-Com” boom
Projected routing table growth without CIDR
Sustainablegrowth?
![Page 11: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/11.jpg)
11
Recent years: 2002 – 2005
2004:
Establishment of the Number Resource Organisation
![Page 12: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/12.jpg)
12
IPv4 Distribution – Global
Unused75
29%
RIPENCC166%
LACNIC2
1%
Historical89
35%
Reserved36
14%
APNIC166%
ARIN229%
![Page 13: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/13.jpg)
13
IPv4 Distribution – Regional
1999 2000 2001 2002 20032004
2005
0.00
0.50
1.00
1.50
2.00
2.50
3.00
apnic
arin
lacnic
ripencc
afrinic
![Page 14: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/14.jpg)
14
IPv4 Allocations – Global top 10
199319941995199619971998 1999 2000 2001 2002 2003 2004 2005
0
0.5
1
1.5
2
2.5
3
3.5
4
4.5
5
ES
NL
CA
FR
DE
KR
UK
CN
JP
US
![Page 15: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/15.jpg)
15
Regional Internet Registries
![Page 16: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/16.jpg)
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
![Page 17: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/17.jpg)
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…
![Page 18: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/18.jpg)
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)
![Page 19: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/19.jpg)
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
DiscussEvaluate
Implement Consensus
![Page 20: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/20.jpg)
20
Rationale for IPv6
![Page 21: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/21.jpg)
21
IPv4 Lifetime
http://bgp.potaroo.net/ipv4
IANA allocations
RIR allocatio
ns
Addresses routed
Historical Data Projection
Reclamation?
![Page 22: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/22.jpg)
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
![Page 23: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/23.jpg)
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
![Page 24: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/24.jpg)
24
The NAT “Problem”
Internet
10.0.0.1
61.100.32.128
NAT
?Extn 10
Phone Network
10 4567 9876
PABX
![Page 25: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/25.jpg)
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
![Page 26: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/26.jpg)
26
Features of IPv6
![Page 27: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/27.jpg)
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
![Page 28: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/28.jpg)
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
![Page 29: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/29.jpg)
29
IPv4 vs IPv6
IPv4: 32 bits
• 232 addresses = 4,294,967,296 addresses
= 4 billion addresses
IPv6: 128 bits
• 2128 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…
![Page 30: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/30.jpg)
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
![Page 31: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/31.jpg)
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
![Page 32: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/32.jpg)
32
• IPv6 tunnel over IPv4
IPv6 transition
IPv4Network
IPv6 IPv6
IPv6 Header Data
IPv4 Header IPv6 Header Data
IPv6 Header Data
tunnel
![Page 33: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/33.jpg)
33
IPv6 Addressing
![Page 34: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/34.jpg)
34
128 bits
How much IPv6?
Topological Interface
/0 /64 /128
Infrastructure Site
/0 /64/48
• 248 site addresses = 281,474,976,710,656
= 281 thousand billion site addresses
• 264 “subnet” addresses = 18,446,744,073,709,551,616
= 18 billion billion subnet addresses
![Page 35: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/35.jpg)
35
IPv6 address format
• 8 groups of 4 hexadecimal digits– Each group represents 16 bits– Separator is “:”– Case-independent
128 bits2001:0DA8:E800:0000:0260:3EFF:FE47:0001
![Page 36: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/36.jpg)
36
2001:0DA8:E800:0000:0000:0000:0000:0001
2001:0DA8:E800:0000:0260:3EFF:FE47:0001
IPv6 address format
2001:DA8:E800:0:260:3EFF:FE47:1
2001:0DA8:E800:0000:0000:0000:0000:0001
2001:0DA8:E800:0000:0260:3EFF:FE47:0001
2001:DA8:E800::1
![Page 37: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/37.jpg)
37
IPv6 Address Structure
![Page 38: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/38.jpg)
38
IPv6 address structure
Infrastructure Site
/0 /64/48
• Each site address is /48• Providing 216 = 65,536 subnet addresses
• Current ISP allocation (min) is /32• Providing 216 = 65,536 customer site addresses• ISP allocation can be larger and can increase
Infrastructure CustomerISP
/0 /48/32
![Page 39: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/39.jpg)
39
• Every ISP receives a /32 (or more)– Providing 65,536 site addresses (/48)
/32
/32
IPv6 – ISP addressing
/32
![Page 40: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/40.jpg)
40
• Every “site” receives a /48– Providing 65,536 /64 (LAN) addresses
IPv6 – Site addressing
/48
![Page 41: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/41.jpg)
41
IPv6 – LAN addressing
• Every LAN segment receives a /64– Providing 264 interface addresses per LAN
/64
![Page 42: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/42.jpg)
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
![Page 43: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/43.jpg)
43
IPv6 Policy
![Page 44: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/44.jpg)
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
![Page 45: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/45.jpg)
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
![Page 46: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/46.jpg)
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
![Page 47: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/47.jpg)
47
IPv6 address structure
Topological Interface
0 /64 127
001 TLA SLANLASub-TLA
001 Infrastructure End Site
0 /3 /64/48/32
![Page 48: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/48.jpg)
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
availableassignednUtilisatio
%84536,65
000,55 availableassigned
![Page 49: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/49.jpg)
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
)log()log(
availableassigned
HDnUtilisatio
83.0)536,65log(
)000,10log()log()log( available
assigned
![Page 50: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/50.jpg)
50
0%
10%
20%
30%
40%
50%
60%
70%
80%
90%
100%
48 44 40 36 32 28 24 20 16 12 8 4 0
IPv6 utilisation (HD = 0.80)
RFC3194 “The Host-Density Ratio for Address Assignment Efficiency”
/32
10.9%
1.18%
/16
0.80)log(
)log( total
utilised
![Page 51: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/51.jpg)
51
IPv6 utilisation (HD = 0.80)
• Percentage utilisation calculation
IPv6
Prefix
Site Address
Bits
Total site address in /48s
Threshold
(HD ratio 0.8)
Utilisation %
/42 6 64 28 43.5 %
/36 12 4096 776 18.9 %
/35 13 8192 1351 16.5 %
/32 16 65536 7132 10.9 %
/29 19 524288 37641 7.3 %
/24 24 16777216 602249 3.6 %
/16 32 4294967296 50859008 1.2 %
/8 40 1099511627776 4294967296 0.4 %
/3 45 35184372088832 68719476736 0.4 %
![Page 52: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/52.jpg)
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
![Page 53: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/53.jpg)
53
IPv4
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
IPv6
![Page 54: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/54.jpg)
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
![Page 55: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/55.jpg)
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
![Page 56: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/56.jpg)
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)
![Page 57: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/57.jpg)
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
![Page 58: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/58.jpg)
58
RIR/NIR
LIR/NIR
ISPAssignment
Allocation
Allocation
IPv6 registration
• LIR is responsible for all registrations
Assignment
Registration
![Page 59: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/59.jpg)
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
![Page 60: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/60.jpg)
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
![Page 61: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/61.jpg)
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– All other needs should be met through
normal processes– Previous /64 holders can “upgrade” to /48
![Page 62: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/62.jpg)
62
IPv6 critical infrastructure
• Available to facilities defined as “critical infrastructure”– Root servers– RIRs and NIRs– ccTLD registries
• Assignment size: /32
![Page 63: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/63.jpg)
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
![Page 64: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/64.jpg)
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
![Page 65: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/65.jpg)
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/
![Page 66: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/66.jpg)
66
References
![Page 67: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/67.jpg)
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
![Page 68: Apnic V6 Tutorial Distribution](https://reader035.vdocuments.us/reader035/viewer/2022062513/554bd47ab4c9058f6c8b4f37/html5/thumbnails/68.jpg)
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