ICMP Query for IP Node Information
draft-xbm-intarea-icmp-query-01
This document is an Internet-Draft (I-D).
Anyone may submit an I-D to the IETF.
This I-D is not endorsed by the IETF and has no formal standing in the
IETF standards process.
| Document | Type | Active Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Xiao Min , Ron Bonica , Greg Mirsky | ||
| Last updated | 2026-06-16 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | I-D Exists | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
draft-xbm-intarea-icmp-query-01
INTAREA Working Group X. Min
Internet-Draft ZTE Corp.
Updates: 4884 (if approved) R. Bonica
Intended status: Standards Track HPE
Expires: 18 December 2026 G. Mirsky
Independent
16 June 2026
ICMP Query for IP Node Information
draft-xbm-intarea-icmp-query-01
Abstract
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.
Status of This Memo
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 18 December 2026.
Copyright Notice
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
Min, et al. Expires 18 December 2026 [Page 1]
Internet-Draft ICMP Query for IP Node Information June 2026
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.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. ICMP Query Request . . . . . . . . . . . . . . . . . . . . . 3
3.1. Query Request Objects . . . . . . . . . . . . . . . . . . 4
3.2. Pad Objects . . . . . . . . . . . . . . . . . . . . . . . 5
3.3. Query Pre-Request Object . . . . . . . . . . . . . . . . 5
4. ICMP Query Response . . . . . . . . . . . . . . . . . . . . . 6
4.1. Query Response Objects . . . . . . . . . . . . . . . . . 7
4.2. Query Pre-Response Object . . . . . . . . . . . . . . . . 8
5. Code Field Processing . . . . . . . . . . . . . . . . . . . . 9
6. Updates to RFC 4884 . . . . . . . . . . . . . . . . . . . . . 9
7. Operational Considerations . . . . . . . . . . . . . . . . . 10
8. Why Not Reuse Existing ICMP Types? . . . . . . . . . . . . . 10
9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 10
10. Security Considerations . . . . . . . . . . . . . . . . . . . 12
11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 13
12. References . . . . . . . . . . . . . . . . . . . . . . . . . 13
12.1. Normative References . . . . . . . . . . . . . . . . . . 13
12.2. Informative References . . . . . . . . . . . . . . . . . 14
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14
1. Introduction
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.
This document updates [RFC4884].
Min, et al. Expires 18 December 2026 [Page 2]
Internet-Draft ICMP Query for IP Node Information June 2026
2. Conventions Used in This Document
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.
3. ICMP Query Request
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
Figure 1: ICMP Query Request Message
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.
* Checksum: The same as defined in [RFC4443].
Min, et al. Expires 18 December 2026 [Page 3]
Internet-Draft ICMP Query for IP Node Information June 2026
* 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.
3.1. Query Request Objects
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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 2: Query Request Object
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.
Min, et al. Expires 18 December 2026 [Page 4]
Internet-Draft ICMP Query for IP Node Information June 2026
3.2. Pad Objects
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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 3: Pad Object
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..
3.3. Query Pre-Request Object
One Query Pre-Request Object MUST be encapsulated in an ICMP
Extension Structure of the ICMP Query Request message.
Query Pre-Request Object has the following format:
Min, et al. Expires 18 December 2026 [Page 5]
Internet-Draft ICMP Query for IP Node Information June 2026
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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Two-tuple1 (Class-Num, C-Type)| Two-tuple2 (Class-Num, C-Type)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Two-tuple3 (Class-Num, C-Type)| Two-tuple4 (Class-Num, C-Type)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Two-tuple5 (Class-Num, C-Type)| ......
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 4: Query Pre-Request Object
Object fields:
* Class-Num: Indicates that it's a Query Pre-Request Object. The
value is TBD6.
* C-Type: The value is 0.
* Length: Length of the object, measured in octets, including the
Object Header and payload.
* Object payload: Following the Query Pre-Request Object Header is
the Query Pre-Request Object Payload, which is a list of two-
tuples (Class-Num and C-Type) used to query what kinds of
information are supported by the ICMP Queried node. The length of
this field is variable. The value of each two-tuple will be the
same as what's assigned by IANA for each Query Request Object,
with an IANA request by a separate document.
4. ICMP Query Response
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:
Min, et al. Expires 18 December 2026 [Page 6]
Internet-Draft ICMP Query for IP Node Information June 2026
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
Figure 5: ICMP Query Response Message
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.
* Checksum: The same as defined in [RFC4443].
* 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.
4.1. Query Response Objects
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:
Min, et al. Expires 18 December 2026 [Page 7]
Internet-Draft ICMP Query for IP Node Information June 2026
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 ~
| |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 6: Query Response Object
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.
4.2. Query Pre-Response Object
One Query Pre-Response Object MUST be encapsulated in an ICMP
Extension Structure of the ICMP Query Response message.
Query Pre-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 |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Two-tuple1 (Class-Num, C-Type)| Two-tuple2 (Class-Num, C-Type)|
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Two-tuple3 (Class-Num, C-Type)| ......
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 7: Query Pre-Response Object
Object fields:
Min, et al. Expires 18 December 2026 [Page 8]
Internet-Draft ICMP Query for IP Node Information June 2026
* Class-Num: Indicates that it's a Query Pre-Response Object. The
value is TBD7.
* C-Type: The value is 0.
* Length: Length of the object, measured in octets, including the
Object Header and payload.
* Object payload: Following the Query Pre-Response Object Header is
the Query Pre-Response Object Payload, which is a list of two-
tuples (Class-Num and C-Type) used to respond the ICMP Querying
node what kinds of information are supported by the ICMP Queried
node. The length of this field is variable. The value of each
two-tuple is copied from the Query Pre-Request Object of the
invoking ICMP Query Request message.
5. Code Field Processing
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:
* The ICMP Extension Structure of the ICMP Query Request does not
include a Query Request Object.
* None of the Class-Num of the Query Request Object is recognized.
* None of the C-Type of the Query Request Object is recognized.
6. Updates to RFC 4884
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.
Min, et al. Expires 18 December 2026 [Page 9]
Internet-Draft ICMP Query for IP Node Information June 2026
7. Operational Considerations
To remove to potential of abusing ICMP Query as a means of attack
amplification, Pad Object defined in Section 3.2 MAY be included in
the ICMP Query Request message, to ensure that the Query Reply
message must never be larger than the invoking Query Request message.
To ensure the queried information is supported by the Queried node,
before sending the ICMP Query Request message containing one or more
Query Request Objects, the ICMP Querying node can send first an ICMP
Query Request message containing only one Query Pre-Request Object
defined in Section 3.3. And once receiving an ICMP Query Request
message containing only one Query Pre-Request Object, the ICMP
Queried node MUST respond an ICMP Query Response message containing
only one Query Pre-Response Object defined in Section 4.2, telling
the ICMP Querying node what kinds of information are supported by the
ICMP Queried node.
8. Why Not Reuse Existing ICMP Types?
[RFC4620] defines an experimental protocol using ICMPv6 type values
139/140. Section 4 of that RFC specifies the two types of Node
Information (NI) messages, the NI Query and the NI Reply, which can
be used to learn the addresses and names for nodes on the other end
of a point-to-point link or nodes on a shared-medium link such as an
Ethernet. [I-D.ietf-intarea-rfc8335bis] defines a network diagnostic
tool called PROBE using ICMP type values 42/43 and ICMPv6 type values
160/161. Sections 2 and 3 of that document specify the two types of
ICMP messages, the Extended Echo Request and the Extended Echo Reply,
which can be used to query the status of a probed interface. Whether
the NI Query/Reply or the Extended Echo Request/Reply are not
designed for a generic ICMP Query, so if reusing their ICMP type
values, some backward compatibility issues need to be resolved, which
means complexity and redundant fields.
9. IANA Considerations
This document requests the following actions from IANA:
* Add the following ICMPv4 Type to the "ICMP Type Numbers" registry:
- TBD1 Query Request
Add the following Code to the "Type TBD1 - Query Request"
subregistry:
- (0) No Error
Min, et al. Expires 18 December 2026 [Page 10]
Internet-Draft ICMP Query for IP Node Information June 2026
* Add the following ICMPv6 Type to the "ICMPv6 'type' Numbers"
registry:
- TBD2 Query Request
- As ICMPv6 distinguishes between informational and error
messages, and this is an informational message, the value must
be assigned from the range 128-255.
Add the following Code to the "Type TBD2 - Query Request"
subregistry:
- (0) No Error
* Add the following ICMPv4 Type to the "ICMP Type Numbers" registry:
- TBD3 Query Response
Add the following Codes to the "Type TBD3 - Query Response"
subregistry:
- (0) No Error
- (1) Malformed Query
- (2) Unrecognized Query Request Object
- (3) Request Denied
* Add the following ICMPv6 Type to the "ICMPv6 'type' Numbers"
registry:
- TBD4 Query Response
- As ICMPv6 distinguishes between informational and error
messages, and this is an informational message, the value must
be assigned from the range 128-255.
Add the following Codes to the "Type TBD4 - Query Response"
subregistry:
- (0) No Error
- (1) Malformed Query
- (2) Unrecognized Query Request Object
- (3) Request Denied
Min, et al. Expires 18 December 2026 [Page 11]
Internet-Draft ICMP Query for IP Node Information June 2026
* Add the following Class-Num to the "ICMP Extension Object Classes
and Class Sub-types" registry:
- (TBD5) Pad Object
- (TBD6) Query Pre-Request Object
- (TBD7) Query Pre-Response Object
Add the following C-type to the "Sub-types - Class TBD5 - Pad
Object" subregistry:
- (0) Reserved
Add the following C-type to the "Sub-types - Class TBD6 - Query
Pre-Request Object" subregistry:
- (0) Reserved
Add the following C-type to the "Sub-types - Class TBD7 - Query
Pre-Response Object" subregistry:
- (0) Reserved
C-Type values are assigned on a First Come First Serve (FCFS)
basis with a range of 0-255.
All subregistries mentioned above are requested to be newly created
by IANA and the subregistries will contain the new codes.
All codes mentioned above are assigned on an FCFS basis with a range
of 0-255.
10. Security Considerations
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.
Min, et al. Expires 18 December 2026 [Page 12]
Internet-Draft ICMP Query for IP Node Information June 2026
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.
11. Acknowledgements
The authors would like to acknowledge Sebastian Moeller, Paul Vixie,
Jen Linkova, and Dave Thaler for their valuable comments.
12. References
12.1. Normative References
[RFC792] Postel, J., "Internet Control Message Protocol", STD 5,
RFC 792, DOI 10.17487/RFC0792, September 1981,
<https://www.rfc-editor.org/info/rfc792>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>.
[RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet
Control Message Protocol (ICMPv6) for the Internet
Protocol Version 6 (IPv6) Specification", STD 89,
RFC 4443, DOI 10.17487/RFC4443, March 2006,
<https://www.rfc-editor.org/info/rfc4443>.
[RFC4884] Bonica, R., Gan, D., Tappan, D., and C. Pignataro,
"Extended ICMP to Support Multi-Part Messages", RFC 4884,
DOI 10.17487/RFC4884, April 2007,
<https://www.rfc-editor.org/info/rfc4884>.
Min, et al. Expires 18 December 2026 [Page 13]
Internet-Draft ICMP Query for IP Node Information June 2026
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
12.2. Informative References
[I-D.ietf-intarea-rfc8335bis]
Fenner, B., Bonica, R. P., Thomas, R., Linkova, J.,
Lenart, C., and M. Boucadair, "PROBE: A Utility for
Probing Interfaces", Work in Progress, Internet-Draft,
draft-ietf-intarea-rfc8335bis-04, 17 April 2026,
<https://datatracker.ietf.org/doc/html/draft-ietf-intarea-
rfc8335bis-04>.
[RFC4302] Kent, S., "IP Authentication Header", RFC 4302,
DOI 10.17487/RFC4302, December 2005,
<https://www.rfc-editor.org/info/rfc4302>.
[RFC4303] Kent, S., "IP Encapsulating Security Payload (ESP)",
RFC 4303, DOI 10.17487/RFC4303, December 2005,
<https://www.rfc-editor.org/info/rfc4303>.
[RFC4620] Crawford, M. and B. Haberman, Ed., "IPv6 Node Information
Queries", RFC 4620, DOI 10.17487/RFC4620, August 2006,
<https://www.rfc-editor.org/info/rfc4620>.
Authors' Addresses
Xiao Min
ZTE Corp.
Nanjing
China
Phone: +86 18061680168
Email: xiao.min2@zte.com.cn
Ron Bonica
HPE
United States of America
Email: ronald.bonica@hpe.com
Greg Mirsky
Independent
United States of America
Email: gregimirsky@gmail.com
Min, et al. Expires 18 December 2026 [Page 14]