Transport Evolution on top of the BSD's: A New, Evolutive API and Transport-Layer Architecture for the Internet

Research output: Contribution to conferenceOther

2 Downloads (Pure)

Abstract

Internet Transport is changing, some changes have been incremental updates to mechanisms (e.g., RACK, BBR), others demand new protocol options (e.g., MPTCP) or entirely new protocols (e.g., QUIC, SCTP). However significant changes are still difficult to deploy - requiring modifications to application code and support by the stack. Even when updates happen, the network needs to support the new method to allow applications to use it. Long deployment times have motivated the need to change how protocols are handled in the stack. We review the state of the art in Internet Transport, and the status of deployment in th BSD's and then propose a new direction for the transport interface, developed in the EU NEAT Project, that can ease deployment of new transports across all platforms. We conclude by showing the advantages and its prospects for standards adoption.
Original languageEnglish
Publication statusPublished - 4 Feb 2017
EventFOSDEM 2017 - ULB, Brussels, Belgium
Duration: 4 Feb 20175 Feb 2017
https://fosdem.org

Conference

ConferenceFOSDEM 2017
CountryBelgium
CityBrussels
Period4/02/175/02/17
Internet address

Fingerprint

Application programming interfaces (API)
Internet
Network protocols

Cite this

Transport Evolution on top of the BSD's : A New, Evolutive API and Transport-Layer Architecture for the Internet. / Jones, Tom Harvey.

2017. FOSDEM 2017, Brussels, Belgium.

Research output: Contribution to conferenceOther

@conference{15989ccb6ac3453b9de9717d21ff72d0,
title = "Transport Evolution on top of the BSD's: A New, Evolutive API and Transport-Layer Architecture for the Internet",
abstract = "Internet Transport is changing, some changes have been incremental updates to mechanisms (e.g., RACK, BBR), others demand new protocol options (e.g., MPTCP) or entirely new protocols (e.g., QUIC, SCTP). However significant changes are still difficult to deploy - requiring modifications to application code and support by the stack. Even when updates happen, the network needs to support the new method to allow applications to use it. Long deployment times have motivated the need to change how protocols are handled in the stack. We review the state of the art in Internet Transport, and the status of deployment in th BSD's and then propose a new direction for the transport interface, developed in the EU NEAT Project, that can ease deployment of new transports across all platforms. We conclude by showing the advantages and its prospects for standards adoption.",
author = "Jones, {Tom Harvey}",
year = "2017",
month = "2",
day = "4",
language = "English",
note = "FOSDEM 2017 ; Conference date: 04-02-2017 Through 05-02-2017",
url = "https://fosdem.org",

}

TY - CONF

T1 - Transport Evolution on top of the BSD's

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

AU - Jones, Tom Harvey

PY - 2017/2/4

Y1 - 2017/2/4

N2 - Internet Transport is changing, some changes have been incremental updates to mechanisms (e.g., RACK, BBR), others demand new protocol options (e.g., MPTCP) or entirely new protocols (e.g., QUIC, SCTP). However significant changes are still difficult to deploy - requiring modifications to application code and support by the stack. Even when updates happen, the network needs to support the new method to allow applications to use it. Long deployment times have motivated the need to change how protocols are handled in the stack. We review the state of the art in Internet Transport, and the status of deployment in th BSD's and then propose a new direction for the transport interface, developed in the EU NEAT Project, that can ease deployment of new transports across all platforms. We conclude by showing the advantages and its prospects for standards adoption.

AB - Internet Transport is changing, some changes have been incremental updates to mechanisms (e.g., RACK, BBR), others demand new protocol options (e.g., MPTCP) or entirely new protocols (e.g., QUIC, SCTP). However significant changes are still difficult to deploy - requiring modifications to application code and support by the stack. Even when updates happen, the network needs to support the new method to allow applications to use it. Long deployment times have motivated the need to change how protocols are handled in the stack. We review the state of the art in Internet Transport, and the status of deployment in th BSD's and then propose a new direction for the transport interface, developed in the EU NEAT Project, that can ease deployment of new transports across all platforms. We conclude by showing the advantages and its prospects for standards adoption.

M3 - Other

ER -