Internet Control Message Protocol (ICMP) Parameters
ICMP Type Numbers
- IESG Approval or Standards Action
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
- RFC 9899: Extensions to the YANG Data Model for Access Control Lists (ACLs)
The Internet Control Message Protocol (ICMP) has many messages that
are identified by a "type" field.
When this registry is modified, the YANG module "iana-icmpv4-types"
YANG Parameters must be updated as defined in
RFC 9899.
Code Fields
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
Many of these ICMP types have a "code" field. Here we list the types
again with their assigned code fields.
Type 0 — Echo Reply
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 1 — Unassigned
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 2 — Unassigned
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 3 — Destination Unreachable
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Net Unreachable |
RFC 792 |
| 1 |
Host Unreachable |
RFC 792 |
| 2 |
Protocol Unreachable |
RFC 792 |
| 3 |
Port Unreachable |
RFC 792 |
| 4 |
Fragmentation Needed and Don't
Fragment was Set |
RFC 792 |
| 5 |
Source Route Failed |
RFC 792 |
| 6 |
Destination Network Unknown |
RFC 1122 |
| 7 |
Destination Host Unknown |
RFC 1122 |
| 8 |
Source Host Isolated |
RFC 1122 |
| 9 |
Communication with Destination
Network is Administratively Prohibited |
RFC 1122 |
| 10 |
Communication with Destination Host is
Administratively Prohibited |
RFC 1122 |
| 11 |
Destination Network Unreachable for Type
of Service |
RFC 1122 |
| 12 |
Destination Host Unreachable for Type of
Service |
RFC 1122 |
| 13 |
Communication Administratively Prohibited |
RFC 1812 |
| 14 |
Host Precedence Violation |
RFC 1812 |
| 15 |
Precedence cutoff in effect |
RFC 1812 |
Type 4 — Source Quench (Deprecated)
- RFC 792: Internet Control Message Protocol
- RFC 6633: Deprecation of ICMP Source Quench Messages
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 5 — Redirect
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Redirect Datagram for the Network (or subnet) |
|
| 1 |
Redirect Datagram for the Host |
|
| 2 |
Redirect Datagram for the Type of Service and Network |
|
| 3 |
Redirect Datagram for the Type of Service and Host |
|
Type 6 — Alternate Host Address (Deprecated)
| Codes |
Description |
Reference |
| 0 |
Alternate Address for Host |
|
Type 7 — Unassigned
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 8 — Echo
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 9 — Router Advertisement
- IESG Approval or Standards Action
- RFC 1256: ICMP Router Discovery Messages
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Normal router advertisement |
RFC 3344 |
| 16 |
Does not route common traffic |
RFC 3344 |
Type 10 — Router Selection
- IESG Approval or Standards Action
- RFC 1256: ICMP Router Discovery Messages
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 11 — Time Exceeded
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Time to Live exceeded in Transit |
|
| 1 |
Fragment Reassembly Time Exceeded |
|
Type 12 — Parameter Problem
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Pointer indicates the error |
|
| 1 |
Missing a Required Option |
RFC 1108 |
| 2 |
Bad Length |
|
Type 13 — Timestamp
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 14 — Timestamp Reply
- IESG Approval or Standards Action
- RFC 792: Internet Control Message Protocol
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 15 — Information Request (Deprecated)
- RFC 792: Internet Control Message Protocol
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 16 — Information Reply (Deprecated)
- RFC 792: Internet Control Message Protocol
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 17 — Address Mask Request (Deprecated)
- RFC 950: Internet Standard Subnetting Procedure
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 18 — Address Mask Reply (Deprecated)
- RFC 950: Internet Standard Subnetting Procedure
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| 0 |
No Code |
|
Type 19 — Reserved (for Security)
| Codes |
Description |
Reference |
| No registrations at this time. |
Types 20-29 — Reserved (for Robustness Experiment)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 30 — Traceroute (Deprecated)
- RFC 1393: Traceroute Using an IP Option
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 31 — Datagram Conversion Error (Deprecated)
- RFC 1475: TP/IX: The Next Internet
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 32 — Mobile Host Redirect (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 33 — IPv6 Where-Are-You (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 34 — IPv6 I-Am-Here (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 35 — Mobile Registration Request (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 36 — Mobile Registration Reply (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 37 — Domain Name Request (Deprecated)
- RFC 1788: ICMP Domain Name Messages
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 38 — Domain Name Reply (Deprecated)
- RFC 1788: ICMP Domain Name Messages
- RFC 6918: Formally Deprecating Some ICMPv4 Message Types
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 39 — SKIP (Deprecated)
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 40 — Photuris
- IESG Approval or Standards Action
- RFC 2521: ICMP Security Failures Messages
- RFC 2780: IANA Allocation Guidelines For Values In the Internet Protocol and Related Headers
| Codes |
Description |
Reference |
| 0 |
Bad SPI |
|
| 1 |
Authentication Failed |
|
| 2 |
Decompression Failed |
|
| 3 |
Decryption Failed |
|
| 4 |
Need Authentication |
|
| 5 |
Need Authorization |
|
Type 41 — ICMP messages utilized by experimental mobility protocols such as Seamoby
- Specification Required or IESG Approval
- RFC 4065: Instructions for Seamoby and Experimental Mobility Protocol IANA Allocations
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 42 — Extended Echo Request
- RFC 8335: PROBE: A Utility for Probing Interfaces
| Codes |
Description |
Reference |
| 0 |
No Error |
RFC 8335 |
| 1-255 |
Unassigned |
|
Type 43 — Extended Echo Reply
- RFC 8335: PROBE: A Utility for Probing Interfaces
Types 44-252 — Unassigned
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 253 — RFC3692-style Experiment 1 [1]
- Standards Action or IESG Approval
- RFC 4727: Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
| Codes |
Description |
Reference |
| No registrations at this time. |
Type 254 — RFC3692-style Experiment 2 [1]
- Standards Action or IESG Approval
- RFC 4727: Experimental Values In IPv4, IPv6, ICMPv4, ICMPv6, UDP, and TCP Headers
| Codes |
Description |
Reference |
| No registrations at this time. |
ICMP Extension Object Classes and Class Sub-types
- RFC 4884: Extended ICMP to Support Multi-Part Messages
| Range |
Registration Procedures |
| 0-246 |
First Come First Served |
| 247-255 |
Private Use |
Sub-types — Class 1 — MPLS Label Stack Class
- RFC 4950: ICMP Extensions for Multiprotocol Label Switching
| C-Type (Value) |
Description |
Reference |
| 0 |
Reserved |
RFC 4950 |
| 1 |
Incoming MPLS Label Stack |
RFC 4950 |
| 2-246 |
Unassigned |
|
| 247-255 |
Reserved for private use |
RFC 4950 |
Sub-types — Class 2 — Interface Information Object
- RFC 5837: Extending ICMP for Interface and Next-Hop Identification
| C-Type (Value) |
Description |
Reference |
| 0-1 |
Interface Role field |
RFC 5837 |
| 2 |
Unallocated - allocatable with Standards Action |
RFC 5837 |
| 3 |
Unallocated - allocatable with Standards Action |
RFC 5837 |
| 4 |
ifIndex included |
RFC 5837 |
| 5 |
IP Address Sub-object included |
RFC 5837 |
| 6 |
Name Sub-object included |
RFC 5837 |
| 7 |
MTU included |
RFC 5837 |
Sub-types — Class 2 — Interface Information Object — Interface Roles
| Value |
Description |
Reference |
| 0 |
Incoming IP Interface |
RFC 5837 |
| 1 |
Sub-IP Component of Incoming IP Interface |
RFC 5837 |
| 2 |
Outgoing IP Interface |
RFC 5837 |
| 3 |
IP Next-hop |
RFC 5837 |
Sub-types — Class 3 — Interface Identification Object
- RFC 8335: PROBE: A Utility for Probing Interfaces
| Codes |
Description |
Reference |
| 0 |
Reserved |
RFC 8335 |
| 1 |
Identifies Interface By Name |
RFC 8335 |
| 2 |
Identifies Interface By Index |
RFC 8335 |
| 3 |
Identifies Interface By Address |
RFC 8335 |
| 4-255 |
Unassigned |
|
Sub-types — Class 4 — Extended Information
- RFC 8883: ICMPv6 Errors for Discarding Packets Due to Processing Limits
Sub-types — Class 6 — Reflect All
Contact Information
Footnote
| [1] |
It is only appropriate to use these values in explicitly-
configured experiments; they MUST NOT be shipped as defaults in
implementations. See RFC 3692 for details. |