TAP
draft-bernstein-tap-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Daniel J. Bernstein | ||
| Last updated | 1992-05-19 | ||
| 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
It is common for Internet hosts to associate a relatively long-lived identifier, commonly a 'username' or 'owner name,' to each TCP connection. TAP announces the identifier associated with a particular TCP connection to the host on the other end of the connection. TAP may be used on any host which associates a relatively long-lived identifier to each connection.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)