Skip to main content

Socket Intents
draft-tiesel-socketintents-00

Document Type Replaced Internet-Draft (individual)
Authors Philipp S. Tiesel , Reese Enghardt
Last updated 2017-06-15
Replaced by draft-tiesel-taps-socketintents
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-tiesel-taps-socketintents
Telechat date (None)
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-socketintents-00.txt

Abstract

This document outlines an API-independent concept that allows applications to share their knowledge about upcoming communication and express their performance preferences in a portable and abstract way: Socket Intents. Socket Intents express what an application knows, assumes, expects or wants to prioritize regarding its own network communication. The information provided by Socket Intents should be taken into account by the network stack in a best-effort way. Socket Intent can be used to stem against the complexity and make use of multiple provisioning domains as well as new transport protocols and features available to a larger user base by expressing the applications intents in an abstract and portable way.

Authors

Philipp S. Tiesel
Reese Enghardt

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