NEAT

A Platform- And Protocol-Independent Internet Transport API

Naeem Khademi, David Ros, Michael Welzl, Zdravko Bozakov, Anna Brunstrom, Gorry Fairhurst, Karl-Johan Grinnemo, David Hayes, Per Hurtig, Tom Jones, Simone Mangiante, Michael Tüxen, Felix Weinrank

Research output: Contribution to journalArticle

12 Citations (Scopus)
11 Downloads (Pure)

Abstract

For more than three decades, the Internet’s transport layer has essentially supported just two protocols: TCP, for applications that need reliable in-sequence delivery; UDP, for applications that assume nothing but port numbers and a checksum. Applications have been built using these protocols, and other transport protocols have even been layered over these. UDP has become a substrate upon which user-space transport protocols are being developed—with most of these customized for specific applications, as with the recent QUIC protocol from Google. In these cases, much effort is expended re-implementing many common transport functions. This paper proposes an alternative approach to realize a new transport API that allows applications to request the service they need, but is agnostic to the specific choice of transport protocol underneath. This not only allows applications to take advantages of common protocol machinery, it also eases introduction of new network mechanisms and transport protocols. We present NEAT, a user-space library that achieves this goal, and then illustrate important benefits that can be gained from this approach. NEAT was designed in accordance with the standardization efforts on Transport Services (TAPS) in the Internet Engineering Task Force (IETF), but its features exceed the envisioned functionality of a TAPS system.
Original languageEnglish
Pages (from-to)46-54
Number of pages9
JournalIEEE Communications Magazine
Volume55
Issue number6
DOIs
Publication statusPublished - 12 Jun 2017

Fingerprint

Application programming interfaces (API)
Internet
Network protocols
Standardization
Machinery
Substrates

Cite this

Khademi, N., Ros, D., Welzl, M., Bozakov, Z., Brunstrom, A., Fairhurst, G., ... Weinrank, F. (2017). NEAT: A Platform- And Protocol-Independent Internet Transport API. IEEE Communications Magazine, 55(6), 46-54. https://doi.org/10.1109/MCOM.2017.1601052

NEAT : A Platform- And Protocol-Independent Internet Transport API. / Khademi, Naeem; Ros, David; Welzl, Michael; Bozakov, Zdravko; Brunstrom, Anna; Fairhurst, Gorry; Grinnemo, Karl-Johan ; Hayes, David; Hurtig, Per; Jones, Tom ; Mangiante, Simone; Tüxen, Michael; Weinrank, Felix .

In: IEEE Communications Magazine, Vol. 55, No. 6, 12.06.2017, p. 46-54.

Research output: Contribution to journalArticle

Khademi, N, Ros, D, Welzl, M, Bozakov, Z, Brunstrom, A, Fairhurst, G, Grinnemo, K-J, Hayes, D, Hurtig, P, Jones, T, Mangiante, S, Tüxen, M & Weinrank, F 2017, 'NEAT: A Platform- And Protocol-Independent Internet Transport API', IEEE Communications Magazine, vol. 55, no. 6, pp. 46-54. https://doi.org/10.1109/MCOM.2017.1601052
Khademi, Naeem ; Ros, David ; Welzl, Michael ; Bozakov, Zdravko ; Brunstrom, Anna ; Fairhurst, Gorry ; Grinnemo, Karl-Johan ; Hayes, David ; Hurtig, Per ; Jones, Tom ; Mangiante, Simone ; Tüxen, Michael ; Weinrank, Felix . / NEAT : A Platform- And Protocol-Independent Internet Transport API. In: IEEE Communications Magazine. 2017 ; Vol. 55, No. 6. pp. 46-54.
@article{8e2fa56ce66b454ead6f915ac84fbdfd,
title = "NEAT: A Platform- And Protocol-Independent Internet Transport API",
abstract = "For more than three decades, the Internet’s transport layer has essentially supported just two protocols: TCP, for applications that need reliable in-sequence delivery; UDP, for applications that assume nothing but port numbers and a checksum. Applications have been built using these protocols, and other transport protocols have even been layered over these. UDP has become a substrate upon which user-space transport protocols are being developed—with most of these customized for specific applications, as with the recent QUIC protocol from Google. In these cases, much effort is expended re-implementing many common transport functions. This paper proposes an alternative approach to realize a new transport API that allows applications to request the service they need, but is agnostic to the specific choice of transport protocol underneath. This not only allows applications to take advantages of common protocol machinery, it also eases introduction of new network mechanisms and transport protocols. We present NEAT, a user-space library that achieves this goal, and then illustrate important benefits that can be gained from this approach. NEAT was designed in accordance with the standardization efforts on Transport Services (TAPS) in the Internet Engineering Task Force (IETF), but its features exceed the envisioned functionality of a TAPS system.",
author = "Naeem Khademi and David Ros and Michael Welzl and Zdravko Bozakov and Anna Brunstrom and Gorry Fairhurst and Karl-Johan Grinnemo and David Hayes and Per Hurtig and Tom Jones and Simone Mangiante and Michael T{\"u}xen and Felix Weinrank",
note = "ACKNOWLEDGMENT The authors would like to thank the anonymous reviewers for their useful remarks. This work has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 644334 (NEAT). The views expressed are solely those of the authors.",
year = "2017",
month = "6",
day = "12",
doi = "10.1109/MCOM.2017.1601052",
language = "English",
volume = "55",
pages = "46--54",
journal = "IEEE Communications Magazine",
publisher = "IEEE Explore",
number = "6",

}

TY - JOUR

T1 - NEAT

T2 - A Platform- And Protocol-Independent Internet Transport API

AU - Khademi, Naeem

AU - Ros, David

AU - Welzl, Michael

AU - Bozakov, Zdravko

AU - Brunstrom, Anna

AU - Fairhurst, Gorry

AU - Grinnemo, Karl-Johan

AU - Hayes, David

AU - Hurtig, Per

AU - Jones, Tom

AU - Mangiante, Simone

AU - Tüxen, Michael

AU - Weinrank, Felix

N1 - ACKNOWLEDGMENT The authors would like to thank the anonymous reviewers for their useful remarks. This work has received funding from the European Union's Horizon 2020 research and innovation programme under grant agreement No. 644334 (NEAT). The views expressed are solely those of the authors.

PY - 2017/6/12

Y1 - 2017/6/12

N2 - For more than three decades, the Internet’s transport layer has essentially supported just two protocols: TCP, for applications that need reliable in-sequence delivery; UDP, for applications that assume nothing but port numbers and a checksum. Applications have been built using these protocols, and other transport protocols have even been layered over these. UDP has become a substrate upon which user-space transport protocols are being developed—with most of these customized for specific applications, as with the recent QUIC protocol from Google. In these cases, much effort is expended re-implementing many common transport functions. This paper proposes an alternative approach to realize a new transport API that allows applications to request the service they need, but is agnostic to the specific choice of transport protocol underneath. This not only allows applications to take advantages of common protocol machinery, it also eases introduction of new network mechanisms and transport protocols. We present NEAT, a user-space library that achieves this goal, and then illustrate important benefits that can be gained from this approach. NEAT was designed in accordance with the standardization efforts on Transport Services (TAPS) in the Internet Engineering Task Force (IETF), but its features exceed the envisioned functionality of a TAPS system.

AB - For more than three decades, the Internet’s transport layer has essentially supported just two protocols: TCP, for applications that need reliable in-sequence delivery; UDP, for applications that assume nothing but port numbers and a checksum. Applications have been built using these protocols, and other transport protocols have even been layered over these. UDP has become a substrate upon which user-space transport protocols are being developed—with most of these customized for specific applications, as with the recent QUIC protocol from Google. In these cases, much effort is expended re-implementing many common transport functions. This paper proposes an alternative approach to realize a new transport API that allows applications to request the service they need, but is agnostic to the specific choice of transport protocol underneath. This not only allows applications to take advantages of common protocol machinery, it also eases introduction of new network mechanisms and transport protocols. We present NEAT, a user-space library that achieves this goal, and then illustrate important benefits that can be gained from this approach. NEAT was designed in accordance with the standardization efforts on Transport Services (TAPS) in the Internet Engineering Task Force (IETF), but its features exceed the envisioned functionality of a TAPS system.

U2 - 10.1109/MCOM.2017.1601052

DO - 10.1109/MCOM.2017.1601052

M3 - Article

VL - 55

SP - 46

EP - 54

JO - IEEE Communications Magazine

JF - IEEE Communications Magazine

IS - 6

ER -