Active Traceback Protocol
draft-yamada-active-trace-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Tatsuya Yamada | ||
| Last updated | 2002-10-30 | ||
| 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
General traceback protocols (e.g. itrace) only consider to send traceback information from Generator to Tracer. But they are not helpful when victims and/or Tracer want to know who attacks them because of conventional traceback mechanisms have not been reflected in Tracer intention. Therefore this draft proposes an additional protocol for conventional traceback protocols, especially itrace, to reflect in Tracer intention and be able to control generation of traceback information by Generator.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)