Probe a specific interface with ICMP Extended Echo under authorization

Use this document to connect an official requirement or behavior to observable evidence: Probe a specific interface with ICMP Extended Echo under authorization. Only the official source and traced locations below supply facts. Confirm applicability before acting.

Source fact:

The official RFC 8335 — PROBE: A Utility for Probing Interfaces from RFC Editor / Internet Engineering Task Force supports the following bounded statements:

• An ICMP Extended Echo Request MUST contain exactly one Interface Identification Object; with L set it may identify a local interface by name, index, or address, while L clear requires an address. The research record locates this support at Section 2 (ICMP Extended Echo Request).
• A node MUST silently discard an Extended Echo Request unless the feature, L-bit setting, query type, and source are explicitly authorized and the source is unicast and destination is not multicast. The research record locates this support at Section 4 (ICMP Message Processing).
• Supporting nodes MUST offer controls for enabling Extended Echo, permitted L-bit settings, query types, and source prefixes; the feature and all query types are disabled by default. The research record locates this support at Section 8 (Security Considerations).

Only the traced statements above are asserted as source facts. Apply the review to address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains after confirming that the source and deployed context match.

What the source does not establish

This RFC evidence supports only the named network-protocol decision; it does not select vendor settings, topology, capacity, or an acceptable failure mode. A correct source interpretation can still be inapplicable to a particular design. Confirm DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, ownership, and change authority instead of treating documented behavior as a deployment guarantee.

Applicability questions

• For source statement 1 at Section 2 (ICMP Extended Echo Request), which observable configuration, record, or test can confirm applicability here?
• For source statement 2 at Section 4 (ICMP Message Processing), which observable configuration, record, or test can confirm applicability here?
• For source statement 3 at Section 8 (Security Considerations), which observable configuration, record, or test can confirm applicability here?
• Within address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, which versions, roles, and configuration states define the review population?
• Could DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring invalidate the test, hide a failure, or change applicability?
• Who owns the decision, and which observation requires stopping, escalation, or rollback?

DSE recommendation:

DSE recommends using the cited source as the evidence anchor for this decision. Begin by recording scope and current state before deciding whether a change is warranted. Record the source location, examined part of address plans, interfaces, routes, peers, protocol roles, timers, middleboxes, and intended failure domains, observed and expected states, owner, and reason for deviation.

Translate the conclusion into change control only after documenting dependencies, impact, test method, expected signals, failure signals, and restoration steps. Include DNS, Active Directory authentication, PKI, time, routing policy, transport reachability, and monitoring, while excluding secrets and sensitive personal or topology data from ordinary tickets.

Verification and evidence

Build a reproducible chain from Section 2 (ICMP Extended Echo Request); Section 4 (ICMP Message Processing); Section 8 (Security Considerations) to the observed environment. Useful domain evidence includes configuration snapshots, route or neighbor state, packet captures, counters, topology records, and controlled failover results; label every item with scope, timestamp, collector, and stable identifier.

Close the review only when the evidence, exception handling, resulting action, and after-state are linked. Schedule a new review after material technical, organizational, incident, or source changes; today’s observation is not a continuing guarantee.

Official references

• RFC 8335 — PROBE: A Utility for Probing Interfaces — RFC Editor / Internet Engineering Task Force