Skip to main content

Extending ICMP for Interface and Next-Hop Identification
RFC 5837

Revision differences

Document history

Date By Action
2018-12-20
(System)
Received changes through RFC Editor sync (changed abstract to 'This memo defines a data structure that can be appended to selected ICMP messages. The ICMP …
Received changes through RFC Editor sync (changed abstract to '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]')
2017-05-16
(System) Changed document authors from "Naiming Shen, Ron Bonica, Carlos Pignataro" to "Naiming Shen, Ron Bonica, Carlos Pignataro, Alia Atlas, JR. Rivers"
2015-10-14
(System) Notify list changed from akatlas@google.com, draft-atlas-icmp-unnumbered@ietf.org, watkinal@us.ibm.com to watkinal@us.ibm.com, akatlas@google.com
2010-04-21
Amy Vezza State Changes to RFC Published from RFC Ed Queue by Amy Vezza
2010-04-21
Amy Vezza [Note]: 'RFC 5837' added by Amy Vezza
2010-04-20
(System) RFC published