Internet Control Message Protocol (ICMPv6) Reflection

The ICMPv6 Reflection utility is an IPv6 diagnostic tool. It is similar to Ping and the ICMPv6 Probe utility in the following respects: A probing node sends an ICMPv6 message to a probed node. This ICMP message requests that it be reflected back to the probing node. The probed node receives the above-mentioned message, encodes it into another ICMPv6 message, and sends that ICMPv6 message back to the probing node. For the purposes of this document, the ICMPv6 message that the probing node sends is called the "request message" and the ICMPv6 message that the probed node sends is called the "reply message". The reply message includes a copy of the request message, starting from its IPv6 header, as was when it arrived at the probed node. The ICMPv6 Reflection utility uses the ICMPv6 Extended Echo Request and Extended Echo Reply message types . Each of these message types includes an ICMP Extension Structure . The ICMP Extension Structure includes one or more extension objects. This document defines the 'Reflect All' object, which is used for reflecting the request message, as it arrived at the probed node. An alternative approach involves the probing node sending a UDP packet with an unused destination port to the probed node. This causes the probed node to send an ICMPv6 Destination Unreachable message, which includes "as much of invoking packet as possible without the ICMPv6 packet exceeding the minimum IPv6 MTU" . However, middle boxes modify the invoking packet in ICMPv6 Destination Unreachable messages (e.g. ). By contrast, middle boxes are not intended to modify the Reflect All object.

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 when, and only when, they appear in all capitals, as shown here.

The following protocols define mutable IPv6 extension headers that can be used to trace a path and its performance: IPv6 Options for In Situ Operations, Administration, and Maintenance (IOAM) Inband Flow Analyzer Path Tracing in SRv6 networks These extensions are used to collect information along a packet's delivery path. Currently, the collected information is sent to a controller for processing. However, in some cases this information is relevant to the sender. The ICMPv6 Reflection utility provides a mechanism by which this information can be returned to the probing node. The ICMPv6 Reflection utility can also be used to determine how the probe message's IPv6 header has changed along its delivery path. For example, it can be used to determine how middleboxes have changed the Source Address, Destination Address, and Flow Label.

The probing node sends an ICMPv6 Extended Echo Request message to the probed node. The ICMPv6 Extended Echo Request message contains an ICMP Extension Structure and the ICMP Extension Structure contains an Extension Header. The ICMP Extension Header MUST include the Length field, as defined in . The ICMP Extension structure includes a 'Reflect All' object, which is defined in this document. The 'Reflect All' object contains an object payload field whose length SHOULD be sufficient to carry the IPv6 and ICMP header of the reflected request message. The total length of both the request and reply packets SHOULD NOT exceed the IPv6 minimum MTU (1280 bytes), to avoid triggering fragmentation. The probed node receives the ICMPv6 Extended Echo Request and formats an ICMPv6 Extended Echo Reply message. The total length of the ICMPv6 Extended Echo Reply message MUST be equal to the total length of the corresponding request message. The main body of the ICMPv6 Extended Echo Reply message reflects the status of an interface on the probed node. The ICMPv6 Extended Echo Reply message also contains an ICMP Extension Structure. The ICMP Extension Header MUST include the Length field, as defined in . The value of the Length field in the reply message MUST be equal to the value of the Length in the ICMP Extension Header of the request message. The ICMP Extension Structure also MUST contain the 'Reflect All' object that the ICMPv6 Extended Echo Request message contained. The length of the 'Reflect All' object in the reply message MUST be equal to the length of the 'Reflect All' object in the request message. If the following requirements are satisfied, the probed node populates the payload field of the 'Reflect All' object: The probed node supports the 'Reflect All' object. Responding to the request message does not violate the probed node's security policy. Otherwise, the probed node sets the object payload field to all zeros. An example of a request and a reply is provided in . In this example the request message includes the 'Reflect All' object. The reply also includes the 'Reflect All' object, containing the IPv6 header, ICMPv6 header and ICMP Extension Header of the request message. The request and reply messages have the same length. The length of the IPv6 header of the request message is at least 40 octets, depending on whether there are extension headers, followed by an 8-octet ICMPv6 header, a 4-octet ICMP Extension Header, and a 4-octet Object Header. For example, if the length of the IPv6 header is H octets, and the length of the object payload is H+12 octets, the reply includes the reflected request message starting from the IPv6 header and up to and including the ICMP Extension Header, as shown in . Middle boxes must not modify the Reflect All extension object. This ensures that the reflected information reaches the probing node exactly as sent by the probed node.

If a node that does not support the 'Reflect All' object receives an ICMP Extended Echo Request containing this object, the expected behavior according to and is to respond with an ICMP Echo Reply message that includes the "Malformed Query" code in the Code field.

This document defines the 'Reflect All' object. An implementation that supports ICMPv6 Reflection MUST support the 'Reflect All' object. In the ICMPv6 Reflection utility, the 'Reflect All' object MUST be included in the Extension Structure. If there is more than one object, the 'Reflect All' object MUST be the first object. An ICMPv6 message MUST NOT include more than one 'Reflect All' object. The structure of the 'Reflect All' object follows the specification of ICMP Extension Objects as defined in and MUST include the following fields: The Length of the 'Reflect All' object. An object class (as specified in ). C-Type as described below. An object payload field. The Length field specifies the number of octets in the object. The Length in the 'Reflect All' object of a reply message MUST be equal to the Length in the 'Reflect All' object of the respective request message. The C-Type value is used for indicating whether the probed node was able to process the object. The following C-Type values are supported: (0) Request (1) Reply - No Error (2) Reply - Unsupported Object The C-Type field of a Reflection object in a request message MUST be set to the 'Request' value. If the probed node is able to process the 'Reflect All' object, it MUST copy the request message into the object payload and update the C-Type field to the 'Reply - No Error' value. If the probed node is not able to process the object, it MUST update the C-Type value of the object in the Extended Echo Reply to 'Reply - Unsupported Object'. The object payload field in the ICMPv6 Extended Echo Request message is a placeholder for the corresponding reply message. Its length determines the number of bytes, starting from the beginning of the IPv6 header, that the probed node includes in the object payload of the reply. The object payload field in a request message MAY contain all zeros. Alternatively, this field MAY contain arbitrary data. In reply messages the object payload field MUST contain the received request message starting from the beginning of the IPv6 header and according to the length of the object payload, provided that the probed node supports the 'Reflect All' object and that responding does not conflict with its security policy. If the 'Reflect All' object is sufficiently long, the reply message includes the initial octets of the 'Reflect All' object. A notable use case for including arbitrary data in the object payload is the inclusion of a transmission timestamp, similar to how conventional Ping utilities incorporate timestamps into the ICMP payload. If the initial octets of the 'Reflect All' object payload contain a timestamp and the object is long enough, the timestamp is reflected back to the probing node, enabling round-trip time calculations.

IANA is requested to allocate the following values in the "ICMP Extension Object Classes and Class Sub-types" registry.

For each of the object classes above the following C-Type values are defined: (0) Request (1) Reply - No Error (2) Reply - Unsupported Object

Since this document uses technologies from , , and , it inherits security considerations from those documents. The Reflection procedure that is defined in this document is symmetric in terms of the length of the request and reply messages. This symmetry mitigates the potential for amplification attacks, which would be possible if the reply message was longer than the request message. Depending on the network policy and the location of nodes in the network, ICMPv6 informational and/or error messages are sometimes filtered or not supported. For example, some nodes do not reply to ICMPv6 Echo or do not send ICMPv6 Time Exceeded messages (used in Traceroute), due to policy considerations that may be related to DoS mitigation or to privacy. Network operators SHOULD apply similar considerations to ICMPv6 Extended Echo messages when they are used for Reflection. For example, an operator can choose to disable support for ICMPv6 Reflection in networks or in nodes that do not respond to ICMPv6 Echo and/or do not generate ICMPv6 Time Exceeded messages. As specified in , in order to protect local resources, implementations SHOULD rate-limit incoming ICMP Extended Echo Request messages. Moreover, as per , by default, ICMP Extend Echo functionality is disabled.

The authors gratefully acknowledge Sebastian Moeller, Zafar Ali, Bob Hinden, Jen Linkova, Jeremy Duncan, Greg Mirsky, Nick Buraglio and Maciej Zenczykowski for their insightful comments.