datatracker.ietf.org
Sign In
Version 4.50, 2013-05-15
Report a bug

Tracing Requirements for Generic Tunnels
draft-ietf-ccamp-tracereq-05

RFC
Document Stream: IETF
Last updated: 2003-06-09
Intended RFC status: Informational
Other versions: (expired, archived): plain text, pdf, html

Document shepherd:(None)
Shepherd writeup
Consensus:Unknown

IESG State: RFC 3609
Responsible AD: Bert Wijnen
IESG Note: Published as RFC3609
Send notices to: <ronald.p.bonica@mci.com>, <kireeti@juniper.net>

This Internet-Draft is no longer active. Unofficial copies of old Internet-Drafts can be found here:
http://tools.ietf.org/id/draft-ietf-ccamp-tracereq.

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.

Authors:
David Meyer <dmm@maoz.com>
Kireeti Kompella <kireeti@juniper.net>
Ron Bonica <ronald.p.bonica@mci.com>

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid)