2019
DOI: 10.48550/arxiv.1901.01863
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Beyond socket options: making the Linux TCP stack truly extensible

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1

Citation Types

0
1
0

Year Published

2019
2019
2019
2019

Publication Types

Select...
1

Relationship

0
1

Authors

Journals

citations
Cited by 1 publication
(1 citation statement)
references
References 0 publications
0
1
0
Order By: Relevance
“…For example, in QUIC and SCTP it is possible to disable reliable transmissions for certain streams, and QUIC and DCCP have mechanisms for feature and parameter negotiation during the connection handshake. This reconfigurability should be however matched by a proper evolution of the APIs to the application layer, so that developers can benefit from it [107]. Explicit QoS signaling represents a step further in this direction: in order to fully support new applications and services, endpoints will need to be able to specify their QoS requirements [108], as will QoS-aware schemes exploiting tools such as SDN [109].…”
Section: Open Challenges and Research Directionsmentioning
confidence: 99%
“…For example, in QUIC and SCTP it is possible to disable reliable transmissions for certain streams, and QUIC and DCCP have mechanisms for feature and parameter negotiation during the connection handshake. This reconfigurability should be however matched by a proper evolution of the APIs to the application layer, so that developers can benefit from it [107]. Explicit QoS signaling represents a step further in this direction: in order to fully support new applications and services, endpoints will need to be able to specify their QoS requirements [108], as will QoS-aware schemes exploiting tools such as SDN [109].…”
Section: Open Challenges and Research Directionsmentioning
confidence: 99%