RFC 5837: Extending ICMP for Interface and Next-Hop Identification

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…

Read RFC 5837 on the RFC Editor

Outgoing relationships (11 related RFCs)

Normative reference — RFC 2119: Key words for use in RFCs to Indicate Requirement Levels
Normative reference — RFC 3629: UTF-8, a transformation format of ISO 10646
Normative reference — RFC 792: Internet Control Message Protocol
Normative reference — RFC 2863: The Interfaces Group MIB
Normative reference — RFC 4443: Internet Control Message Protocol (ICMPv6) for the Internet Protocol Version 6 (IPv6) Specification
Normative reference — RFC 4884: Extended ICMP to Support Multi-Part Messages
Informative reference — RFC 1122: Requirements for Internet Hosts - Communication Layers
Informative reference — RFC 1812: Requirements for IP Version 4 Routers
Informative reference — RFC 3022: Traditional IP Network Address Translator (Traditional NAT)
Informative reference — RFC 2277: IETF Policy on Character Sets and Languages
Informative reference — RFC 5508: NAT Behavioral Requirements for ICMP

Incoming relationships (7 related RFCs)

Normatively referenced by — RFC 6791: Stateless Source Address Mapping for ICMPv6 Packets
Informatively referenced by — RFC 7276: An Overview of Operations, Administration, and Maintenance (OAM) Tools
Informatively referenced by — RFC 7439: Gap Analysis for Operating IPv6-Only MPLS Networks
Informatively referenced by — RFC 9259: Operations, Administration, and Maintenance (OAM) in Segment Routing over IPv6 (SRv6)
Informatively referenced by — RFC 9692: RIFT: Routing in Fat Trees
Informatively referenced by — RFC 6860: Hiding Transit-Only Networks in OSPF
Informatively referenced by — RFC 6752: Issues with Private IP Addressing in the Internet