HO CHI MINH CITY UNIVERSITY OF SCIENCE IPv6 – Why We Need More Address Space

FACULTY OF ELECTRONICS AND TELECOMMUNICATIONS

DEPARTMENT OF TELECOMMUNICATIONS AND NETWORKS
IPv4 Address Allocation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
COURSE
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
1993
COMPUTER NETWORKS 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111

Chapter
IP VERSION 6
112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127

05
128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
Allocated
176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
Reference: Peter L Dordal, “An Introduction to Computer Networks,” Jul 26, 2019 Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
Available
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
addresses
Lecturer: Nguyen Viet Ha, Ph.D. Email: nvha@[Link] Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 2

IPv6 – Why We Need More Address Space IPv6 – Why We Need More Address Space

IPv4 Address Allocation IPv4 Address Allocation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
2000 2007
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
Allocated Allocated
176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
Available Available
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
addresses addresses
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 3 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 4
 IPv6 – Why We Need More Address Space IPv6 – Why We Need More Address Space

IPv4 Address Allocation IPv4 Address Allocation

0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

2009
16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
2010 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143
144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159
160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
Allocated Allocated
176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
Available Available
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
addresses addresses
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 5 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 6

IPv6 – Why We Need More Address Space IPv6 – Why We Need More Address Space

IPv4 Address Allocation ❖Address Availability:

➢IPv4: 4 octets - 32 bits
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
February 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
o 2^32 or 4,294,467,295 IP Addresses.
2011 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47
48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63
64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79
➢IPv6: 16 octets - 128 bits
80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 o 2^128 ≈ 3.4 x 10^38 or
340,282,366,920,938,463,463,374,607,431,768,211,456
96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111
112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127
128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 (340 undecillion)
144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 IP Addresses.
Allocated 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175
176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191
Unavailable 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207
208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223
Available
224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239
16,777,216 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255
addresses
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 7 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 8
 1. The IPv6 Header

4-bit 8-bit 20-bit

16-bit 8-bit 8-bit

1 The IPv6 Header

128-bit

128-bit

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 10

1. The IPv6 Header 1. The IPv6 Header

❖ Fixed header (40 bytes) ❖ Version: 4-bit, identifying the IP packet version (0110).
➢ No support for fragmentation ❖ Traffic Class: 8-bit, is equivalent to the IPv4
➢ No header checksum ‘Differentiated Services’ field
➢ No option fields. ❖ Payload Length: 16-bit, is equivalent to the IPv4 ‘Total
Length’ field.
❖ Next Header: 8-bit, is equivalent to the IPv4 ‘Protocol’
o Extension headers has been introduced to support field.
some of these as options. (latter in Section 5) ❖ Hop Limit: 8-bit, replaces the IPv4 ‘TTL’ field.
❖ Source Address: 128-bit, identifies the IPv6 address of
the sending host.
❖ Destination Address: 128-bit, identifies the IPv6 address
of the receiving host.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 11 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 12
 1. The IPv6 Header

❖Flow Label: 20-bit, be used by a source to label

sequences of packets for which it requests special
handling by the IPv6 routers, such as:
o Non-default quality of service
o “real-time” service.

➢ A flow, as the term is used here, is one-way; the

2 IPv6 Addresses
return traffic belongs to a different flow.

➢ All packets belonging to the same flow should

have the same Routing Extension header.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 13

2. IPv6 Addresses 2. IPv6 Addresses

❖128 bits in length and written as a string of hexadecimal
❖Hexadecimal is a base
values
sixteen system

❖32 hexadecimal values = IPv6 address

❖Base 16 numbering system
uses the numbers 0 to 9
and the letters A to F 2001:0DB8:0000:1111:0000:0000:0000:0200
FE80:0000:0000:0000:0123:4567:89AB:CDEF
❖Four bits (half of a byte)
can be represented with a ❖Hextet used to refer to a segment of 16 bits or four
single hexadecimal value hexadecimals

❖Can be written in either lowercase or uppercase

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 15 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 16
 2. IPv6 Addresses 2. IPv6 Addresses
❖Rule 1- Omitting Leading 0s ❖Rule 2- Omitting All 0 Segments
➢The first rule to help reduce the notation of IPv6 ➢A double colon (::) can replace any single, contiguous
addresses is any leading 0s (zeros) in any 16-bit section string of one or more 16-bit segments (hextets)
or hextet can be omitted consisting of all 0’s
▪ 01AB can be represented as 1AB ➢Known as the compressed format
▪ 09F0 can be represented as 9F0 ➢Double colon (::) can only be used once within an
▪ 0A00 can be represented as A00 address otherwise the address will be ambiguous.
▪ 00AB can be represented as AB

Example: 1843:f01::22::fa
1843:0f01:0000:0000:0022:0000:0000:00fa ?
1843:0f01:0000:0000:0000:0022:0000:00fa ?
1843:0f01:0000:0022:0000:0000:0000:00fa ?

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 17 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 18

2. IPv6 Addresses 2. IPv6 Addresses

❖Interface identifiers ❖EUI-64
➢IPv6 addresses can be divided into a 64-bit network
prefix and a 64-bit “host” portion.
o host-portion bits are known officially as the interface
identifier.

➢Original plan for the interface identifier was to derive it

in most cases from the LAN address.
o 48 bits → 64 bits ???
▪ EUI-64

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 19 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 20
 2. IPv6 Addresses 2. IPv6 Addresses
❖EUI-64 ❖EUI-64
➢Review MAC ➢A major privacy concern:
Address: o No matter where a host connects to the Internet –
home or work or airport or Internet cafe
o "c" is the bits of the assigned company_id, ▪ Such an interface identifier always remains the
o "m" is the bits of the manufacturer selected extension same, and thus serves as a permanent host
identifier. fingerprint.
o “U" is the value of the Universal/Local bit.
▪ 0: Universal, i.e., MAC address is the burned-in-address
➢Now discouraged for personal workstations and mobile
(BIA)
devices. (Only for some fixed-location hosts)
▪ 1: Local, i.e., MAC address that has been changed locally
o “G" is individual/group bit
▪ 0: individual (i.e., unicast)
▪ 1: group (i.e., multicast/broadcast)
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 21 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 22

2. IPv6 Addresses 2. IPv6 Addresses

❖An alternative (RFC 7217): ❖Link-local addresses:
➢The interface identifier is a secure hash of: ➢Used only on a single LAN and never routed.
o A “Net_Iface” parameter. ➢ FE80::/64
▪ The interface’s MAC address, o The remaining 64 bits are the interface identifier
▪ Or the interface’s “name”, e.g., eth0. (EUI-64 or “Hashing” methods).
o 64-bit IPv6 address prefix.
o A host-specific secret key. ➢Applications:
o A “bootstrap” address for global-address auto-
➢Interface identifiers created this way change from configuration
connection point to connection point (because the prefix o An optional permanent address for routers.
changes). ▪ IPv6 routers often communicate with neighboring
routers via their link-local addresses.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 23 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 24
 2. IPv6 Addresses
❖Anycast addresses:
➢Assigned to each of a set of routers/servers.

➢A packet addressed to this anycast address would be

delivered to only one member of this set.

➢It is up to the local

routing infrastructure
3 Network Prefixes
to decide which
member of the anycast
group would receive
the packet; normally it
would be sent to the
“closest” member. [Link]

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 25

3. Network Prefixes 3. Network Prefixes

❖IPv6 address is composed of a 64-bit network prefix and a ❖IPv6 customers will typically be assigned a relatively large
64-bit interface identifier. block of addresses, e.g., “/48” or “/56”.

❖Routers still uses CIDR (10.1 Classless Internet Domain ➢The former allows 64–48 = 16 bits for local “subnet”
Routing: CIDR) and still bases forwarding decisions on specification within a 64-bit network prefix
prefixes shorter than /64.
➢The latter (“/56”) allows 8 subnet bits.
❖64-bit network prefixes are supplied by a provider, and
which represent the first half of globally routable IPv6
addresses.
➢These are the prefixes that will be visible to the outside
world.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 27 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 28
 2. IPv6 Addresses
❖Unique Local Unicast Address:
➢Corresponding to IPv4 private address blocks like
[Link]/16, [Link]/12, and [Link]/8.
➢The first 8 bits of a unique-local prefix are 1111 1101
(fd00::/8).
➢The related prefix 1111 1100 (fc00::/8) is reserved for
future use.
4 IPv6 Multicast
➢The last 16 bits of a 64-bit unique-local prefix represent
the subnet ID, and are assigned either administratively
or via autoconfiguration.
➢The 40 bits in between, from bit 8 up to bit 48,
represent the Global ID.
o A site is to set the Global ID to a pseudorandom
value.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 29

4. IPv6 Multicast 4. IPv6 Multicast

❖For actual delivery, IPv6 multicast addresses correspond to
❖IPv6 has no LAN-layer broadcast.
LAN-layer (e.g., Ethernet) multicast addresses through a
well-defined static correspondence.
➢Providing a wide range of LAN-layer multicast groups. ➢If x, y, z and w are the last four bytes of the IPv6
multicast address, in hex,
➢Intended to limit broadcast traffic in general, though →Ethernet multicast
many switches still propagate LAN multicast traffic address is 33:33:x:y:z:w.
everywhere, like broadcast.
❖ff02::1
➢All-nodes
➢ff00::/8
➢Ethernet multicast address: 33:33:00:00:00:01.

❖ff02::2
➢All-routers.
➢Ethernet multicast address: 33:33:00:00:00:02.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 31 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 32
 4. IPv6 Multicast
❖IPv6 nodes on Ethernets send LAN-layer Multicast Listener
Discovery (MLD) messages to multicast groups they wish to
start using.
➢These messages allow multicast-aware Ethernet switches
to optimize forwarding so that only those hosts that have
subscribed to the multicast group in question will receive
the messages.
5 IPv6 Extension Headers
➢Otherwise, switches are supposed to treat multicast like
broadcast;
➢Worse case, some switches may simply fail to forward
multicast packets to destinations that have not explicitly
opted to join the group.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 33

5. IPv6 Extension Headers 5. IPv6 Extension Headers

❖Hop-by-Hop options header

❖Destination options header

❖Routing header

❖Fragment header

❖Authentication header

❖Mobility header

❖Encapsulated Security Payload header

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 35 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 36
 5. IPv6 Extension Headers 5. IPv6 Extension Headers
❖Hop-by-Hop options header ❖Destination Options Header
➢Consists of a set of <type,value> pairs which are ➢Consists of a set of <type,value> pairs, and the
intended to be processed by each router on the path. original RFC 2460 specification only defined options for
padding. (similar to the Hop-by-Hop Options header)
o The only Hop-by-Hop options provided by RFC 2460
➢Since RFC 2460, a few more Destination Options
were for padding, so as to set the alignment of later header types have been defined, though none is in
headers. common use.
o RFC 2675 later defined a Hop-by-Hop option to ➢RFC 2473 defined a Destination Options header to limit
support IPv6 jumbograms: datagrams larger than the nesting of tunnels, called the Tunnel Encapsulation
65,535 bytes. Limit.
➢Because this options headers must be processed by each ➢RFC 6275 defines a Destination Options header for use
router encountered, they have the potential to in Mobile IPv6.
overburden the Internet routing system. As a result, RFC ➢RFC 6553, on the Routing Protocol for Low-Power and
6564 strongly discourages new Hop-by-Hop Option Lossy Networks (RPL), has defined a Destination (and
headers, unless examination at every hop is essential. Hop-by-Hop) Options type for carrying RPL data.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 37 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 38

5. IPv6 Extension Headers 5. IPv6 Extension Headers

❖Routing Header ❖Routing Header
➢The original, or Type 0, Routing header contained a list ➢The original, or Type 0, Routing header contained a list
of IPv6 addresses through which the packet should be of IPv6 addresses through which the packet should be
routed. These did not have to be contiguous. routed. These did not have to be contiguous.
o Ex: The list to be visited enroute to destination D was o Ex: (continue)
<R1 ,R2 ,…,Rn>. ▪ The header contained a Segments Left pointer
▪ Then this option
contained header indicating the next address to be processed,
<R2 ,R3 ,…,Rn ,D> with R1 as the initial incremented at each Ri. When the packet arrived
destination address; at D the Routing Header would contain the
▪ R1 then would update this header to <R1 ,R3, routing list <R1 ,R2 ,…,Rn>.
…,Rn ,D>, and would send the packet on to R2. ▪ Note, however, that routers between the listed
▪ This was to continue on until Rn addressed the routers R1 . . . Rn did not need to examine this
packet to the final destination D. header; they processed the packet based only on
its current destination address.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 39 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 40
 5. IPv6 Extension Headers 5. IPv6 Extension Headers
❖Routing Header ❖Routing Header
➢This form of routing header was deprecated by RFC ➢RFC 6275 and RFC 6554 define more limited routing
5095, due to concerns about a traffic-amplification headers.
attack. o RFC 6275 defines a quite limited routing header to
o An attacker could send off a packet with a routing be used for IPv6 mobility (and also defines the IPv6
header containing an alternating list of just two Mobility header).
routers <R1 ,R2 ,R1 ,R2 ,…,R1 ,R2 ,D>. o RFC 6554 routing header used for RPL, mentioned
▪ This would generate substantial traffic on the R1– above, has the same basic form as the Type 0 header
R2 link. described above, but its use is limited to specific low-
power routing domains.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 41 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 42

5. IPv6 Extension Headers

❖IPv6 Fragment Header
➢Contains a 13-bit Fragment Offset field (as in IPv4) and
a 32-bit Identification field.
➢IPv6 fragmentation is done only by the original sender.

6
➢Generally speaking, fragmentation should be avoided at
the application layer when possible. Neighbor Discovery

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 43
 6. Neighbor Discovery 6. Neighbor Discovery
❖A set of related protocols that replaces several IPv4 tools, ❖Router Discovery
most notably ARP, ICMP redirects and most non-address- ➢IPv6 routers periodically send Router Advertisement (RA)
assignment parts of DHCP. packets to the all-nodes multicast group.
o Hosts can request an RA packet immediately by
❖Provides the following services: sending a Router Solicitation (RS) request to the all-
routers multicast group.
➢Finding the local router(s)
➢Finding the set of network address prefixes that can be
reached via local delivery. ➢RA packets contain:
➢Finding a local host’s LAN address, given its IPv6 address. o Identification of the routers,
➢Detecting duplicate IPv6 addresses. o A list of all network address prefixes in use on the
LAN.
➢Determining that some neighbors are now unreachable
o An agreed-on MTU.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 45 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 46

6. Neighbor Discovery 6. Neighbor Discovery

❖ Prefix Discovery ❖ Neighbor Solicitation (Similar to IPv4 ARP requests)
➢Support hosts to learn the network-address prefixes. ➢Sent to the solicited-node multicast address.
o ff02::0001:x.y.z.w.
➢Router Advertisement packets contain a complete list of ▪ x, y, z and w are the low-order 32 bits of the IPv6
valid network-address prefixes, as the Prefix Information address the sender is trying to look up.
option. o Each IPv6 host on the LAN will need to subscribe to
all the solicited-node multicast addresses
➢Each prefix will have an associated lifetime. corresponding to its own IPv6 addresses.
o Nodes receiving a prefix from an RA packet are to use ➢Neighbor Solicitation messages are repeated regularly
it only for the duration of this lifetime. but follow up verifications are initially sent to the unicast
o On expiration a node must obtain a newer RA packet LAN address on file.
with a newer prefix list.
➢The target host’s response to a Neighbor Solicitation
message is called Neighbor Advertisement.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 47 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 48
 7. IPv6 Host Address Assignment
❖IPv6 provides two competing ways for hosts to obtain their
full IP addresses.

➢DHCPv6.

7 IPv6 Host Address Assignment

➢StateLess Address Auto Configuration (SLAAC)

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 50

7. IPv6 Host Address Assignment 7. IPv6 Host Address Assignment

❖Duplicate Address Detection ❖Duplicate Address Detection
➢Whenever an IPv6 host obtains a unicast address it goes ➢A host is not allowed to use an IPv6 address if the DAD
through a duplicate-address detection (DAD) process. process has failed.

➢The host sends one or more Neighbor Solicitation o If the DAD process fails for an address based on an
messages, asking if any other host has this address. EUI-64 identifier, then some other node has the same
o If anyone answers, then the address is a duplicate. Ethernet address and you have bigger problems than
just finding a working IPv6 address.

o If the DAD process fails for an address constructed

with the Interface identifiers, the host is able to
generate a new interface identifier and try again.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 51 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 52
 7. IPv6 Host Address Assignment 7. IPv6 Host Address Assignment
❖Stateless Autoconfiguration (SLAAC) ❖Stateless Autoconfiguration (SLAAC)
➢Host generates its link-local address, appending the ➢If there is a router available.
standard 64-bit link-local prefix fe80::/64 to its interface o The host send a RS message.
identifier. o A router answers with a RA message that contains a
➢Derived from the host’s LAN address using either EUI-64 Prefix Information option.
or the RFC 7217 mechanism. ▪ RA message will mark with a flag those prefixes
eligible for use with SLAAC.
▪ All prefixes will also be marked with a lifetime.
o The host chooses an appropriate prefix, stores the
prefix-lifetime information, and appends the prefix to
the front of its interface identifier
▪ This is a routable address.
➢Do DAD.
o Do DAD.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 53 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 54

7. IPv6 Host Address Assignment 7. IPv6 Host Address Assignment

❖Stateless Autoconfiguration (SLAAC) ❖DHCPv6
➢The host knows its IPv6 address and its default router ➢Similar to IPv4, host automatically receives addressing
but no DNS server. information including a global unicast address, prefix
length, default gateway address and DNS server
o In RFC 6106 now defines a process by which IPv6 addresses
routers can include DNS-server information in the RA ➢Device receives all or some of its IPv6 addressing
packets they send to hosts as part of the SLAAC information from a DHCPv6 server depending upon
process. option 2 (SLAAC and DHCPv6) or option 3 (DHCPv6 only)
is specified in the ICMPv6 RA message.

➢A device may obtain its IPv6 global unicast address

dynamically and also be configured with multiple static
IPv6 addresses on the same interface.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 55 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 56
 7. IPv6 Host Address Assignment 7. IPv6 Host Address Assignment
❖DHCPv6

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 57 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 58

8. ICMPv6
❖As part of the Neighbor Discovery Protocol.

❖Messages are identified by 8-bit type and code (subtype)

fields.

8 ICMPv6 ❖Distinguishes between informational and error messages by

the first bit of the type field.

❖ICMPv6 includes an IPv6 version of Echo Request/Echo

Reply, upon which the “ping6” command.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 60
 8. ICMPv6 8. ICMPv6
❖Destination Unreachable ❖Destination Unreachable
➢In this case, one of the following numeric codes is returned: ➢In this case, one of the following numeric codes is returned:
0: No route to destination, returned when a router has 3: Address unreachable, a catchall category for routing
no next_hop entry. failure not covered by any other message. An example is if
the packet was successfully routed to the last_hop router,
1: Communication with destination administratively but Neighbor Discovery failed to find a LAN address
prohibited, returned when a router has a next_hop entry, corresponding to the IPv6 address.
but declines to use it for policy reasons. Codes 5 and 6,
below, are special cases of this situation; these more- 4: Port unreachable, returned when, as in ICMPv4, the
specific codes are returned when appropriate. destination host does not have the requested UDP port
2: Beyond scope of source address, returned when a open.
router is, for example, asked to route a packet to a global
address, but the return address is not, e.g., is unique-local. 5: Source address failed ingress/egress policy, see
In IPv4, when a host with a private address attempts to code 1
connect to a global address, NAT is almost always involved.
6: Reject route to destination, see code 1.
Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 61 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 62

8. ICMPv6
❖Packet Too Big
➢This is like ICMPv4’s “Fragmentation Required but Don’t
Fragment flag set”; IPv6 however has no router-based
fragmentation.

❖Time Exceeded
➢This is used for cases where the Hop Limit was exceeded,
and also where source-based fragmentation was 9 IPv6 Subnets
used and the fragment-reassembly timer expired.

❖Parameter Problem
➢This is used when there is a malformed entry in the IPv6
header, an unrecognized Next Header type, or an
unrecognized IPv6 option.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 63
 9. IPv6 Subnets 9. IPv6 Subnets
❖In IPv6, this is much simpler: all subnets are of size /64. ❖If users are given only “/64” blocks, and they want to use
➢There is one common exception: RFC 6164 permits the subnets.
use of 127-bit prefixes at each end of a point-to-point ➢They have to break the 64/64 rule locally.
link. The 128th bit is then 0 at one end and 1 at the other. o Perhaps they can create four subnets each with a
prefix of length 66 bits, and each with only 62 bits for
❖A site receiving from its provider an address prefix of size the host identifier.
/56 can assign up to 256 “/64 subnets”. o Wanting to do that in a standard way would dictate
more flexibility in the prefix/host division.

Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 65 Lecturer: Nguyen Viet Ha, Ph.D. - Department of Telecommunications and Networks, FETEL, HCMUS 66

QA

Lecturer: Nguyen Viet Ha, Ph.D.

Ho Chi Minh City University of Science
Faculty of Electronics and Communications
Department of Telecommunication and Networks
Email: nvha@[Link]