TAPS: an abstract application interface for QUIC

Mirja Kuehlewind; Brian Trammell; Anna Brunstrom; Godred Fairhurst; Michael Welzl

TAPS: an abstract application interface for QUIC

Mirja Kuehlewind, Brian Trammell, Anna Brunstrom, Godred Fairhurst, Michael Welzl

Engineering

Research output: Contribution to conference › Poster › peer-review

Abstract

The TAPS Architecture for Transport Services provides a framework for the design of a protocol-independent asynchronous message-based transport API. While the traditional BSD socket API requires the user to make a choice about which protocol to use from the beginning, the TAPS API focuses on transport features and gives the transport stack itself the opportunity to select the most appropriate protocol. This flexibility also supports deployment of new protocols, such as QUIC, because the application does not need to change in order to benefit from such new innovations. This poster defines two API mappings for QUIC, either exposing multistreaming explicitly to the application or providing a way to utilize multistreaming without application input.

Original language	English
Publication status	Published - 4 Dec 2018
Event	CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC - Heraklion, Crete, Greece Duration: 4 Dec 2018 → 4 Dec 2018 https://conferences2.sigcomm.org/co-next/2018/#!/workshop-epiq

Conference

Conference	CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC
Abbreviated title	ACM COnEXT EPIQ
Country/Territory	Greece
City	Heraklion, Crete
Period	4/12/18 → 4/12/18
Internet address	https://conferences2.sigcomm.org/co-next/2018/#!/workshop-epiq

Keywords

API
TAPS

Access to Document

https://epiq18.hotcrp.com/doc/epiq18-paper3.pdfLicence: Other

Cite this

@conference{457b9afe58d04fc598ff48072bc5c14f,

title = "TAPS: an abstract application interface for QUIC",

abstract = "The TAPS Architecture for Transport Services provides a framework for the design of a protocol-independent asynchronous message-based transport API. While the traditional BSD socket API requires the user to make a choice about which protocol to use from the beginning, the TAPS API focuses on transport features and gives the transport stack itself the opportunity to select the most appropriate protocol. This flexibility also supports deployment of new protocols, such as QUIC, because the application does not need to change in order to benefit from such new innovations. This poster defines two API mappings for QUIC, either exposing multistreaming explicitly to the application or providing a way to utilize multistreaming without application input.",

keywords = "API, TAPS",

author = "Mirja Kuehlewind and Brian Trammell and Anna Brunstrom and Godred Fairhurst and Michael Welzl",

year = "2018",

month = dec,

day = "4",

language = "English",

note = "CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC , ACM COnEXT EPIQ ; Conference date: 04-12-2018 Through 04-12-2018",

url = "https://conferences2.sigcomm.org/co-next/2018/#!/workshop-epiq",

}

TY - CONF

T1 - TAPS: an abstract application interface for QUIC

AU - Kuehlewind, Mirja

AU - Trammell, Brian

AU - Brunstrom, Anna

AU - Fairhurst, Godred

AU - Welzl, Michael

PY - 2018/12/4

Y1 - 2018/12/4

N2 - The TAPS Architecture for Transport Services provides a framework for the design of a protocol-independent asynchronous message-based transport API. While the traditional BSD socket API requires the user to make a choice about which protocol to use from the beginning, the TAPS API focuses on transport features and gives the transport stack itself the opportunity to select the most appropriate protocol. This flexibility also supports deployment of new protocols, such as QUIC, because the application does not need to change in order to benefit from such new innovations. This poster defines two API mappings for QUIC, either exposing multistreaming explicitly to the application or providing a way to utilize multistreaming without application input.

AB - The TAPS Architecture for Transport Services provides a framework for the design of a protocol-independent asynchronous message-based transport API. While the traditional BSD socket API requires the user to make a choice about which protocol to use from the beginning, the TAPS API focuses on transport features and gives the transport stack itself the opportunity to select the most appropriate protocol. This flexibility also supports deployment of new protocols, such as QUIC, because the application does not need to change in order to benefit from such new innovations. This poster defines two API mappings for QUIC, either exposing multistreaming explicitly to the application or providing a way to utilize multistreaming without application input.

KW - API

KW - TAPS

UR - https://epiq18.hotcrp.com/paper/3?cap=03akrSuqR1a6WQ

M3 - Poster

T2 - CoNEXT Workshop on the Evolution, Performance, and Interoperability of QUIC

Y2 - 4 December 2018 through 4 December 2018

ER -

TAPS: an abstract application interface for QUIC

Abstract

Conference

Keywords

Access to Document

Other files and links

Fingerprint

Cite this