The Post Sockets cabal was at IETF 103 in Bangkok in November 2018.
We gave an update on some recent changes to the Transport Services
Architecture to the
TAPS working group, and met separately to discuss the next steps
towards completing the work.
Welcome to Mihail Yanev, who started work as a research student under
my supervision today.
The Post Sockets cabal met at IETF 102 in Montreal in July 2018. We
gave several presentations to the TAPS working group, to review the
status of the Transport Services Architecture drafts, and also held
a side meeting to discuss next steps.
Slides from the presentations of our proposed transport services architecture
at the IETF 101 meeting in London, on 21 March 2018, are now available.
We've recently submitted two new drafts to the IETF, outlining a proposed
Transport Services
architecture
and associated
API,
along with a third draft giving some
implementation guidance.
These drafts represent the merger of the ideas from our Post Sockets
proposal, the EU NEAT project, and the Socket Intents project at TU-Berlin.
They will be presented in the TAPS working group session at
IETF 101 in London, on 21 March 2018.
The Post Sockets cabal met with friends from the EU
NEAT project, and others, to
discuss a unified proposal for the IETF Transport Services architecture
and associated API. This is intended to form the basis for future work
in the IETF TAPS
working group, and will be discussed in their upcoming meeting at
IETF 101 in London, in March 2018.
The Post Sockets cabal met at
IETF 100 in Singapore in November 2017 to resolve some of the open
issues with the API, and to participate in the TAPS working group.
I'm pleased to have co-authored two papers that were presented in the
IFIP Networking 2017 workshop on the Future of Internet Transport,
held on 12 June 2017 in Stockholm. The first was a paper outlining our
proposal for a Post Sockets API, building on our
IETF draft in this area, written with Brian Trammell and Mirja Kühlewind
of ETH Zürich. The second is with Tom Jones and Gorry Fairhurst from the
University of Aberdeen, and looks at raising the level of abstraction of the
datagram API to enable transport protocol evolution.
We've submitted an updated draft describing Post Sockets
(draft-trammell-taps-post-sockets-00) to the IETF.
The changes in this version reflect the outcome of the
meeting held at ETH Zürich in February.
I visited ETH Zürich on 13-14 February 2017, for a meeting to discuss
evolution of Internet transport protocols and their programming interfaces.
We considered what transport services existing protocols (e.g., TCP, UDP,
SCTP, HTTP, etc.) offer, what interface they expose to applications
programmers, and how the protocols and their API should change to support
future needs. The goal was to make the design of our Post Sockets interface
more concrete, taking input from the IETF TAPS working group, the EU H2020
NEAT project, and the experience of the workshop participants.
We've submitted an initial draft on
Post Sockets, An Abstract Programming Interface for the Transport Layer
to the IETF. This draft proposes an outline new API for the transport
layer that could form an eventual replacement for the Berkeley Sockets
API. It aims to support the features of modern transport- and
path-layer protocols, including long-lived security associations and
multipath operation.