Tracing Requirements for Generic Tunnels
RFC 3609, “Tracing Requirements for Generic Tunnels”, is an Informational document published in October 2003 by R. Bonica, K. Kompella, D. Meyer. The canonical text is published by the RFC Editor.
Abstract
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.
What “Informational” means
Published for the general information of the community. It does not define an IETF standard and carries no standards-track status.
The canonical text of RFC 3609 is hosted at rfc-editor.org. Available in TXT,HTML.
- RFC 3608 Session Initiation Protocol Extension Header Field for Service Route Discovery During Registration
- RFC 3610 Counter with CBC-MAC
- RFC 3607 Chinese Lottery Cryptanalysis Revisited: The Internet as a Codebreaking Tool
- RFC 3611 RTP Control Protocol Extended Reports
- RFC 3606 Definitions of Supplemental Managed Objects for ATM Interface
- RFC 3612 Applicability Statement for Restart Mechanisms for the Label Distribution Protocol
- RFC 3605 Real Time Control Protocol attribute in Session Description Protocol
- RFC 3613 Definition of a Uniform Resource Name Namespace for the Middleware Architecture Committee for Education