Subject: [Taps] Fwd: New Version Notification for draft-trammell-post-sockets-00.txt

From: Brian Trammell <[email-masked]>
Date: Thu, 27 Oct 2016 14:52:40 +0200

Greetings, TAPS,

We've submitted an initial version of our Post Sockets abstract interface draft, draft-trammell-post-sockets. It's not yet clear that we'd want this to be adopted by the TAPS working group for a future milestone in partial fulfillment of point 3 on the charter -- perhaps the ideas here are merely an illustration of what is possible in the space, that could point toward a more concrete definition of an abstract interface for TAPS.  We'd like to discuss this point in Seoul.

Thanks, cheers,

Brian

> Begin forwarded message:
> 
> From: [email-masked]
> Subject: New Version Notification for draft-trammell-post-sockets-00.txt
> Date: 27 October 2016 at 11:57:39 GMT+2
> To: "Mirja Kuehlewind" <[email-masked]>, "Tommy Pauly" <[email-masked]>, "Brian Trammell" <[email-masked]>, "Colin Perkins" <[email-masked]>
> 
> 
> A new version of I-D, draft-trammell-post-sockets-00.txt
> has been successfully submitted by Brian Trammell and posted to the
> IETF repository.
> 
> Name:		draft-trammell-post-sockets
> Revision:	00
> Title:		Post Sockets, An Abstract Programming Interface for the Transport Layer
> Document date:	2016-10-27
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-trammell-post-sockets-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-trammell-post-sockets/
> Htmlized:       https://tools.ietf.org/html/draft-trammell-post-sockets-00
> 
> 
> Abstract:
>   This document describes Post Sockets, an asynchronous abstract
>   programming interface for the atomic transmission of objects in an
>   explicitly multipath environment.  Post replaces connections with
>   long-lived associations between endpoints, with the possibility to
>   cache cryptographic state in order to reduce amortized connection
>   latency.  We present this abstract interface as an illustration of
>   what is possible with present developments in transport protocols
>   when freed from the strictures of the current sockets API.
> 
> 
> 
> 
> 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
>