NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet

Karl-Johan Grinnemo, Anna Brunstrom, Tom Harvey Jones, Godred Fairhurst, Per Hurtig, David Ros

Research output: Contribution to conferencePoster

Abstract

There is a growing concern that the Internet transport layer has stagnated and become less adaptive to the requirements imposed by new applications, and that further evolution has become very difficult. This is because a fundamental assumption no longer holds: it can no longer be assumed that the transport layer is only in the scope of end-hosts. The success of TCP and UDP and the ubiquity of middleboxes have led to ossification of both the network infrastructure and the API presented to applications. This has led to the development of workarounds, and a range of point solutions that fail to cover many facets of the problem. To address this issue, this paper identifies requirements for a new transport layer and then proposes a conceptual architecture that we argue is both flexible and evolvable. This new architecture requires that applications interface to the transport at a higher abstraction level, where an application can express communication preferences via a new richer API. Protocol machinery can use this information to decide which of the available transport protocols is used. By placing the protocol machinery in the transport layer, the new architecture can allow for new protocols to be deployed and enable evolution of the transport layer.
Original languageEnglish
Publication statusPublished - 1 Jun 2016
Event12th Swedish National Computer Networking Workshop - Sundsvall, Sweden
Duration: 1 Jun 20162 Jun 2016

Workshop

Workshop12th Swedish National Computer Networking Workshop
Abbreviated title(SNCNW 2016)
CountrySweden
CitySundsvall
Period1/06/162/06/16

Fingerprint

Application programming interfaces (API)
Internet
Network protocols
Machinery
Information use
Communication

Cite this

Grinnemo, K-J., Brunstrom, A., Jones, T. H., Fairhurst, G., Hurtig, P., & Ros, D. (2016). NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet. Poster session presented at 12th Swedish National Computer Networking Workshop, Sundsvall, Sweden.

NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet. / Grinnemo, Karl-Johan; Brunstrom, Anna; Jones, Tom Harvey; Fairhurst, Godred; Hurtig, Per; Ros, David.

2016. Poster session presented at 12th Swedish National Computer Networking Workshop, Sundsvall, Sweden.

Research output: Contribution to conferencePoster

Grinnemo, K-J, Brunstrom, A, Jones, TH, Fairhurst, G, Hurtig, P & Ros, D 2016, 'NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet' 12th Swedish National Computer Networking Workshop, Sundsvall, Sweden, 1/06/16 - 2/06/16, .
Grinnemo K-J, Brunstrom A, Jones TH, Fairhurst G, Hurtig P, Ros D. NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet. 2016. Poster session presented at 12th Swedish National Computer Networking Workshop, Sundsvall, Sweden.
Grinnemo, Karl-Johan ; Brunstrom, Anna ; Jones, Tom Harvey ; Fairhurst, Godred ; Hurtig, Per ; Ros, David. / NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet. Poster session presented at 12th Swedish National Computer Networking Workshop, Sundsvall, Sweden.
@conference{d053046538814c2bb4a292de5da94948,
title = "NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet",
abstract = "There is a growing concern that the Internet transport layer has stagnated and become less adaptive to the requirements imposed by new applications, and that further evolution has become very difficult. This is because a fundamental assumption no longer holds: it can no longer be assumed that the transport layer is only in the scope of end-hosts. The success of TCP and UDP and the ubiquity of middleboxes have led to ossification of both the network infrastructure and the API presented to applications. This has led to the development of workarounds, and a range of point solutions that fail to cover many facets of the problem. To address this issue, this paper identifies requirements for a new transport layer and then proposes a conceptual architecture that we argue is both flexible and evolvable. This new architecture requires that applications interface to the transport at a higher abstraction level, where an application can express communication preferences via a new richer API. Protocol machinery can use this information to decide which of the available transport protocols is used. By placing the protocol machinery in the transport layer, the new architecture can allow for new protocols to be deployed and enable evolution of the transport layer.",
author = "Karl-Johan Grinnemo and Anna Brunstrom and Jones, {Tom Harvey} and Godred Fairhurst and Per Hurtig and David Ros",
note = "ACKNOWLEDGMENTS 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. ; 12th Swedish National Computer Networking Workshop, (SNCNW 2016) ; Conference date: 01-06-2016 Through 02-06-2016",
year = "2016",
month = "6",
day = "1",
language = "English",

}

TY - CONF

T1 - NEAT - A New, Evolutive API and Transport-Layer Architecture for the Internet

AU - Grinnemo, Karl-Johan

AU - Brunstrom, Anna

AU - Jones, Tom Harvey

AU - Fairhurst, Godred

AU - Hurtig, Per

AU - Ros, David

N1 - ACKNOWLEDGMENTS 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 - 2016/6/1

Y1 - 2016/6/1

N2 - There is a growing concern that the Internet transport layer has stagnated and become less adaptive to the requirements imposed by new applications, and that further evolution has become very difficult. This is because a fundamental assumption no longer holds: it can no longer be assumed that the transport layer is only in the scope of end-hosts. The success of TCP and UDP and the ubiquity of middleboxes have led to ossification of both the network infrastructure and the API presented to applications. This has led to the development of workarounds, and a range of point solutions that fail to cover many facets of the problem. To address this issue, this paper identifies requirements for a new transport layer and then proposes a conceptual architecture that we argue is both flexible and evolvable. This new architecture requires that applications interface to the transport at a higher abstraction level, where an application can express communication preferences via a new richer API. Protocol machinery can use this information to decide which of the available transport protocols is used. By placing the protocol machinery in the transport layer, the new architecture can allow for new protocols to be deployed and enable evolution of the transport layer.

AB - There is a growing concern that the Internet transport layer has stagnated and become less adaptive to the requirements imposed by new applications, and that further evolution has become very difficult. This is because a fundamental assumption no longer holds: it can no longer be assumed that the transport layer is only in the scope of end-hosts. The success of TCP and UDP and the ubiquity of middleboxes have led to ossification of both the network infrastructure and the API presented to applications. This has led to the development of workarounds, and a range of point solutions that fail to cover many facets of the problem. To address this issue, this paper identifies requirements for a new transport layer and then proposes a conceptual architecture that we argue is both flexible and evolvable. This new architecture requires that applications interface to the transport at a higher abstraction level, where an application can express communication preferences via a new richer API. Protocol machinery can use this information to decide which of the available transport protocols is used. By placing the protocol machinery in the transport layer, the new architecture can allow for new protocols to be deployed and enable evolution of the transport layer.

M3 - Poster

ER -