Generic Internet Signaling Transport over DCCP and DTLS
draft-manner-nsis-gist-dccp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jukka Manner | ||
| Last updated | 2007-06-15 | ||
| 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
The General Internet Signaling Transport (GIST) protocol specification supports two transport modes: UDP for very infrequent messaging, and TCP for all other cases. However, with TCP comes certain undesirable features, e.g., head of line blocking, which affect performance when a number of sessions are multiplexed over the same TCP connection. In certain environments and deployment scenarios, an unreliable, but still congestion controlled, transport would be needed. This specification proposes DCCP as a transport protocol for GIST.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)