database logo graphic

RFC 5837

"Extending ICMP for Interface and Next-Hop Identification", April 2010

Canonical URL:
http://www.rfc-editor.org/rfc/rfc5837.txt
This document is also available in this non-normative format: PDF.
Status:
PROPOSED STANDARD
Authors:
A. Atlas, Ed.
R. Bonica, Ed.
C. Pignataro, Ed.
N. Shen
JR. Rivers
Stream:
IETF
Source:
NON WORKING GROUP

Cite this RFC: TXT  |  XML

Other actions: Find Errata (if any)  |  Submit Errata  |  Find IPR Disclosures from the IETF


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]


For the definition of Status, see RFC 2026.

For the definition of Stream, see RFC 4844.


Go to the RFC Editor Homepage.