TCP Performance Enhancing Proxy Terminology
draft-griner-tcppep-term-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jim Griner | ||
| Last updated | 1998-11-17 | ||
| 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 presents definitions for many terms to be used during the discussion of various TCP Performance Enhancing Proxies (PEP). A PEP, located between two end-systems, is used to, in some way, enhance a TCP connection. PEP's are commonly referred to as spoofing, connection splitting gateways, etc.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)