Extending ICMP for Interface and Next-Hop Identification
RFC 5837, “Extending ICMP for Interface and Next-Hop Identification”, is a Proposed Standard document published in April 2010 by A. Atlas, R. Bonica, C. Pignataro, N. Shen, JR. Rivers. The canonical text is published by the RFC Editor.
Abstract
This memo defines a data structure that can be appended to selected ICMP messages. The ICMP extension defined herein can be used to identify any combination of the following: the IP interface upon which a datagram arrived, the sub-IP component of an IP interface upon which a datagram arrived, the IP interface through which the datagram would have been forwarded had it been forwardable, and the IP next hop to which the datagram would have been forwarded.
Devices can use this ICMP extension to identify interfaces and their components by any combination of the following: ifIndex, IPv4 address, IPv6 address, name, and MTU. ICMP-aware devices can use these extensions to identify both numbered and unnumbered interfaces. [STANDARDS-TRACK]
What “Proposed Standard” means
An entry-level standards-track specification: stable, peer-reviewed and a solid basis for implementation, though it may still evolve before becoming an Internet Standard.
The canonical text of RFC 5837 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 5836 Extensible Authentication Protocol Early Authentication Problem Statement
- RFC 5838 Support of Address Families in OSPFv3
- RFC 5835 Framework for Metric Composition
- RFC 5839 An Extension to Session Initiation Protocol Events for Conditional Event Notification
- RFC 5834 Control and Provisioning of Wireless Access Points Protocol Binding MIB for IEEE 802.11
- RFC 5840 Wrapped Encapsulating Security Payload for Traffic Visibility
- RFC 5833 Control and Provisioning of Wireless Access Points Protocol Base MIB
- RFC 5841 TCP Option to Denote Packet Mood