Requirements for Host-to-Network Collaboration Signaling
draft-kwbdgrr-tsvwg-net-collab-rqmts-04
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | John Kaippallimalil , Dan Wing , Sri Gundavelli , Sridharan Rajagopalan , Spencer Dawkins , Mohamed Boucadair | ||
| Last updated | 2025-04-17 (Latest revision 2024-10-14) | ||
| Replaces | draft-rwbr-tsvwg-signaling-use-cases | ||
| 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
Collaborative signaling from host-to-network (i.e., client-to-network and server-to-network) can improve the user experience by informing the network about the nature and relative importance of packets (frames, streams, etc.) without having to disclose the content of the packets. Moreover, the collaborative signaling may be enabled so that clients and servers are aware of the network's treatment of incoming packets. Also, client-to-network collaboration can be put in place without revealing the identity of the remote servers. This collaboration allows for differentiated services at the network (e.g., packet discard preference), the sender (e.g., adaptive transmission), or through cooperation of server/client and the network. This document lists some use cases that illustrate the need for a mechanism to share metadata and outlines host-to-network requirements. The document focuses on signaling information about a UDP transport flow (UDP 4-tuple).
Authors
John Kaippallimalil
Dan Wing
Sri Gundavelli
Sridharan Rajagopalan
Spencer Dawkins
Mohamed Boucadair
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)