Tracing Requirements for Generic Tunnels
draft-bonica-tunneltrace-03
Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
---|---|---|---|
Authors | Ron Bonica , Kireeti Kompella , David Meyer | ||
Last updated | 2002-06-07 | ||
RFC stream | (None) | ||
Intended RFC status | (None) | ||
Formats | |||
Stream | Stream state | (No stream defined) | |
Consensus boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | Expired | |
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document specifies requirements for a generic route tracing application. The application must provide all functionality that 'traceroute' [RFC 2151] currently provides. It also must provide enhanced capabilities with regard to tunnel tracing (e.g., tracing through IP-in-IP tunnels, tracing through MPLS LSPs).
Authors
Ron Bonica
Kireeti Kompella
David Meyer
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)