ULP Framing for TCP
draft-ietf-tsvwg-tcp-ulp-frame-01
| Document | Type | Expired Internet-Draft (tsvwg WG) | |
|---|---|---|---|
| Last updated | 2001-11-29 | ||
| Stream | IETF | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
pdf
htmlized
bibtex
|
||
| Stream | WG state | WG Document | |
| Document shepherd | No shepherd assigned | ||
| IESG | IESG state | Expired | |
| Consensus Boilerplate | Unknown | ||
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-ietf-tsvwg-tcp-ulp-frame-01.txt
https://www.ietf.org/archive/id/draft-ietf-tsvwg-tcp-ulp-frame-01.txt
Abstract
The TCP ULP Framing (TUF) protocol defines a shim layer protocol between an Upper Layer Protocol (ULP) and TCP. TUF also depends on a specified TCP segmentation convention between TUF endpoints. Together, the shim and segmentation conventions enable a TUF/TCP receiver to recognize ULP data units within a TCP segment independently of other TCP segments.
Authors
Scott Bailey (baileyse@us.ibm.com)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)