Socket Intents
draft-tiesel-taps-socketintents-01

Document Type Expired Internet-Draft (individual)
Last updated 2018-05-01 (latest revision 2017-10-28)
Replaces draft-tiesel-socketintents
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-tiesel-taps-socketintents-01.txt

Abstract

This document outlines Socket Intents, a concept that allows applications to share their knowledge about upcoming communication and express their performance preferences in a generic, intuitive and, portable way. Using Socket Intents, an application can express what it knows, assumes, expects, or wants regarding its network communication. The information provided by Socket Intents can be used by the network stack to optimize communication in a best-effort way. Socket Intent can be used to stem against the complexity of exploiting transport diversity, e.g., to automate the choice among multiple paths, provisioning domains or protocols. By shifting this complexity from the application developer to the operating system, it enables the use of these transport features to a wider range of applications.

Authors

Philipp Tiesel (philipp@inet.tu-berlin.de)
Theresa Enghardt (theresa@inet.tu-berlin.de)
Anja Feldmann (anja@inet.tu-berlin.de)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)