A Proposal for Generic Traceroute Over Tunnels
draft-fu-ccamp-traceroute-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Last updated | 2003-06-26 | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-fu-ccamp-traceroute-00.txt
Abstract
We identify some issues for generic traceroute for tunnels (tunnel- trace): (1) it is possible that some IP hops do not support tunneltrace, (2) for each tunnel wishing to be traced, at least the two end points should support the tunneltrace, (3) tracing message should be able to by-pass firewalls and NATs. One possible solution, based on the CASP signaling protocol (stateless mode), is proposed to support generic routetracing over tunnels.
Authors
Xiaoming Fu
(fu@cs.uni-goettingen.de)
Rene Soltwisch
(soltwisch@cs.uni-goettingen.de)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)