Subject: [Taps] New Version Notification for draft-tiesel-taps-socketintents-01.txt

From: "Philipp S. Tiesel" <[email-masked]>
Date: Mon, 30 Oct 2017 21:15:57 +0100

Hi,

We’ve updated our Internet Draft on Socket Intents.

Socket Intents are a generic mechanism for applications to express non-requirement performance preferences, like optimize for bandwidth or latency, and applications’ knowledge, like expected bandwidth usage.   
Socket Intents are specified in a portable way and can be added to any transport API, including Post Sockets, the NEAT API or, with limitations, to regular BSD sockets.

With this second version, I want to raise a few questions.

 - Are Socket Intents easy enough?

 - Is the structure of Socket Intent Types sufficient to express
   all anticipated future  non-requirement performance preferences
   and application knowledge?

 - What Socket Intent Types / kinds of information are missing?

 - Does the current abstract definition of Socket Intents
   fit the way the IETF specifies abstract APIs?

We are looking forward to an active discussion here and in Singapore and hope that we find a way to push Socket Intents forward.

AVE!
  Philipp S. Tiesel / phils…

> Begin forwarded message:
> 
> A new version of I-D, draft-tiesel-taps-socketintents-01.txt
> has been successfully submitted by Philipp S. Tiesel and posted to the
> IETF repository.
> 
> Name:		draft-tiesel-taps-socketintents
> Revision:	01
> Title:		Socket Intents
> Document date:	2017-10-27
> Group:		Individual Submission
> Pages:		15
> URL:            https://www.ietf.org/internet-drafts/draft-tiesel-taps-socketintents-01.txt
> Status:         https://datatracker.ietf.org/doc/draft-tiesel-taps-socketintents/
> Htmlized:       https://tools.ietf.org/html/draft-tiesel-taps-socketintents-01
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-tiesel-taps-socketintents-01
> Diff:           https://www.ietf.org/rfcdiff?url2=draft-tiesel-taps-socketintents-01
> 
> 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.
> 
> 
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> The IETF Secretariat
>