RFC 3609: Tracing Requirements for Generic Tunnels
In plain English — editorial summary, not part of the RFC
This document specifies requirements for a generic route-tracing application. It also specifies requirements for a protocol that will support that application. Network operators will use the generic route-tracing application to verify proper operation of the IP forwarding plane. They will also use the application to discover details regarding tunnels that support IP forwarding. The generic route-tracing application, specified herein, supports a superset of the functionality that "traceroute" currently offers. Like traceroute, the generic route-tracing application can discover the forwarding path between two interfaces that are contained by an IP network. Unlike traceroute, this application can reveal details regarding tunnels that support the IP forwarding path.
Document record
- Document ID
- RFC3609
- Published
- October 2003
- Authors
- R. Bonica; K. Kompella; D. Meyer
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- rtg
- Pages
- 9
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3242RObust Header Compression (ROHC): A Link-Layer Assisted Profile for IP/UDP/RTPObsoleted
April 2002
- RFC 3376Internet Group Management Protocol, Version 3Obsoleted
October 2002
- RFC 3077A Link-Layer Tunneling Mechanism for Unidirectional LinksCurrent
March 2001
- RFC 3033The Assignment of the Information Field and Protocol Identifier in the Q.2941 Generic Identifier and Q.2957 User-to-user Signaling for the Internet ProtocolCurrent
January 2001
- RFC 2584Definitions of Managed Objects for APPN/HPR in IP NetworksCurrent
May 1999
- RFC 5302Domain-Wide Prefix Distribution with Two-Level IS-ISCurrent
October 2008
- RFC 3678Socket Interface Extensions for Multicast Source FiltersCurrent
January 2004
- RFC 3738Wave and Equation Based Rate Control (WEBRC) Building BlockCurrent
April 2004
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?