@article {25372,
	title = {NEAT: A Platform- and Protocol-Independent Internet Transport API},
	journal = {IEEE Communications Magazine},
	volume = {55},
	year = {2017},
	month = {06/2017},
	pages = {46-54},
	publisher = {IEEE},
	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 introduction of new network mechanisms and transport protocols. The paper describes the components of the NEAT library and illustrates the important benefits that can be gained from this new approach. NEAT is a software platform for developing advanced network applications that was designed in accordance with the standardization efforts on Transport Services (TAPS) in the Internet Engineering Task Force (IETF), but its features exceed the envisioned functionality of a TAPS system.},
	issn = {0163-6804},
	doi = {https://doi.org/10.1109/MCOM.2017.1601052},
	author = {Khademi, Naeem and Ros, David and Welzl, Michael and Bozakov, Zdravko and Brunstr{\"o}m, Anna and Fairhurst, Gorry and Grinnemo, Karl-Johan and David Andrew {Hayes} and Hurtig, Per and Jones, Tom and Mangiante, Simone and T{\"u}xen, Michael and Weinrank, Felix}
}
@inproceedings { ANRW2017,
	title = {A NEAT Way to Browse the Web},
	journal = {Proceedings of the Applied Networking Research Workshop~(ANRW)},
	year = {2017},
	note = {Demo Presentation},
	month = {07/15/2017},
	publisher = {IEEE},
	address = {Praha/Czech Republic},
	abstract = {There is a growing concern that the Internet transport layer has become ossified in the face of emerging novel applications, and that further evolution has become very difficult. The NEAT system is a novel and evolvable transport system that decouples applications from the underlying transport layer and network services. In so doing, it facilitates dynamic transport selection. This demo shows how the NEAT system is able to dynamically select the most appropriate transport solution for the Mozilla Firefox web browser.},
	keywords = {NEAT, ossification, SCTP, tcp, Transport Selection, Transport Service},
	url = {https://irtf.org/anrw/2017/anrw17-final13.pdf},
	author = {Weinrank, Felix and Grinnemo, Karl-Johan and Bozakov, Zdravko and Brunstr{\"o}m, Anna and Dreibholz, Thomas and Hurtig, Per and Khademi, Naeem},
	editor = {T{\"u}xen, Michael}
}
@inproceedings {24988,
	title = {On the Cost of Using Happy Eyeballs for Transport Protocol Selection},
	journal = {Applied Networking Research Workshop (ANRW)},
	year = {2016},
	month = {07/2016},
	pages = {45-51},
	publisher = {ACM},
	abstract = {Concerns have been raised in the past several years that introducing new transport protocols on the Internet has become increasingly difficult, not least because there is no agreed-upon way for a source end host to find out if a transport protocol is supported all the way to a destination peer. A solution to a similar problem\&mdash;finding out support for IPv6\&mdash;has been proposed and is currently being deployed: the Happy Eyeballs (HE) mechanism. HE has also been proposed as an efficient way for an application to select an appropriate transport protocol. Still, there are few, if any, performance evaluations of transport HE. This paper demonstrates that transport HE could indeed be a feasible solution to the transport support problem. The paper evaluates HE between TCP and SCTP using TLS encrypted and unencrypted traffic, and shows that although there is indeed a cost in terms of CPU load to introduce HE, the cost is relatively small, especially in comparison with the cost of using TLS encryption. Moreover, our results suggest that HE has a marginal impact on memory usage. Finally, by introducing caching of previous connection attempts, the additional cost of transport HE could be significantly reduced.},
	keywords = {CPU load, Happy Eyeballs, memory usage, SCTP, tcp, TLS, Transport-protocol selection},
	isbn = {978-1-4503-4443-2},
	doi = {https://doi.org/10.1145/2959424.2959437},
	url = {https://irtf.org/anrw/2016/anrw16-final27.pdf},
	author = {Papastergiou, Georgios and Grinnemo, Karl-Johan and Brunstr{\"o}m, Anna and Ros, David and T{\"u}xen, Michael and Khademi, Naeem and Hurtig, Per}
}
@article {24989,
	title = {De-ossifying the Internet transport layer: A survey and future perspectives},
	journal = {IEEE Communications Surveys and Tutorials},
	year = {2016},
	month = {11/2016},
	publisher = {IEEE},
	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.},
	keywords = {API, middleboxes, protocol-stack ossification, transport protocols, user-space networking stacks},
	issn = {1553-877X},
	doi = {https://doi.org/10.1109/COMST.2016.2626780},
	author = {Papastergiou, Georgios and Fairhurst, Gorry and Ros, David and Brunstr{\"o}m, Anna and Grinnemo, Karl-Johan and Hurtig, Per and Khademi, Naeem and T{\"u}xen, Michael and Welzl, Michael and Damjanovic, Dragana and Mangiante, Simone}
}
