2017
DOI: 10.1109/mcom.2017.1601052
|View full text |Cite
|
Sign up to set email alerts
|

NEAT: A Platform- and Protocol-Independent Internet Transport API

Abstract: The sockets Applications Programming Interface (API) has become the standard way that applications access the transport services offered by the Internet Protocol stack. This paper presents NEAT, a user-space library that can provide an alternate transport API. NEAT allows applications to request the service they need using a new design that is agnostic to the specific choice of transport protocol underneath. This not only allows applications to take advantage of common protocol machinery, but also eases introd… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
20
0

Year Published

2017
2017
2022
2022

Publication Types

Select...
5
4

Relationship

3
6

Authors

Journals

citations
Cited by 28 publications
(20 citation statements)
references
References 7 publications
0
20
0
Order By: Relevance
“…Our ongoing work on coupled congestion control focuses on the practical deployments of our results; the WebRTC Internet draft [15] is close to publication as an RFC, and we are working on an FSE-SBD implementation in the Chromium browser. The FreeBSD implementation of the TCP coupling is used by the NEAT European research project [29].…”
Section: Discussionmentioning
confidence: 99%
“…Our ongoing work on coupled congestion control focuses on the practical deployments of our results; the WebRTC Internet draft [15] is close to publication as an RFC, and we are working on an FSE-SBD implementation in the Chromium browser. The FreeBSD implementation of the TCP coupling is used by the NEAT European research project [29].…”
Section: Discussionmentioning
confidence: 99%
“…More recent works [12,13,2] propose to rethink the entire Transport layer architecture in order to delegate to the Transport layer the choice of the protocol to be used; let us recall that this choice is currently let to the application developer. In [2], the authors assert that the main cause explaining the lack of new Transport protocols deployment and adoption comes from architectural limitations of the Transport layer, hence their proposal for a new architecture.…”
Section: B Related Workmentioning
confidence: 99%
“…The NEAT transport architecture [5] and accompanying software stack [6] is designed to offer a flexible and evolvable transport system. Applications interface the NEAT System through an enhanced API that effectively decouples them from the operation of the transport protocols and the network features being used.…”
Section: End-host Sdn Integration With Neatmentioning
confidence: 99%
“…Building on previous successes, in this demo we introduce a generic, overarching framework for end-host SDN integration, integrated into the NEAT transport architecture [5]. Our framework provides structured interfaces for communication between applications and external controllers.…”
Section: Introductionmentioning
confidence: 99%