Use Cases for SPUD
draft-yw-spud-use-cases-00
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Jianjie You , Xinpeng Wei | ||
| Last updated | 2015-12-30 (Latest revision 2015-06-28) | ||
| Stream | (None) | ||
| Formats |
Expired & archived
plain text
htmlized
pdfized
bibtex
|
||
| 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) |
https://www.ietf.org/archive/id/draft-yw-spud-use-cases-00.txt
Abstract
The purpose of SPUD is to provide a standardized layer below the transport layer, to behavior as a communication channel between the host and network devices. So when a new transport protocol is deployed, it's easy for network devices to cooperate with it. New transports could have a common encapsulation to middleboxes. On the other hand, the transport layer could also make use of the state of network devices collected by the SPUD, to improve transport performance. This document provides some exemplary use cases for SPUD, especially in stateful firewall and TCP optimization. The objective of this draft is not to cover all conceivable p2a or a2p signaling in detail. Rather, the intention is to explain the requirements in these use cases as far as it is required to complement the problem statement of the SPUD.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)