| Internet-Draft | ICMP Query for IP Node Information | February 2026 |
| Min, et al. | Expires 28 August 2026 | [Page] |
This document introduces two new ICMP messages. They are called the ICMP Query Request and the ICMP Query Response. The ICMP Query Request requests information. The ICMP Query Response provides information in response to an ICMP Query Request.¶
This document updates RFC 4884.¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 28 August 2026.¶
Copyright (c) 2026 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document introduces two new ICMP messages. They are called the ICMP Query Request and the ICMP Query Response. The ICMP Query Request requests information. The ICMP Query Response provides information in response to an ICMP Query Request.¶
Both messages are specified for ICMPv4 [RFC792] and ICMPv6 [RFC4443]. Both messages include an ICMP Extension Structure [RFC4884]. ICMP Extension Objects in the Query Request message determine which information is requested. ICMP Extension Objects in the Query Response message provide the requested information.¶
To prevent denial of service attacks, the ICMP Query Response message MUST NOT be longer than the corresponding ICMP Query Request message.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all capitals, as shown here.¶
The ICMP Query Request message is defined for both ICMPv4 and ICMPv6. Like any ICMP message, the ICMP Query Request message is encapsulated in an IP header. The ICMPv4 version of the Query Request message is encapsulated in an IPv4 header, while the ICMPv6 version is encapsulated in an IPv6 header.¶
The ICMP Query Request message has the following format:¶
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = TBD1/2 | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identifier | Sequence Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ICMP Extension Structure
IP Header fields:¶
Source Address: The Source Address identifies the ICMP Querying node. It MUST be a valid IP unicast address.¶
Destination Address: The Destination Address identifies the ICMP Queried node. It MUST be a valid IP unicast address.¶
ICMP fields:¶
Type: ICMP Query Request. The value is TBD1 for ICMP and TBD2 for ICMPv6.¶
Code: MUST be set to 0 and MUST be ignored upon receipt.¶
Identifier: An Identifier aids in matching ICMP Query Replies to ICMP Query Requests.¶
Sequence Number: A Sequence Number to aid in matching ICMP Query Replies to ICMP Query Requests.¶
Following the ICMP Query Request header, it's an ICMP Extension Structure as specified in Sections 7 and 8 of [RFC4884], continuing to the end of the packet.¶
Nothing can be added after the ICMP Extension Structure.¶
One or more Query Request Objects MUST be encapsulated in an ICMP Extension Structure of the ICMP Query Request message.¶
Each Query Request Object has the following format:¶
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num | C-Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Query Request Object Payload ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Object fields:¶
Class-Num: Indicates the class of IP node information to be queried. The value will be requested by a separate document.¶
C-Type: Indicates the sub-type of IP node information to be queried. The value will be requested by a separate document.¶
Length: Length of the object, measured in octets, including the Object Header and payload.¶
Object payload: Following the Query Request Object Header is the Query Request Object Payload, which is used to define the scope of IP node information to be queried. The length of this field is variable. The value will be defined by a separate document.¶
One or more Pad Objects MAY be encapsulated in an ICMP Extension Structure of the ICMP Query Request message.¶
Each Pad Object has the following format:¶
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num | C-Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Extra Padding ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Object fields:¶
Class-Num: Indicates that it's a Pad Object. The value is TBD5.¶
C-Type: The value is 0.¶
Length: Length of the object, measured in octets, including the Object Header and payload.¶
Object payload: Following the Pad Object Header is the Pad Object Payload, which SHOULD be filled by a sequence of pseudorandom numbers, or MAY be filled with all zeros. An implementation MUST control the content of the Pad Object Payload field..¶
The ICMP Query Response message is defined for both ICMPv4 and ICMPv6. Like any ICMP message, the ICMP Query Response message is encapsulated in an IP header. The ICMPv4 version of the Query Response message is encapsulated in an IPv4 header, while the ICMPv6 version is encapsulated in an IPv6 header.¶
The ICMP Query Response message has the following format:¶
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Type = TBD3/4 | Code | Checksum | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Identifier | Sequence Number | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | ICMP Extension Structure
IP Header fields:¶
Source Address: Copied from the Destination Address field of the invoking ICMP Query Request packet.¶
Destination Address: Copied from the Source Address field of the invoking ICMP Query Request packet.¶
ICMP fields:¶
Type: ICMP Query Response. The value is TBD3 for ICMPv4 and TBD4 for ICMPv6.¶
Code: The values are (0) No Error, (1) Malformed Query, (2) Unrecognized Query Request Object, and (3) Request Denied. See Section 5 for details.¶
Identifier: Copied from the Identifier field of the invoking ICMP Query Request message.¶
Sequence Number: Copied from the Sequence Number field of the invoking ICMP Query Request message.¶
Following the ICMP Query Response header, it's an ICMP Extension Structure as specified in Sections 7 and 8 of [RFC4884], continuing to the end of the packet.¶
Nothing can be added after the ICMP Extension Structure.¶
One or more Query Response Objects MUST be encapsulated in an ICMP Extension Structure of the ICMP Query Response message.¶
Each Query Response Object has the following format:¶
0 1 2 3 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 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | Length | Class-Num | C-Type | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ | | ~ Query Response Object Payload ~ | | +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Object fields:¶
Class-Num: Indicates the class of replied IP node information. The value will be requested by a separate document.¶
C-Type: Indicates the sub-type of replied IP node information. The value will be requested by a separate document.¶
Length: Length of the object, measured in octets, including the Object Header and payload.¶
Object payload: Following the Query Response Object Header is the Query Response Object Payload, which is the replied IP node information. The length of this field is variable. The value will be defined by a separate document.¶
The Code field in the ICMP Query Response MUST be set to (1) Malformed Query if any of the following conditions apply:¶
The ICMP Query Request does not include an ICMP Extension Structure.¶
The ICMP Extension Structure checksum is 0 or incorrect.¶
The ICMP Query Request is otherwise malformed.¶
The Code field in the ICMP Query Response MUST be set to (2) Unrecognized Query Request Object if any of the following conditions apply:¶
Section 4.6 of [RFC4884] provides a list of extensible ICMP messages (i.e., messages that can carry the ICMP Extension Structure). This document adds the ICMP Query Request message and the ICMP Query Response message to that list.¶
This document requests the following actions from IANA:¶
Add the following ICMPv6 Type to the "ICMPv6 'type' Numbers" registry:¶
Add the following Codes to the "Type TBD3 - Query Response" subregistry:¶
Add the following ICMPv6 Type to the "ICMPv6 'type' Numbers" registry:¶
Add the following Codes to the "Type TBD4 - Query Response" subregistry:¶
Add the following Class-Num to the "ICMP Extension Object Classes and Class Sub-types" registry:¶
(TBD5) Pad Object¶
Add the following C-type to the "Sub-types - Class TBD5 - Pad Object" subregistry:¶
(0) Reserved¶
C-Type values are assigned on a First Come First Serve (FCFS) basis with a range of 0-255.¶
All codes mentioned above are assigned on an FCFS basis with a range of 0-255.¶
Security issues discussed in [RFC4884] apply to this document.¶
This document recommends using IP Authentication Header [RFC4302] or IP Encapsulating Security Payload Header [RFC4303] to provide integrity protection for replied IP node information.¶
This document recommends using IP Encapsulating Security Payload Header [RFC4303] to provide privacy protection for replied IP node information.¶
This document recommends that the network operators establish policies that restrict access to ICMP Query functionality. In order to enforce these policies, nodes that support ICMP Query functionality MUST support the following configuration options:¶
Enable/disable ICMP Query functionality. By default, ICMP Query functionality is disabled.¶
Define the prefixes from which ICMP Query Request messages are permitted.¶
In order to protect local resources, implementations SHOULD rate-limit incoming ICMP Query Request messages.¶
To avoid the potential amplification attack, an implementation that supports this specification MUST ensure that the Query Response message must never be larger than the Query Request message.¶
TBA.¶