| 1 |
<pre>Internet Engineering Task Force (IETF) M. Shore |
| 2 |
Request for Comments: 7279 No Mountain Software |
| 3 |
BCP: 189 C. Pignataro |
| 4 |
Category: Best Current Practice Cisco Systems, Inc. |
| 5 |
ISSN: 2070-1721 May 2014 |
| 6 |
|
| 7 |
|
| 8 |
<span class="h1">An Acceptable Use Policy for New ICMP Types and Codes</span> |
| 9 |
|
| 10 |
Abstract |
| 11 |
|
| 12 |
In this document we provide a basic description of ICMP's role in the |
| 13 |
IP stack and some guidelines for future use. |
| 14 |
|
| 15 |
This document is motivated by concerns about lack of clarity |
| 16 |
concerning when to add new Internet Control Message Protocol (ICMP) |
| 17 |
types and/or codes. These concerns have highlighted a need to |
| 18 |
describe policies for when adding new features to ICMP is desirable |
| 19 |
and when it is not. |
| 20 |
|
| 21 |
Status of This Memo |
| 22 |
|
| 23 |
This memo documents an Internet Best Current Practice. |
| 24 |
|
| 25 |
This document is a product of the Internet Engineering Task Force |
| 26 |
(IETF). It represents the consensus of the IETF community. It has |
| 27 |
received public review and has been approved for publication by the |
| 28 |
Internet Engineering Steering Group (IESG). Further information on |
| 29 |
BCPs is available in <a href="./rfc5741#section-2">Section 2 of RFC 5741</a>. |
| 30 |
|
| 31 |
Information about the current status of this document, any errata, |
| 32 |
and how to provide feedback on it may be obtained at |
| 33 |
<a href="http://www.rfc-editor.org/info/rfc7279">http://www.rfc-editor.org/info/rfc7279</a>. |
| 34 |
|
| 35 |
Copyright Notice |
| 36 |
|
| 37 |
Copyright (c) 2014 IETF Trust and the persons identified as the |
| 38 |
document authors. All rights reserved. |
| 39 |
|
| 40 |
This document is subject to <a href="https://www.rfc-editor.org/bcp/bcp78">BCP 78</a> and the IETF Trust's Legal |
| 41 |
Provisions Relating to IETF Documents |
| 42 |
(<a href="http://trustee.ietf.org/license-info">http://trustee.ietf.org/license-info</a>) in effect on the date of |
| 43 |
publication of this document. Please review these documents |
| 44 |
carefully, as they describe your rights and restrictions with respect |
| 45 |
to this document. Code Components extracted from this document must |
| 46 |
include Simplified BSD License text as described in Section 4.e of |
| 47 |
the Trust Legal Provisions and are provided without warranty as |
| 48 |
described in the Simplified BSD License. |
| 49 |
|
| 50 |
|
| 51 |
|
| 52 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 1]</span></pre> |
| 53 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-2" ></span> |
| 54 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 55 |
|
| 56 |
|
| 57 |
Table of Contents |
| 58 |
|
| 59 |
<a href="#section-1">1</a>. Introduction . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 60 |
<a href="#section-2">2</a>. Acceptable Use Policy . . . . . . . . . . . . . . . . . . . . <a href="#page-2">2</a> |
| 61 |
<a href="#section-2.1">2.1</a>. Classification of Existing Message Types . . . . . . . . <a href="#page-3">3</a> |
| 62 |
<a href="#section-2.1.1">2.1.1</a>. ICMP Use as a Routing Protocol . . . . . . . . . . . <a href="#page-6">6</a> |
| 63 |
<a href="#section-2.1.2">2.1.2</a>. A Few Notes on RPL . . . . . . . . . . . . . . . . . <a href="#page-6">6</a> |
| 64 |
<a href="#section-2.2">2.2</a>. Applications Using ICMP . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 65 |
<a href="#section-2.3">2.3</a>. Extending ICMP . . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 66 |
<a href="#section-2.4">2.4</a>. ICMPv4 vs. ICMPv6 . . . . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 67 |
<a href="#section-3">3</a>. ICMP's Role in the Internet . . . . . . . . . . . . . . . . . <a href="#page-7">7</a> |
| 68 |
<a href="#section-4">4</a>. Security Considerations . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 69 |
<a href="#section-5">5</a>. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 70 |
<a href="#section-6">6</a>. References . . . . . . . . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 71 |
<a href="#section-6.1">6.1</a>. Normative references . . . . . . . . . . . . . . . . . . <a href="#page-8">8</a> |
| 72 |
<a href="#section-6.2">6.2</a>. Informative references . . . . . . . . . . . . . . . . . <a href="#page-9">9</a> |
| 73 |
|
| 74 |
<span class="h2"><a class="selflink" id="section-1" href="#section-1">1</a>. Introduction</span> |
| 75 |
|
| 76 |
There has been some recent concern expressed about a lack of clarity |
| 77 |
around when new message types and codes should be added to ICMP |
| 78 |
(including ICMPv4 [<a href="./rfc0792" title=""Internet Control Message Protocol"">RFC0792</a>] and ICMPv6 [<a href="./rfc4443" title=""Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"">RFC4443</a>]). We lay out a |
| 79 |
policy regarding when (and when not) to move functionality into ICMP. |
| 80 |
|
| 81 |
This document is the result of discussions among ICMP experts within |
| 82 |
the Operations and Management (OPS) area's IP Diagnostics Technical |
| 83 |
Interest Group [<a href="#ref-DIAGNOSTICS">DIAGNOSTICS</a>] and concerns expressed by the OPS area |
| 84 |
leadership. |
| 85 |
|
| 86 |
Note that this document does not supercede the "IANA Allocation |
| 87 |
Guidelines For Values In the Internet Protocol and Related Headers" |
| 88 |
[<a href="./rfc2780" title=""IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers"">RFC2780</a>], which specifies best practices and processes for the |
| 89 |
allocation of values in the IANA registries but does not describe the |
| 90 |
policies to be applied in the standards process. |
| 91 |
|
| 92 |
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", |
| 93 |
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this |
| 94 |
document are to be interpreted as described in [<a href="./rfc2119" title=""Key words for use in RFCs to Indicate Requirement Levels"">RFC2119</a>]. |
| 95 |
|
| 96 |
<span class="h2"><a class="selflink" id="section-2" href="#section-2">2</a>. Acceptable Use Policy</span> |
| 97 |
|
| 98 |
In this document, we describe an acceptable use policy for new ICMP |
| 99 |
message types and codes, and provide some background about the |
| 100 |
policy. |
| 101 |
|
| 102 |
|
| 103 |
|
| 104 |
|
| 105 |
|
| 106 |
|
| 107 |
|
| 108 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 2]</span></pre> |
| 109 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-3" ></span> |
| 110 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 111 |
|
| 112 |
|
| 113 |
In summary, any future message types added to ICMP should be limited |
| 114 |
to two broad categories: |
| 115 |
|
| 116 |
1. to inform a datagram's originator that a forwarding plane anomaly |
| 117 |
has been encountered downstream. The datagram originator must be |
| 118 |
able to determine whether or not the datagram was discarded by |
| 119 |
examining the ICMP message. |
| 120 |
|
| 121 |
2. to discover and convey dynamic information about a node (other |
| 122 |
than information usually carried in routing protocols), to |
| 123 |
discover and convey network-specific parameters, and to discover |
| 124 |
on-link routers and hosts. |
| 125 |
|
| 126 |
Normally, ICMP SHOULD NOT be used to implement a general-purpose |
| 127 |
routing or network management protocol. However, ICMP does have a |
| 128 |
role to play in conveying dynamic information about a network, which |
| 129 |
would belong in category 2 above. |
| 130 |
|
| 131 |
<span class="h3"><a class="selflink" id="section-2.1" href="#section-2.1">2.1</a>. Classification of Existing Message Types</span> |
| 132 |
|
| 133 |
This section provides a rough breakdown of existing message types |
| 134 |
according to the taxonomy described in <a href="#section-2">Section 2</a> at the time of |
| 135 |
publication. |
| 136 |
|
| 137 |
IPv4 forwarding plane anomaly reporting: |
| 138 |
|
| 139 |
3: Destination Unreachable |
| 140 |
|
| 141 |
4: Source Quench (Deprecated) |
| 142 |
|
| 143 |
6: Alternate Host Address (Deprecated) |
| 144 |
|
| 145 |
11: Time Exceeded |
| 146 |
|
| 147 |
12: Parameter Problem |
| 148 |
|
| 149 |
31: Datagram Conversion Error (Deprecated) |
| 150 |
|
| 151 |
IPv4 router or host discovery: |
| 152 |
|
| 153 |
0: Echo Reply |
| 154 |
|
| 155 |
5: Redirect |
| 156 |
|
| 157 |
8: Echo |
| 158 |
|
| 159 |
9: Router Advertisement |
| 160 |
|
| 161 |
|
| 162 |
|
| 163 |
|
| 164 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 3]</span></pre> |
| 165 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-4" ></span> |
| 166 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 167 |
|
| 168 |
|
| 169 |
10: Router Solicitation |
| 170 |
|
| 171 |
13: Timestamp |
| 172 |
|
| 173 |
14: Timestamp Reply |
| 174 |
|
| 175 |
15: Information Request (Deprecated) |
| 176 |
|
| 177 |
16: Information Reply (Deprecated) |
| 178 |
|
| 179 |
17: Address Mask Request (Deprecated) |
| 180 |
|
| 181 |
18: Address Mask Reply (Deprecated) |
| 182 |
|
| 183 |
30: Traceroute (Deprecated) |
| 184 |
|
| 185 |
32: Mobile Host Redirect (Deprecated) |
| 186 |
|
| 187 |
33: IPv6 Where-Are-You (Deprecated) |
| 188 |
|
| 189 |
34: IPv6 I-Am-Here (Deprecated) |
| 190 |
|
| 191 |
35: Mobile Registration Request (Deprecated) |
| 192 |
|
| 193 |
36: Mobile Registration Reply (Deprecated) |
| 194 |
|
| 195 |
37: Domain Name Request (Deprecated) |
| 196 |
|
| 197 |
38: Domain Name Reply (Deprecated) |
| 198 |
|
| 199 |
39: SKIP (Deprecated) |
| 200 |
|
| 201 |
40: Photuris |
| 202 |
|
| 203 |
41: ICMP messages utilized by experimental mobility protocols |
| 204 |
such as Seamoby |
| 205 |
|
| 206 |
Please note that some ICMP message types were formally deprecated by |
| 207 |
[<a href="./rfc6918" title=""Formally Deprecating Some ICMPv4 Message Types"">RFC6918</a>]. |
| 208 |
|
| 209 |
IPv6 forwarding plane anomaly reporting: |
| 210 |
|
| 211 |
1: Destination Unreachable |
| 212 |
|
| 213 |
2: Packet Too Big |
| 214 |
|
| 215 |
|
| 216 |
|
| 217 |
|
| 218 |
|
| 219 |
|
| 220 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 4]</span></pre> |
| 221 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-5" ></span> |
| 222 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 223 |
|
| 224 |
|
| 225 |
3: Time Exceeded |
| 226 |
|
| 227 |
4: Parameter Problem |
| 228 |
|
| 229 |
150: ICMP messages utilized by experimental mobility protocols |
| 230 |
such as Seamoby |
| 231 |
|
| 232 |
IPv6 router or host discovery: |
| 233 |
|
| 234 |
128: Echo Request |
| 235 |
|
| 236 |
129: Echo Reply |
| 237 |
|
| 238 |
130: Multicast Listener Query |
| 239 |
|
| 240 |
131: Multicast Listener Report |
| 241 |
|
| 242 |
132: Multicast Listener Done |
| 243 |
|
| 244 |
133: Router Solicitation |
| 245 |
|
| 246 |
134: Router Advertisement |
| 247 |
|
| 248 |
135: Neighbor Solicitation |
| 249 |
|
| 250 |
136: Neighbor Advertisement |
| 251 |
|
| 252 |
137: Redirect Message |
| 253 |
|
| 254 |
138: Router Renumbering |
| 255 |
|
| 256 |
139: ICMP Node Information Query |
| 257 |
|
| 258 |
140: ICMP Node Information Response |
| 259 |
|
| 260 |
141: Inverse Neighbor Discovery Solicitation Message |
| 261 |
|
| 262 |
142: Inverse Neighbor Discovery Advertisement Message |
| 263 |
|
| 264 |
143: Version 2 Multicast Listener Report |
| 265 |
|
| 266 |
144: Home Agent Address Discovery Request Message |
| 267 |
|
| 268 |
145: Home Agent Address Discovery Reply Message |
| 269 |
|
| 270 |
146: Mobile Prefix Solicitation |
| 271 |
|
| 272 |
|
| 273 |
|
| 274 |
|
| 275 |
|
| 276 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 5]</span></pre> |
| 277 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-6" ></span> |
| 278 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 279 |
|
| 280 |
|
| 281 |
147: Mobile Prefix Advertisement |
| 282 |
|
| 283 |
148: Certification Path Solicitation Message |
| 284 |
|
| 285 |
149: Certification Path Advertisement Message |
| 286 |
|
| 287 |
150: ICMP messages utilized by experimental mobility protocols |
| 288 |
such as Seamoby |
| 289 |
|
| 290 |
151: Multicast Router Advertisement |
| 291 |
|
| 292 |
152: Multicast Router Solicitation |
| 293 |
|
| 294 |
153: Multicast Router Termination |
| 295 |
|
| 296 |
154: FMIPv6 Messages |
| 297 |
|
| 298 |
155: RPL Control Message |
| 299 |
|
| 300 |
<span class="h4"><a class="selflink" id="section-2.1.1" href="#section-2.1.1">2.1.1</a>. ICMP Use as a Routing Protocol</span> |
| 301 |
|
| 302 |
As mentioned in <a href="#section-2">Section 2</a>, using ICMP as a general-purpose routing or |
| 303 |
network management protocol is not advisable and SHOULD NOT be used |
| 304 |
that way. |
| 305 |
|
| 306 |
ICMP has a role in the Internet as an integral part of the IP layer; |
| 307 |
it is not as a routing protocol or as a transport protocol for other |
| 308 |
layers including routing information. From a more pragmatic |
| 309 |
perspective, some of the key characteristics of ICMP make it a less- |
| 310 |
than-ideal choice for a routing protocol. These key characteristics |
| 311 |
include that ICMP is frequently filtered, is not authenticated, and |
| 312 |
is easily spoofed. In addition, specialist hardware processing of |
| 313 |
ICMP would disrupt the deployment of an ICMP-based routing or |
| 314 |
management protocol. |
| 315 |
|
| 316 |
<span class="h4"><a class="selflink" id="section-2.1.2" href="#section-2.1.2">2.1.2</a>. A Few Notes on RPL</span> |
| 317 |
|
| 318 |
RPL, the IPv6 routing protocol for low-power and lossy networks (see |
| 319 |
[<a href="./rfc6550" title=""RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks"">RFC6550</a>]) uses ICMP as a transport. In this regard, it is an |
| 320 |
exception among the ICMP message types. Note that, although RPL is |
| 321 |
an IP routing protocol, it is not deployed on the general Internet; |
| 322 |
it is limited to specific, contained networks. |
| 323 |
|
| 324 |
This should be considered anomalous and is not a model for future |
| 325 |
ICMP message types. That is, ICMP is not intended as a transport for |
| 326 |
other protocols and SHOULD NOT be used in that way in future |
| 327 |
specifications. In particular, while it is adequate to use ICMP as a |
| 328 |
discovery protocol, it does not extend to full routing capabilities. |
| 329 |
|
| 330 |
|
| 331 |
|
| 332 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 6]</span></pre> |
| 333 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-7" ></span> |
| 334 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 335 |
|
| 336 |
|
| 337 |
<span class="h3"><a class="selflink" id="section-2.2" href="#section-2.2">2.2</a>. Applications Using ICMP</span> |
| 338 |
|
| 339 |
Some applications make use of ICMP error notifications, or even |
| 340 |
deliberately create anomalous conditions in order to elicit ICMP |
| 341 |
messages. These ICMP messages are then used to generate feedback to |
| 342 |
the higher layer. Some of these applications include some of the |
| 343 |
most widespread examples, such as PING, TRACEROUTE, and Path MTU |
| 344 |
Discovery (PMTUD). These uses are considered acceptable because they |
| 345 |
use existing ICMP message types and do not change ICMP functionality. |
| 346 |
|
| 347 |
<span class="h3"><a class="selflink" id="section-2.3" href="#section-2.3">2.3</a>. Extending ICMP</span> |
| 348 |
|
| 349 |
ICMP multi-part messages are specified in [<a href="./rfc4884" title=""Extended ICMP to Support Multi-Part Messages"">RFC4884</a>] by defining an |
| 350 |
extension mechanism for selected ICMP messages. This mechanism |
| 351 |
addresses a fundamental problem in ICMP extensibility. An ICMP |
| 352 |
multi-part message carries all of the information that ICMP messages |
| 353 |
carried previously, as well as additional information that |
| 354 |
applications may require. |
| 355 |
|
| 356 |
Some currently defined ICMP extensions include ICMP extensions for |
| 357 |
Multiprotocol Label Switching [<a href="./rfc4950" title=""ICMP Extensions for Multiprotocol Label Switching"">RFC4950</a>] and ICMP extensions for |
| 358 |
interface and next-hop identification [<a href="./rfc5837" title=""Extending ICMP for Interface and Next-Hop Identification"">RFC5837</a>]. |
| 359 |
|
| 360 |
Extensions to ICMP SHOULD follow the requirements provided in |
| 361 |
[<a href="./rfc4884" title=""Extended ICMP to Support Multi-Part Messages"">RFC4884</a>]. |
| 362 |
|
| 363 |
<span class="h3"><a class="selflink" id="section-2.4" href="#section-2.4">2.4</a>. ICMPv4 vs. ICMPv6</span> |
| 364 |
|
| 365 |
Because ICMPv6 is used for IPv6 Neighbor Discovery, deployed IPv6 |
| 366 |
routers, IPv6-capable security gateways, and IPv6-capable firewalls |
| 367 |
normally support administrator configuration of how specific ICMPv6 |
| 368 |
message types are handled. By contrast, deployed IPv4 routers, |
| 369 |
IPv4-capable security gateways, and IPv4-capable firewalls are less |
| 370 |
likely to allow an administrator to configure how specific ICMPv4 |
| 371 |
message types are handled. So, at present, ICMPv6 messages usually |
| 372 |
have a higher probability of travelling end-to-end than ICMPv4 |
| 373 |
messages. |
| 374 |
|
| 375 |
<span class="h2"><a class="selflink" id="section-3" href="#section-3">3</a>. ICMP's Role in the Internet</span> |
| 376 |
|
| 377 |
ICMP was originally intended to be a mechanism for gateways or |
| 378 |
destination hosts to report error conditions back to source hosts in |
| 379 |
ICMPv4 [<a href="./rfc0792" title=""Internet Control Message Protocol"">RFC0792</a>]; ICMPv6 [<a href="./rfc4443" title=""Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification"">RFC4443</a>] is modeled after it. ICMP is also |
| 380 |
used to perform IP-layer functions, such as diagnostics (e.g., PING). |
| 381 |
|
| 382 |
ICMP is defined to be an integral part of IP and must be implemented |
| 383 |
by every IP module. This is true for ICMPv4 as an integral part of |
| 384 |
IPv4 (see the Introduction of [<a href="./rfc0792" title=""Internet Control Message Protocol"">RFC0792</a>]), and for ICMPv6 as an |
| 385 |
|
| 386 |
|
| 387 |
|
| 388 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 7]</span></pre> |
| 389 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-8" ></span> |
| 390 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 391 |
|
| 392 |
|
| 393 |
integral part of IPv6 (see <a href="./rfc4443#section-2">Section 2 of [RFC4443]</a>). When first |
| 394 |
defined, ICMP messages were thought of as IP messages that didn't |
| 395 |
carry any higher-layer data. It could be conjectured that the term |
| 396 |
"control" was used because ICMP messages were not "data" messages. |
| 397 |
|
| 398 |
The word "control" in the protocol name did not describe ICMP's |
| 399 |
function (i.e., it did not "control" the Internet); rather, it was |
| 400 |
used to communicate about the control functions in the Internet. For |
| 401 |
example, even though ICMP included a redirect message type that |
| 402 |
affects routing behavior in the context of a LAN segment, it was not |
| 403 |
and is not used as a generic routing protocol. |
| 404 |
|
| 405 |
<span class="h2"><a class="selflink" id="section-4" href="#section-4">4</a>. Security Considerations</span> |
| 406 |
|
| 407 |
This document describes a high-level policy for adding ICMP types and |
| 408 |
codes. While special attention must be paid to the security |
| 409 |
implications of any particular new ICMP type or code, this |
| 410 |
recommendation presents no new security considerations. |
| 411 |
|
| 412 |
From a security perspective, ICMP plays a part in the Photuris |
| 413 |
protocol [<a href="./rfc2521" title=""ICMP Security Failures Messages"">RFC2521</a>]. But more generally, ICMP is not a secure |
| 414 |
protocol and does not include features to be used to discover network |
| 415 |
security parameters or to report on network security anomalies in the |
| 416 |
forwarding plane. |
| 417 |
|
| 418 |
Additionally, new ICMP functionality (e.g., ICMP extensions, or new |
| 419 |
ICMP types or codes) needs to consider potential ways that ICMP can |
| 420 |
be abused (e.g., Smurf IP DoS [<a href="#ref-CA-1998-01">CA-1998-01</a>]). |
| 421 |
|
| 422 |
<span class="h2"><a class="selflink" id="section-5" href="#section-5">5</a>. Acknowledgments</span> |
| 423 |
|
| 424 |
This document was originally proposed by, and received substantial |
| 425 |
review and suggestions from, Ron Bonica. Discussions with Pascal |
| 426 |
Thubert helped clarify the history of RPL's use of ICMP. We are very |
| 427 |
grateful for the review, feedback, and comments from Ran Atkinson, |
| 428 |
Tim Chown, Joe Clarke, Adrian Farrel, Ray Hunter, Hilarie Orman, Eric |
| 429 |
Rosen, JINMEI Tatuya, and Wen Zhang, which resulted in a much |
| 430 |
improved document. |
| 431 |
|
| 432 |
<span class="h2"><a class="selflink" id="section-6" href="#section-6">6</a>. References</span> |
| 433 |
|
| 434 |
<span class="h3"><a class="selflink" id="section-6.1" href="#section-6.1">6.1</a>. Normative references</span> |
| 435 |
|
| 436 |
[<a id="ref-RFC0792">RFC0792</a>] Postel, J., "Internet Control Message Protocol", STD 5, |
| 437 |
<a href="./rfc792">RFC 792</a>, September 1981. |
| 438 |
|
| 439 |
[<a id="ref-RFC2119">RFC2119</a>] Bradner, S., "Key words for use in RFCs to Indicate |
| 440 |
Requirement Levels", <a href="https://www.rfc-editor.org/bcp/bcp14">BCP 14</a>, <a href="./rfc2119">RFC 2119</a>, March 1997. |
| 441 |
|
| 442 |
|
| 443 |
|
| 444 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 8]</span></pre> |
| 445 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-9" ></span> |
| 446 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 447 |
|
| 448 |
|
| 449 |
[<a id="ref-RFC4443">RFC4443</a>] Conta, A., Deering, S., and M. Gupta, "Internet Control |
| 450 |
Message Protocol (ICMPv6) for the Internet Protocol |
| 451 |
Version 6 (IPv6) Specification", <a href="./rfc4443">RFC 4443</a>, March 2006. |
| 452 |
|
| 453 |
[<a id="ref-RFC4884">RFC4884</a>] Bonica, R., Gan, D., Tappan, D., and C. Pignataro, |
| 454 |
"Extended ICMP to Support Multi-Part Messages", <a href="./rfc4884">RFC 4884</a>, |
| 455 |
April 2007. |
| 456 |
|
| 457 |
<span class="h3"><a class="selflink" id="section-6.2" href="#section-6.2">6.2</a>. Informative references</span> |
| 458 |
|
| 459 |
[<a id="ref-CA-1998-01">CA-1998-01</a>] |
| 460 |
CERT, "Smurf IP Denial-of-Service Attacks", CERT Advisory |
| 461 |
CA-1998-01, January 1998, |
| 462 |
<<a href="http://www.cert.org/advisories/CA-1998-01.html">http://www.cert.org/advisories/CA-1998-01.html</a>>. |
| 463 |
|
| 464 |
[<a id="ref-DIAGNOSTICS">DIAGNOSTICS</a>] |
| 465 |
"IP Diagnostics Technical Interest Group", , |
| 466 |
<<a href="https://svn.tools.ietf.org/area/ops/trac/wiki/TIG_DIAGNOSTICS">https://svn.tools.ietf.org/area/ops/trac/wiki/</a> |
| 467 |
<a href="https://svn.tools.ietf.org/area/ops/trac/wiki/TIG_DIAGNOSTICS">TIG_DIAGNOSTICS</a>>. |
| 468 |
|
| 469 |
[<a id="ref-RFC2521">RFC2521</a>] Karn, P. and W. Simpson, "ICMP Security Failures |
| 470 |
Messages", <a href="./rfc2521">RFC 2521</a>, March 1999. |
| 471 |
|
| 472 |
[<a id="ref-RFC2780">RFC2780</a>] Bradner, S. and V. Paxson, "IANA Allocation Guidelines For |
| 473 |
Values In the Internet Protocol and Related Headers", <a href="https://www.rfc-editor.org/bcp/bcp37">BCP</a> |
| 474 |
<a href="https://www.rfc-editor.org/bcp/bcp37">37</a>, <a href="./rfc2780">RFC 2780</a>, March 2000. |
| 475 |
|
| 476 |
[<a id="ref-RFC4950">RFC4950</a>] Bonica, R., Gan, D., Tappan, D., and C. Pignataro, "ICMP |
| 477 |
Extensions for Multiprotocol Label Switching", <a href="./rfc4950">RFC 4950</a>, |
| 478 |
August 2007. |
| 479 |
|
| 480 |
[<a id="ref-RFC5837">RFC5837</a>] Atlas, A., Bonica, R., Pignataro, C., Shen, N., and JR. |
| 481 |
Rivers, "Extending ICMP for Interface and Next-Hop |
| 482 |
Identification", <a href="./rfc5837">RFC 5837</a>, April 2010. |
| 483 |
|
| 484 |
[<a id="ref-RFC6550">RFC6550</a>] Winter, T., Thubert, P., Brandt, A., Hui, J., Kelsey, R., |
| 485 |
Levis, P., Pister, K., Struik, R., Vasseur, JP., and R. |
| 486 |
Alexander, "RPL: IPv6 Routing Protocol for Low-Power and |
| 487 |
Lossy Networks", <a href="./rfc6550">RFC 6550</a>, March 2012. |
| 488 |
|
| 489 |
[<a id="ref-RFC6918">RFC6918</a>] Gont, F. and C. Pignataro, "Formally Deprecating Some |
| 490 |
ICMPv4 Message Types", <a href="./rfc6918">RFC 6918</a>, April 2013. |
| 491 |
|
| 492 |
|
| 493 |
|
| 494 |
|
| 495 |
|
| 496 |
|
| 497 |
|
| 498 |
|
| 499 |
|
| 500 |
<span class="grey">Shore & Pignataro Best Current Practice [Page 9]</span></pre> |
| 501 |
<hr class='noprint'/><!--NewPage--><pre class='newpage'><span id="page-10" ></span> |
| 502 |
<span class="grey"><a href="./rfc7279">RFC 7279</a> ICMP AUP May 2014</span> |
| 503 |
|
| 504 |
|
| 505 |
Authors' Addresses |
| 506 |
|
| 507 |
Melinda Shore |
| 508 |
No Mountain Software |
| 509 |
PO Box 16271 |
| 510 |
Two Rivers, AK 99716 |
| 511 |
US |
| 512 |
|
| 513 |
Phone: +1 907 322 9522 |
| 514 |
EMail: [email protected] |
| 515 |
|
| 516 |
|
| 517 |
Carlos Pignataro |
| 518 |
Cisco Systems, Inc. |
| 519 |
7200-12 Kit Creek Road |
| 520 |
Research Triangle Park, NC 27709 |
| 521 |
US |
| 522 |
|
| 523 |
EMail: [email protected] |
| 524 |
|
| 525 |
|
| 526 |
|
| 527 |
|
| 528 |
|
| 529 |
|
| 530 |
|
| 531 |
|
| 532 |
|
| 533 |
|
| 534 |
|
| 535 |
|
| 536 |
|
| 537 |
|
| 538 |
|
| 539 |
|
| 540 |
|
| 541 |
|
| 542 |
|
| 543 |
|
| 544 |
|
| 545 |
|
| 546 |
|
| 547 |
|
| 548 |
|
| 549 |
|
| 550 |
|
| 551 |
|
| 552 |
|
| 553 |
|
| 554 |
|
| 555 |
|
| 556 |
Shore & Pignataro Best Current Practice [Page 10] |
| 557 |
</pre> |