End-by-Hop Transmission Protocol
draft-bogdanov-ehtp-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Alexander Bogdanov | ||
| Last updated | 2002-07-25 | ||
| 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
End-by-Hop Transmission Protocol (EHTP) is the connection-oriented transport service for the reliable or unreliable delivery of data packets with possible violation of a sequence. It has the own address space compatible with Unified Memory Space Protocol (UMSP, RFC3018 [5]). EHTP includes the gateway protocol, which supports labels and dynamic resources deallocating. Networks with non- overlapping or incompatible addresses space may be united at EHTP layer with end-to-end interaction and with preservation of a transparency.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)