Movatterモバイル変換


[0]ホーム

URL:


Search RFCs

Advanced Search

RFC Editor

RFC 5837

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

File formats:
icon for text fileicon for PDFicon for HTML
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  |  BibTeX

DOI:  https://doi.org/10.17487/RFC5837

Discuss this RFC: Send questions or comments to the mailing listiesg@ietf.org

Other actions:Submit Errata  | Find IPR Disclosures from the IETF  | View History of RFC 5837


Abstract

This memo defines a data structure that can be appended to selectedICMP messages. The ICMP extension defined herein can be used toidentify any combination of the following: the IP interface uponwhich a datagram arrived, the sub-IP component of an IP interfaceupon which a datagram arrived, the IP interface through which thedatagram would have been forwarded had it been forwardable, and theIP next hop to which the datagram would have been forwarded.

Devices can use this ICMP extension to identify interfaces and theircomponents by any combination of the following: ifIndex, IPv4address, IPv6 address, name, and MTU. ICMP-aware devices can usethese extensions to identify both numbered and unnumbered interfaces. [STANDARDS-TRACK]


For the definition ofStatus,seeRFC 2026.

For the definition ofStream, seeRFC 8729.




IABIANAIETFIRTFISEISOCIETF Trust
ReportsPrivacy StatementSite MapContact Us

Advanced Search

[8]ページ先頭

©2009-2026 Movatter.jp