Debian Codegraph @

rfc2463.html

raw
1 <pre>Network Working Group A. Conta
2 Request for Comments: 2463 Lucent
3 Obsoletes: <a href="./rfc1885">1885</a> S. Deering
4 Category: Standards Track Cisco Systems
5 December 1998
6
7
8 <span class="h1">Internet Control Message Protocol (ICMPv6)</span>
9 <span class="h1">for the Internet Protocol Version 6 (IPv6)</span>
10 <span class="h1">Specification</span>
11
12 Status of this Memo
13
14 This document specifies an Internet standards track protocol for the
15 Internet community, and requests discussion and suggestions for
16 improvements. Please refer to the current edition of the "Internet
17 Official Protocol Standards" (STD 1) for the standardization state
18 and status of this protocol. Distribution of this memo is unlimited.
19
20 Copyright Notice
21
22 Copyright (C) The Internet Society (1998). All Rights Reserved.
23
24 Abstract
25
26 This document specifies a set of Internet Control Message Protocol
27 (ICMP) messages for use with version 6 of the Internet Protocol
28 (IPv6).
29
30 Table of Contents
31
32 <a href="#section-1">1</a>. Introduction........................................<a href="#page-2">2</a>
33 <a href="#section-2">2</a>. ICMPv6 (ICMP for IPv6)..............................<a href="#page-2">2</a>
34 <a href="#section-2.1">2.1</a> Message General Format.......................<a href="#page-2">2</a>
35 <a href="#section-2.2">2.2</a> Message Source Address Determination.........<a href="#page-3">3</a>
36 <a href="#section-2.3">2.3</a> Message Checksum Calculation.................<a href="#page-4">4</a>
37 <a href="#section-2.4">2.4</a> Message Processing Rules.....................<a href="#page-4">4</a>
38 <a href="#section-3">3</a>. ICMPv6 Error Messages...............................<a href="#page-6">6</a>
39 <a href="#section-3.1">3.1</a> Destination Unreachable Message..............<a href="#page-6">6</a>
40 <a href="#section-3.2">3.2</a> Packet Too Big Message...................... <a href="#page-8">8</a>
41 <a href="#section-3.3">3.3</a> Time Exceeded Message....................... <a href="#page-9">9</a>
42 <a href="#section-3.4">3.4</a> Parameter Problem Message...................<a href="#page-10">10</a>
43 <a href="#section-4">4</a>. ICMPv6 Informational Messages......................<a href="#page-11">11</a>
44 <a href="#section-4.1">4.1</a> Echo Request Message........................<a href="#page-11">11</a>
45 <a href="#section-4.2">4.2</a> Echo Reply Message..........................<a href="#page-12">12</a>
46 <a href="#section-5">5</a>. Security Considerations............................<a href="#page-13">13</a>
47 <a href="#section-6">6</a>. References.........................................<a href="#page-14">14</a>
48 <a href="#section-7">7</a>. Acknowledgments....................................<a href="#page-15">15</a>
49
50
51
52 <span class="grey">Conta &amp; Deering Standards Track [Page 1]</span></pre>
53 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span>
54 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
55
56
57 <a href="#section-8">8</a>. Authors' Addresses.................................<a href="#page-16">16</a>
58 <a href="#appendix-A">Appendix A</a> - Changes since <a href="./rfc1885">RFC 1885</a>...................<a href="#page-17">17</a>
59 Full Copyright Statement..............................<a href="#page-18">18</a>
60
61 <span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span>
62
63 The Internet Protocol, version 6 (IPv6) is a new version of IP. IPv6
64 uses the Internet Control Message Protocol (ICMP) as defined for IPv4
65 [<a href="./rfc792" title="&quot;Internet Control Message Protocol&quot;">RFC-792</a>], with a number of changes. The resulting protocol is
66 called ICMPv6, and has an IPv6 Next Header value of 58.
67
68 This document describes the format of a set of control messages used
69 in ICMPv6. It does not describe the procedures for using these
70 messages to achieve functions like Path MTU discovery; such
71 procedures are described in other documents (e.g., [<a href="#ref-PMTU" title="&quot;Path MTU Discovery for IP version 6&quot;">PMTU</a>]). Other
72 documents may also introduce additional ICMPv6 message types, such as
73 Neighbor Discovery messages [<a href="#ref-IPv6-DISC" title="&quot;Neighbor Discovery for IP Version 6 (IPv6)&quot;">IPv6-DISC</a>], subject to the general rules
74 for ICMPv6 messages given in <a href="#section-2">section 2</a> of this document.
75
76 Terminology defined in the IPv6 specification [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] and the IPv6
77 Routing and Addressing specification [<a href="#ref-IPv6-ADDR" title="&quot;IP Version 6 Addressing Architecture&quot;">IPv6-ADDR</a>] applies to this
78 document as well.
79
80 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
81 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
82 document are to be interpreted as described in [<a href="./rfc2119" title="&quot;Key words for use in RFCs to Indicate Requirement Levels&quot;">RFC-2119</a>].
83
84 <span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. ICMPv6 (ICMP for IPv6)</span>
85
86 ICMPv6 is used by IPv6 nodes to report errors encountered in
87 processing packets, and to perform other internet-layer functions,
88 such as diagnostics (ICMPv6 "ping"). ICMPv6 is an integral part of
89 IPv6 and MUST be fully implemented by every IPv6 node.
90
91 <span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a> Message General Format</span>
92
93 ICMPv6 messages are grouped into two classes: error messages and
94 informational messages. Error messages are identified as such by
95 having a zero in the high-order bit of their message Type field
96 values. Thus, error messages have message Types from 0 to 127;
97 informational messages have message Types from 128 to 255.
98
99 This document defines the message formats for the following ICMPv6
100 messages:
101
102
103
104
105
106
107
108 <span class="grey">Conta &amp; Deering Standards Track [Page 2]</span></pre>
109 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span>
110 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
111
112
113 ICMPv6 error messages:
114
115 1 Destination Unreachable (see <a href="#section-3.1">section 3.1</a>)
116 2 Packet Too Big (see <a href="#section-3.2">section 3.2</a>)
117 3 Time Exceeded (see <a href="#section-3.3">section 3.3</a>)
118 4 Parameter Problem (see <a href="#section-3.4">section 3.4</a>)
119
120 ICMPv6 informational messages:
121
122 128 Echo Request (see <a href="#section-4.1">section 4.1</a>)
123 129 Echo Reply (see <a href="#section-4.2">section 4.2</a>)
124
125
126 Every ICMPv6 message is preceded by an IPv6 header and zero or more
127 IPv6 extension headers. The ICMPv6 header is identified by a Next
128 Header value of 58 in the immediately preceding header. (NOTE: this
129 is different than the value used to identify ICMP for IPv4.)
130
131 The ICMPv6 messages have the following general format:
132
133 0 1 2 3
134 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
135 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
136 | Type | Code | Checksum |
137 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
138 | |
139 + Message Body +
140 | |
141
142 The type field indicates the type of the message. Its value
143 determines the format of the remaining data.
144
145 The code field depends on the message type. It is used to create an
146 additional level of message granularity.
147
148 The checksum field is used to detect data corruption in the ICMPv6
149 message and parts of the IPv6 header.
150
151 <span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a> Message Source Address Determination</span>
152
153 A node that sends an ICMPv6 message has to determine both the Source
154 and Destination IPv6 Addresses in the IPv6 header before calculating
155 the checksum. If the node has more than one unicast address, it must
156 choose the Source Address of the message as follows:
157
158 (a) If the message is a response to a message sent to one of the
159 node's unicast addresses, the Source Address of the reply must
160 be that same address.
161
162
163
164 <span class="grey">Conta &amp; Deering Standards Track [Page 3]</span></pre>
165 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span>
166 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
167
168
169 (b) If the message is a response to a message sent to a multicast or
170 anycast group in which the node is a member, the Source Address
171 of the reply must be a unicast address belonging to the
172 interface on which the multicast or anycast packet was received.
173
174 (c) If the message is a response to a message sent to an address
175 that does not belong to the node, the Source Address should be
176 that unicast address belonging to the node that will be most
177 helpful in diagnosing the error. For example, if the message is
178 a response to a packet forwarding action that cannot complete
179 successfully, the Source Address should be a unicast address
180 belonging to the interface on which the packet forwarding
181 failed.
182
183 (d) Otherwise, the node's routing table must be examined to
184 determine which interface will be used to transmit the message
185 to its destination, and a unicast address belonging to that
186 interface must be used as the Source Address of the message.
187
188 <span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a> Message Checksum Calculation</span>
189
190 The checksum is the 16-bit one's complement of the one's complement
191 sum of the entire ICMPv6 message starting with the ICMPv6 message
192 type field, prepended with a "pseudo-header" of IPv6 header fields,
193 as specified in [IPv6, <a href="#section-8.1">section 8.1</a>]. The Next Header value used in
194 the pseudo-header is 58. (NOTE: the inclusion of a pseudo-header in
195 the ICMPv6 checksum is a change from IPv4; see [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] for the
196 rationale for this change.)
197
198 For computing the checksum, the checksum field is set to zero.
199
200 <span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a> Message Processing Rules</span>
201
202 Implementations MUST observe the following rules when processing
203 ICMPv6 messages (from [<a href="./rfc1122" title="&quot;Requirements for Internet Hosts - Communication Layers&quot;">RFC-1122</a>]):
204
205 (a) If an ICMPv6 error message of unknown type is received, it MUST
206 be passed to the upper layer.
207
208 (b) If an ICMPv6 informational message of unknown type is received,
209 it MUST be silently discarded.
210
211 (c) Every ICMPv6 error message (type &lt; 128) includes as much of the
212 IPv6 offending (invoking) packet (the packet that caused the
213 error) as will fit without making the error message packet
214 exceed the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>].
215
216
217
218
219
220 <span class="grey">Conta &amp; Deering Standards Track [Page 4]</span></pre>
221 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span>
222 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
223
224
225 (d) In those cases where the internet-layer protocol is required to
226 pass an ICMPv6 error message to the upper-layer process, the
227 upper-layer protocol type is extracted from the original packet
228 (contained in the body of the ICMPv6 error message) and used to
229 select the appropriate upper-layer process to handle the error.
230
231 If the original packet had an unusually large amount of
232 extension headers, it is possible that the upper-layer protocol
233 type may not be present in the ICMPv6 message, due to truncation
234 of the original packet to meet the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>]
235 limit. In that case, the error message is silently dropped
236 after any IPv6-layer processing.
237
238 (e) An ICMPv6 error message MUST NOT be sent as a result of
239 receiving:
240
241 (e.1) an ICMPv6 error message, or
242
243 (e.2) a packet destined to an IPv6 multicast address (there are
244 two exceptions to this rule: (1) the Packet Too Big
245 Message - <a href="#section-3.2">Section 3.2</a> - to allow Path MTU discovery to
246 work for IPv6 multicast, and (2) the Parameter Problem
247 Message, Code 2 - <a href="#section-3.4">Section 3.4</a> - reporting an unrecognized
248 IPv6 option that has the Option Type highest-order two
249 bits set to 10), or
250
251 (e.3) a packet sent as a link-layer multicast, (the exception
252 from e.2 applies to this case too), or
253
254 (e.4) a packet sent as a link-layer broadcast, (the exception
255 from e.2 applies to this case too), or
256
257 (e.5) a packet whose source address does not uniquely identify
258 a single node -- e.g., the IPv6 Unspecified Address, an
259 IPv6 multicast address, or an address known by the ICMP
260 message sender to be an IPv6 anycast address.
261
262 (f) Finally, in order to limit the bandwidth and forwarding costs
263 incurred sending ICMPv6 error messages, an IPv6 node MUST limit
264 the rate of ICMPv6 error messages it sends. This situation may
265 occur when a source sending a stream of erroneous packets fails
266 to heed the resulting ICMPv6 error messages. There are a
267 variety of ways of implementing the rate-limiting function, for
268 example:
269
270 (f.1) Timer-based - for example, limiting the rate of
271 transmission of error messages to a given source, or to
272 any source, to at most once every T milliseconds.
273
274
275
276 <span class="grey">Conta &amp; Deering Standards Track [Page 5]</span></pre>
277 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span>
278 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
279
280
281 (f.2) Bandwidth-based - for example, limiting the rate at which
282 error messages are sent from a particular interface to
283 some fraction F of the attached link's bandwidth.
284
285 The limit parameters (e.g., T or F in the above examples) MUST
286 be configurable for the node, with a conservative default value
287 (e.g., T = 1 second, NOT 0 seconds, or F = 2 percent, NOT 100
288 percent).
289
290 The following sections describe the message formats for the above
291 ICMPv6 messages.
292
293 <span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. ICMPv6 Error Messages</span>
294
295 <span class="h3"><a class="selflink" id="section-3.1" href="#section-3.1">3.1</a> Destination Unreachable Message</span>
296
297 0 1 2 3
298 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
299 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
300 | Type | Code | Checksum |
301 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
302 | Unused |
303 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
304 | As much of invoking packet |
305 + as will fit without the ICMPv6 packet +
306 | exceeding the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] |
307
308 IPv6 Fields:
309
310 Destination Address
311
312 Copied from the Source Address field of the invoking
313 packet.
314
315 ICMPv6 Fields:
316
317 Type 1
318
319 Code 0 - no route to destination
320 1 - communication with destination
321 administratively prohibited
322 2 - (not assigned)
323 3 - address unreachable
324 4 - port unreachable
325
326 Unused This field is unused for all code values.
327 It must be initialized to zero by the sender
328 and ignored by the receiver.
329
330
331
332 <span class="grey">Conta &amp; Deering Standards Track [Page 6]</span></pre>
333 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span>
334 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
335
336
337 Description
338
339 A Destination Unreachable message SHOULD be generated by a router, or
340 by the IPv6 layer in the originating node, in response to a packet
341 that cannot be delivered to its destination address for reasons other
342 than congestion. (An ICMPv6 message MUST NOT be generated if a
343 packet is dropped due to congestion.)
344
345 If the reason for the failure to deliver is lack of a matching entry
346 in the forwarding node's routing table, the Code field is set to 0
347 (NOTE: this error can occur only in nodes that do not hold a "default
348 route" in their routing tables).
349
350 If the reason for the failure to deliver is administrative
351 prohibition, e.g., a "firewall filter", the Code field is set to 1.
352
353 If there is any other reason for the failure to deliver, e.g.,
354 inability to resolve the IPv6 destination address into a
355 corresponding link address, or a link-specific problem of some sort,
356 then the Code field is set to 3.
357
358 A destination node SHOULD send a Destination Unreachable message with
359 Code 4 in response to a packet for which the transport protocol
360 (e.g., UDP) has no listener, if that transport protocol has no
361 alternative means to inform the sender.
362
363 Upper layer notification
364
365 A node receiving the ICMPv6 Destination Unreachable message MUST
366 notify the upper-layer process.
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388 <span class="grey">Conta &amp; Deering Standards Track [Page 7]</span></pre>
389 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span>
390 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
391
392
393 <span class="h3"><a class="selflink" id="section-3.2" href="#section-3.2">3.2</a> Packet Too Big Message</span>
394
395 0 1 2 3
396 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
397 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
398 | Type | Code | Checksum |
399 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
400 | MTU |
401 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
402 | As much of invoking packet |
403 + as will fit without the ICMPv6 packet +
404 | exceeding the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] |
405
406 IPv6 Fields:
407
408 Destination Address
409
410 Copied from the Source Address field of the invoking
411 packet.
412
413 ICMPv6 Fields:
414
415 Type 2
416
417 Code Set to 0 (zero) by the sender and ignored by the
418 receiver
419
420 MTU The Maximum Transmission Unit of the next-hop link.
421
422 Description
423
424 A Packet Too Big MUST be sent by a router in response to a packet
425 that it cannot forward because the packet is larger than the MTU of
426 the outgoing link. The information in this message is used as part
427 of the Path MTU Discovery process [<a href="#ref-PMTU" title="&quot;Path MTU Discovery for IP version 6&quot;">PMTU</a>].
428
429 Sending a Packet Too Big Message makes an exception to one of the
430 rules of when to send an ICMPv6 error message, in that unlike other
431 messages, it is sent in response to a packet received with an IPv6
432 multicast destination address, or a link-layer multicast or link-
433 layer broadcast address.
434
435 Upper layer notification
436
437 An incoming Packet Too Big message MUST be passed to the upper-layer
438 process.
439
440
441
442
443
444 <span class="grey">Conta &amp; Deering Standards Track [Page 8]</span></pre>
445 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span>
446 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
447
448
449 <span class="h3"><a class="selflink" id="section-3.3" href="#section-3.3">3.3</a> Time Exceeded Message</span>
450
451 0 1 2 3
452 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
453 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
454 | Type | Code | Checksum |
455 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
456 | Unused |
457 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
458 | As much of invoking packet |
459 + as will fit without the ICMPv6 packet +
460 | exceeding the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] |
461
462 IPv6 Fields:
463
464 Destination Address
465 Copied from the Source Address field of the invoking
466 packet.
467
468 ICMPv6 Fields:
469
470 Type 3
471
472 Code 0 - hop limit exceeded in transit
473
474 1 - fragment reassembly time exceeded
475
476 Unused This field is unused for all code values.
477 It must be initialized to zero by the sender
478 and ignored by the receiver.
479
480 Description
481
482 If a router receives a packet with a Hop Limit of zero, or a router
483 decrements a packet's Hop Limit to zero, it MUST discard the packet
484 and send an ICMPv6 Time Exceeded message with Code 0 to the source of
485 the packet. This indicates either a routing loop or too small an
486 initial Hop Limit value.
487
488 The rules for selecting the Source Address of this message are
489 defined in <a href="#section-2.2">section 2.2</a>.
490
491 Upper layer notification
492
493 An incoming Time Exceeded message MUST be passed to the upper-layer
494 process.
495
496
497
498
499
500 <span class="grey">Conta &amp; Deering Standards Track [Page 9]</span></pre>
501 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span>
502 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
503
504
505 <span class="h3"><a class="selflink" id="section-3.4" href="#section-3.4">3.4</a> Parameter Problem Message</span>
506
507 0 1 2 3
508 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
509 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
510 | Type | Code | Checksum |
511 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
512 | Pointer |
513 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
514 | As much of invoking packet |
515 + as will fit without the ICMPv6 packet +
516 | exceeding the minimum IPv6 MTU [<a href="#ref-IPv6" title="&quot;Internet Protocol, Version 6, (IPv6) Specification&quot;">IPv6</a>] |
517
518 IPv6 Fields:
519
520 Destination Address
521
522 Copied from the Source Address field of the invoking
523 packet.
524
525 ICMPv6 Fields:
526
527 Type 4
528
529 Code 0 - erroneous header field encountered
530
531 1 - unrecognized Next Header type encountered
532
533 2 - unrecognized IPv6 option encountered
534
535 Pointer Identifies the octet offset within the
536 invoking packet where the error was detected.
537
538 The pointer will point beyond the end of the ICMPv6
539 packet if the field in error is beyond what can fit
540 in the maximum size of an ICMPv6 error message.
541
542 Description
543
544 If an IPv6 node processing a packet finds a problem with a field in
545 the IPv6 header or extension headers such that it cannot complete
546 processing the packet, it MUST discard the packet and SHOULD send an
547 ICMPv6 Parameter Problem message to the packet's source, indicating
548 the type and location of the problem.
549
550 The pointer identifies the octet of the original packet's header
551 where the error was detected. For example, an ICMPv6 message with
552 Type field = 4, Code field = 1, and Pointer field = 40 would indicate
553
554
555
556 <span class="grey">Conta &amp; Deering Standards Track [Page 10]</span></pre>
557 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-11" ></span>
558 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
559
560
561 that the IPv6 extension header following the IPv6 header of the
562 original packet holds an unrecognized Next Header field value.
563
564 Upper layer notification
565
566 A node receiving this ICMPv6 message MUST notify the upper-layer
567 process.
568
569 <span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. ICMPv6 Informational Messages</span>
570
571 <span class="h3"><a class="selflink" id="section-4.1" href="#section-4.1">4.1</a> Echo Request Message</span>
572
573 0 1 2 3
574 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
575 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
576 | Type | Code | Checksum |
577 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
578 | Identifier | Sequence Number |
579 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
580 | Data ...
581 +-+-+-+-+-
582
583 IPv6 Fields:
584
585 Destination Address
586
587 Any legal IPv6 address.
588
589 ICMPv6 Fields:
590
591 Type 128
592
593 Code 0
594
595 Identifier An identifier to aid in matching Echo Replies
596 to this Echo Request. May be zero.
597
598 Sequence Number
599
600 A sequence number to aid in matching Echo Replies
601 to this Echo Request. May be zero.
602
603 Data Zero or more octets of arbitrary data.
604
605
606
607
608
609
610
611
612 <span class="grey">Conta &amp; Deering Standards Track [Page 11]</span></pre>
613 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-12" ></span>
614 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
615
616
617 Description
618
619 Every node MUST implement an ICMPv6 Echo responder function that
620 receives Echo Requests and sends corresponding Echo Replies. A node
621 SHOULD also implement an application-layer interface for sending Echo
622 Requests and receiving Echo Replies, for diagnostic purposes.
623
624 Upper layer notification
625
626 Echo Request messages MAY be passed to processes receiving ICMP
627 messages.
628
629 <span class="h3"><a class="selflink" id="section-4.2" href="#section-4.2">4.2</a> Echo Reply Message</span>
630
631 0 1 2 3
632 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
633 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
634 | Type | Code | Checksum |
635 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
636 | Identifier | Sequence Number |
637 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
638 | Data ...
639 +-+-+-+-+-
640
641 IPv6 Fields:
642
643 Destination Address
644
645 Copied from the Source Address field of the invoking
646 Echo Request packet.
647
648 ICMPv6 Fields:
649
650 Type 129
651
652 Code 0
653
654 Identifier The identifier from the invoking Echo Request message.
655
656 Sequence The sequence number from the invoking Echo Request
657 Number message.
658
659 Data The data from the invoking Echo Request message.
660
661
662
663
664
665
666
667
668 <span class="grey">Conta &amp; Deering Standards Track [Page 12]</span></pre>
669 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-13" ></span>
670 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
671
672
673 Description
674
675 Every node MUST implement an ICMPv6 Echo responder function that
676 receives Echo Requests and sends corresponding Echo Replies. A node
677 SHOULD also implement an application-layer interface for sending Echo
678 Requests and receiving Echo Replies, for diagnostic purposes.
679
680 The source address of an Echo Reply sent in response to a unicast
681 Echo Request message MUST be the same as the destination address of
682 that Echo Request message.
683
684 An Echo Reply SHOULD be sent in response to an Echo Request message
685 sent to an IPv6 multicast address. The source address of the reply
686 MUST be a unicast address belonging to the interface on which the
687 multicast Echo Request message was received.
688
689 The data received in the ICMPv6 Echo Request message MUST be returned
690 entirely and unmodified in the ICMPv6 Echo Reply message.
691
692 Upper layer notification
693
694 Echo Reply messages MUST be passed to the process that originated an
695 Echo Request message. It may be passed to processes that did not
696 originate the Echo Request message.
697
698 <span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Security Considerations</span>
699
700 <span class="h3"><a class="selflink" id="section-5.1" href="#section-5.1">5.1</a> Authentication and Encryption of ICMP messages</span>
701
702 ICMP protocol packet exchanges can be authenticated using the IP
703 Authentication Header [IPv6-AUTH]. A node SHOULD include an
704 Authentication Header when sending ICMP messages if a security
705 association for use with the IP Authentication Header exists for the
706 destination address. The security associations may have been created
707 through manual configuration or through the operation of some key
708 management protocol.
709
710 Received Authentication Headers in ICMP packets MUST be verified for
711 correctness and packets with incorrect authentication MUST be ignored
712 and discarded.
713
714 It SHOULD be possible for the system administrator to configure a
715 node to ignore any ICMP messages that are not authenticated using
716 either the Authentication Header or Encapsulating Security Payload.
717 Such a switch SHOULD default to allowing unauthenticated messages.
718
719
720
721
722
723
724 <span class="grey">Conta &amp; Deering Standards Track [Page 13]</span></pre>
725 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-14" ></span>
726 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
727
728
729 Confidentiality issues are addressed by the IP Security Architecture
730 and the IP Encapsulating Security Payload documents [IPv6-SA, IPv6-
731 ESP].
732
733 <span class="h3"><a class="selflink" id="section-5.2" href="#section-5.2">5.2</a> ICMP Attacks</span>
734
735 ICMP messages may be subject to various attacks. A complete
736 discussion can be found in the IP Security Architecture [<a href="#ref-IPv6-SA" title="&quot;Security Architecture for the Internet Protocol&quot;">IPv6-SA</a>]. A
737 brief discussion of such attacks and their prevention is as follows:
738
739 1. ICMP messages may be subject to actions intended to cause the
740 receiver believe the message came from a different source than the
741 message originator. The protection against this attack can be
742 achieved by applying the IPv6 Authentication mechanism [<a href="#ref-IPv6-Auth" title="&quot;IP Authentication Header&quot;">IPv6-Auth</a>]
743 to the ICMP message.
744
745 2. ICMP messages may be subject to actions intended to cause the
746 message or the reply to it go to a destination different than the
747 message originator's intention. The ICMP checksum calculation
748 provides a protection mechanism against changes by a malicious
749 interceptor in the destination and source address of the IP packet
750 carrying that message, provided the ICMP checksum field is
751 protected against change by authentication [<a href="#ref-IPv6-Auth" title="&quot;IP Authentication Header&quot;">IPv6-Auth</a>] or
752 encryption [<a href="#ref-IPv6-ESP" title="&quot;IP Encapsulating Security Protocol (ESP)&quot;">IPv6-ESP</a>] of the ICMP message.
753
754 3. ICMP messages may be subject to changes in the message fields, or
755 payload. The authentication [<a href="#ref-IPv6-Auth" title="&quot;IP Authentication Header&quot;">IPv6-Auth</a>] or encryption [<a href="#ref-IPv6-ESP" title="&quot;IP Encapsulating Security Protocol (ESP)&quot;">IPv6-ESP</a>]
756 of the ICMP message is a protection against such actions.
757
758 4. ICMP messages may be used as attempts to perform denial of service
759 attacks by sending back to back erroneous IP packets. An
760 implementation that correctly followed <a href="#section-2.4">section 2.4</a>, paragraph (f)
761 of this specifications, would be protected by the ICMP error rate
762 limiting mechanism.
763
764 <span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span>
765
766 [<a id="ref-IPv6">IPv6</a>] Deering, S. and R. Hinden, "Internet Protocol, Version
767 6, (IPv6) Specification", <a href="./rfc2460">RFC 2460</a>, December 1998.
768
769 [<a id="ref-IPv6-ADDR">IPv6-ADDR</a>] Hinden, R. and S. Deering, "IP Version 6 Addressing
770 Architecture", <a href="./rfc2373">RFC 2373</a>, July 1998.
771
772 [<a id="ref-IPv6-DISC">IPv6-DISC</a>] Narten, T., Nordmark, E. and W. Simpson, "Neighbor
773 Discovery for IP Version 6 (IPv6)", <a href="./rfc2461">RFC 2461</a>, December
774 1998.
775
776
777
778
779
780 <span class="grey">Conta &amp; Deering Standards Track [Page 14]</span></pre>
781 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-15" ></span>
782 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
783
784
785 [<a id="ref-RFC-792">RFC-792</a>] Postel, J., "Internet Control Message Protocol", STD 5,
786 <a href="./rfc792">RFC 792</a>, September 1981.
787
788 [<a id="ref-RFC-1122">RFC-1122</a>] Braden, R., "Requirements for Internet Hosts -
789 Communication Layers", STD 5, <a href="./rfc1122">RFC 1122</a>, August 1989.
790
791 [<a id="ref-PMTU">PMTU</a>] McCann, J., Deering, S. and J. Mogul, "Path MTU
792 Discovery for IP version 6", <a href="./rfc1981">RFC 1981</a>, August 1996.
793
794 [<a id="ref-RFC-2119">RFC-2119</a>] Bradner, S., "Key words for use in RFCs to Indicate
795 Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997.
796
797 [<a id="ref-IPv6-SA">IPv6-SA</a>] Kent, S. and R. Atkinson, "Security Architecture for the
798 Internet Protocol", <a href="./rfc2401">RFC 2401</a>, November 1998.
799
800 [<a id="ref-IPv6-Auth">IPv6-Auth</a>] Kent, S. and R. Atkinson, "IP Authentication Header",
801 <a href="./rfc2402">RFC 2402</a>, November 1998.
802
803 [<a id="ref-IPv6-ESP">IPv6-ESP</a>] Kent, S. and R. Atkinson, "IP Encapsulating Security
804 Protocol (ESP)", <a href="./rfc2406">RFC 2406</a>, November 1998.
805
806 <span class="h2"><a class="selflink" id="section-7" href="#section-7">7</a>. Acknowledgments</span>
807
808 The document is derived from previous ICMP drafts of the SIPP and
809 IPng working group.
810
811 The IPng working group and particularly Robert Elz, Jim Bound, Bill
812 Simpson, Thomas Narten, Charlie Lynn, Bill Fink, Scott Bradner,
813 Dimitri Haskin, and Bob Hinden (in chronological order) provided
814 extensive review information and feedback.
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836 <span class="grey">Conta &amp; Deering Standards Track [Page 15]</span></pre>
837 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-16" ></span>
838 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
839
840
841 <span class="h2"><a class="selflink" id="section-8" href="#section-8">8</a>. Authors' Addresses</span>
842
843 Alex Conta
844 Lucent Technologies Inc.
845 300 Baker Ave, Suite 100
846 Concord, MA 01742
847 USA
848
849 Phone: +1 978 287-2842
850 EMail: [email protected]
851
852
853 Stephen Deering
854 Cisco Systems, Inc.
855 170 West Tasman Drive
856 San Jose, CA 95134-1706
857 USA
858
859 Phone: +1 408 527-8213
860 EMail: [email protected]
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892 <span class="grey">Conta &amp; Deering Standards Track [Page 16]</span></pre>
893 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-17" ></span>
894 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
895
896
897 Appendix A - Changes from <a href="./rfc1885">RFC 1885</a>
898
899 Version 2-02
900
901 - Excluded mentioning informational replies from paragraph (f.2) of
902 <a href="#section-2.4">section 2.4</a>.
903 - In "Upper layer notification" sections changed "upper-layer
904 protocol" and "User Interface" to "process".
905 - Changed <a href="#section-5.2">section 5.2</a>, item 2 and 3 to also refer to AH
906 authentication.
907 - Removed item 5. from <a href="#section-5.2">section 5.2</a> on denial of service attacks.
908 - Updated phone numbers and Email addresses in the "Authors'
909 Addresses" section.
910
911 Version 2-01
912
913 - Replaced all references to "576 octets" as the maximum for an ICMP
914 message size with "minimum IPv6 MTU" as defined by the base IPv6
915 specification.
916 - Removed rate control from informational messages.
917 - Added requirement that receivers ignore Code value in Packet Too
918 Big message.
919 - Removed "Not a Neighbor" (code 2) from destination unreachable
920 message.
921 - Fixed typos and update references.
922
923 Version 2-00
924
925 - Applied rate control to informational messages
926 - Removed <a href="#section-2.4">section 2.4</a> on Group Management ICMP messages
927 - Removed references to IGMP in Abstract and <a href="#section-1">Section 1</a>.
928 - Updated references to other IPv6 documents
929 - Removed references to <a href="./rfc1112">RFC-1112</a> in Abstract, and <a href="#section-1">Section 1</a>, and to
930 <a href="./rfc1191">RFC-1191</a> in <a href="#section-1">section 1</a>, and <a href="#section-3.2">section 3.2</a>
931 - Added security section
932 - Added <a href="#appendix-A">Appendix A</a> - changes
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948 <span class="grey">Conta &amp; Deering Standards Track [Page 17]</span></pre>
949 <hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-18" ></span>
950 <span class="grey"><a href="./rfc2463">RFC 2463</a> ICMPv6 (ICMP for IPv6) December 1998</span>
951
952
953 Full Copyright Statement
954
955 Copyright (C) The Internet Society (1998). All Rights Reserved.
956
957 This document and translations of it may be copied and furnished to
958 others, and derivative works that comment on or otherwise explain it
959 or assist in its implementation may be prepared, copied, published
960 and distributed, in whole or in part, without restriction of any
961 kind, provided that the above copyright notice and this paragraph are
962 included on all such copies and derivative works. However, this
963 document itself may not be modified in any way, such as by removing
964 the copyright notice or references to the Internet Society or other
965 Internet organizations, except as needed for the purpose of
966 developing Internet standards in which case the procedures for
967 copyrights defined in the Internet Standards process must be
968 followed, or as required to translate it into languages other than
969 English.
970
971 The limited permissions granted above are perpetual and will not be
972 revoked by the Internet Society or its successors or assigns.
973
974 This document and the information contained herein is provided on an
975 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
976 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
977 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
978 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
979 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
1001
1002
1003
1004 Conta &amp; Deering Standards Track [Page 18]
1005 </pre>