@article{14309, keywords = {transport protocols, middleboxes, protocol-stack ossification, API, user-space networking stacks}, author = {Georgios Papastergiou and Gorry Fairhurst and David Ros and Anna Brunstr{\"o}m and Karl-Johan Grinnemo and Per Hurtig and Naeem Khademi and Michael T{\"u}xen and Michael Welzl and Dragana Damjanovic and Simone Mangiante}, title = {De-ossifying the Internet transport layer: A survey and future perspectives}, abstract = {It is widely recognized that the Internet transport layer has become ossified, where further evolution has become hard or even impossible. This is a direct consequence of the ubiquitous deployment of middleboxes that hamper the deployment of new transports, aggravated further by the limited flexibility of the Application Programming Interface (API) typically presented to applications. To tackle this problem, a wide range of solutions have been proposed in the literature, each aiming to address a particular aspect. Yet, no single proposal has emerged that is able to enable evolution of the transport layer. In this work, after an overview of the main issues and reasons for transport-layer ossification, we survey proposed solutions and discuss their potential and limitations. The survey is divided into five parts, each covering a set of point solutions for a different facet of the problem space: 1) designing middleboxproof transports, 2) signaling for facilitating middlebox traversal, 3) enhancing the API between the applications and the transport layer, 4) discovering and exploiting end-to-end capabilities, and 5) enabling user-space protocol stacks. Based on this analysis, we then identify further development needs towards an overall solution. We argue that the development of a comprehensive transport layer framework, able to facilitate the integration and cooperation of specialized solutions in an application-independent and flexible way, is a necessary step toward making the Internet transport architecture truly evolvable. To this end, we identify the requirements for such a framework and provide insights for its development.}, year = {2016}, journal = {IEEE Communications Surveys and Tutorials}, month = {11/2016}, publisher = {IEEE}, issn = {1553-877X}, doi = {https://doi.org/10.1109/COMST.2016.2626780}, }