| 1. |
- Grinnemo, Karl-Johan, 1968-, et al.
(författare)
-
Deliverable D3.1 - Initial Report on the Extended Transport System
- 2017
-
Rapport (refereegranskat)abstract
- The NEAT System offers an enhanced API for applications that disentangles them from the actual transport protocol being used. The system also enables applications to communicate their service requirements to the transport system in a generic, transport-protocol independent way. Moreover, the architecture of the NEAT System promotes the evolution of new transport services. Work Package 3 (WP3) enhances and extends the core parts of the NEAT Transport. Efforts have been devoted to developing transport-protocol mechanisms that enable a wider spectrum of NEAT Transport Services, and that assist the NEAT System in facilitating several of the commercial use cases. Work has also started on the development of optimal transport-selection mechanisms; mechanisms that enable for the NEAT System to make optimal transport selections on the basis of application requirements and network measurements. Lastly, another research activity has been initiated on how to use SDN to signal application requirements to routers, switches, and similar network elements. This document provides an initial report on all these WP3 activities—both on completed and on near-termplanned work.
|
|
| 2. |
- Grinnemo, Karl-Johan, 1968-, et al.
(författare)
-
Deliverable D3.2 - Final Report on Transport Protocol Enhancements
- 2017
-
Rapport (refereegranskat)abstract
- This deliverable provides a final report on the work on transport protocol enhancements done inWork Package 3. First, we report on the extensions made to the SCTP protocol that turn it into a viable alternative to TCP and allow to deliver a lower-latency transport service. Next, we describe our work to develop a framework for providing a deadline-aware, less-than-best-effort transport service, targeting background traffic and thus addressing requirements on NEAT from the EMC use case. We also present our efforts to design and implement a latency-aware scheduler for MPTCP, which enables NEAT to offer a transport service that meets the needs of latency-sensitive applications, and that efficiently utilises available network resources. Lastly, this document informs on our work on coupled congestion control for TCP, a mechanism that treats a bundle of parallel TCP flows between the same pair of hosts as a single unit. By efficiently multiplexing concurrent TCP flows, our coupled congestion control alleviates the effects of queueing, and tends to result in a more efficient usage of available bandwidth, where the flows’ aggregate capacity share can be apportioned based on application preferences.
|
|
| 3. |
- Grinnemo, Karl-Johan, 1968-, et al.
(författare)
-
Deliverable D3.3 - Extended Transport System and Transparent Support of Non-NEAT Applications
- 2017
-
Rapport (refereegranskat)abstract
- This deliverable summarises and concludes our work in Work Package 3 (WP3) to extend the transport services provided by the NEAT System developed in Work Package 2, and to enable non-NEAT applications to harness the transport services offered by NEAT. We have demonstrated how a policy- and information-based selection of transport protocol by NEAT could provide a more efficient transport service for web applications. The information on which NEAT makes its transport selection decisions resides in the Characteristics Information Base (CIB). The CIB is populated by various CIB sources, and in WP3 we have designed, implemented, and evaluated various CIB sources, including meta data from mobile broadband networks, passive measurements, IPv6 Provisioning Domain protocols and the Happy Eyeballs mechanism, which caches the outcome of its connection attempts. A key property of NEAT is that it not only “vertically” decouples applications from transport protocols, but also “horizontally”. Particularly, it enables applications to harness information about resource availability and policies from Software Defined Networking (SDN) controllers in managed networks, without these applications actually being SDN-aware. To extend the use of NEAT to non-NEAT applications, we have implemented a BSDcompatible sockets API on top of NEAT and a NEAT proxy that intercepts and replaces standard TCP connections with NEAT flows, i.e., with the transport solutions deemed most appropriate by NEAT.We have also proposed a way for non-NEAT applications to make use of NEAT through the deployment of NEAT-enabled virtual appliances in SDN-controlled networks: connections from these applications are routed via an SDN-controlled proxy that terminates the original connection and replaces it with a NEAT-selected connection.
|
|
| 4. |
- Khademi, Naeem, et al.
(författare)
-
Deliverable D2.2 - Core Transport System, with both Low-level and High-level Components
- 2017
-
Rapport (refereegranskat)abstract
- This document presents the core transport system in NEAT, as used for development of thereference implementation of the NEAT System. The document describes the componentsnecessary to realise the basic Transport Services provided by the NEAT User API, with thedescription of a set of NEAT building blocks and their related design choices. The designof this core transport system takes into consideration the Transport Services and the API(defined in Task 1.3) and in close coordination with the overall architecture (Task 1.2).To realise the Transport Services provided by the API, a set of transport functionalitieshas to be provided by the NEAT Core Transport System. These functionalities take the formof several building blocks, or NEAT Components, each representing an associated implementationactivity. Some of the components are needed to ensure the basic operation ofthe NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, theNEAT Logic and the functionality to Connect to a name. Additional components are neededfor: (a) ensuring connectivity, by means of mechanisms for discovery of path support fordifferent protocols; (b) supporting end-to-end security; (c) the ability to apply differentpolicies to influence the decision-making process of the transport system; (d) providingother important functionalities (e.g., a user-space SCTP stack, or gathering statistics forusers or system administrators).This document updates Deliverable D2.1; in particular, the descriptions of NEAT componentspresented here correspond to the implementation status at the time of writing,and as such they replace those in D2.1.
|
|
| 5. |
- Khademi, Naeem, et al.
(författare)
-
Deliverable D2.3 - Final Version of Core Transport System
- 2017
-
Rapport (refereegranskat)abstract
- This document presents the core transport system in NEAT, as used for development of the reference implementation of the NEAT System. The document describes the components necessary to realise the basic Transport Services provided by the NEAT User API, with the description of a set of NEAT building blocks and their related design choices. The design of this core transport system, which is the final product ofWork Package 2, is driven by the Transport Services and API design from Task 1.4, and in close coordination with the overall NEAT architecture defined in Task 1.2. To realise the Transport Services provided by the API, a set of transport functions has to be provided by the NEAT Core Transport System. These functions take the form of several building blocks, or NEAT Components, each representing an associated implementation activity. Some components are needed to ensure the basic operation of the NEAT System—e.g., a NEAT Flow Endpoint, a callback-based NEAT API Framework, the NEAT Logic and the functionality to Connect to a name. Additional components are needed for: (a) ensuring connectivity, by means of mechanisms for discovery of path support for different protocols; (b) supporting end-to-end security; (c) the ability to apply different policies to influence the decision-making process of the transport system; (d) providing other important functionalities (e.g., a user-space SCTP stack, or gathering statistics for users or system administrators). This document updates Deliverable D2.2; in particular, the descriptions of NEAT components presented here correspond to their implementation status by the end of WP2, and as such they supersede those in D2.2.
|
|
| 6. |
- Khademi, Naeem, et al.
(författare)
-
NEAT: A Platform- and Protocol-Independent Internet Transport API
- 2017
-
Ingår i: IEEE Communications Magazine. - : IEEE Communications Society. - 0163-6804 .- 1558-1896. ; 55:6, s. 46-54
-
Tidskriftsartikel (refereegranskat)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.
|
|
| 7. |
- Papastergiou, Giorgos, et al.
(författare)
-
De-Ossifying the Internet Transport Layer: A Survey and Future Perspectives
- 2017
-
Ingår i: IEEE Communications Surveys and Tutorials. - : IEEE. - 1553-877X. ; 19:1, s. 619-639
-
Tidskriftsartikel (refereegranskat)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 paper, 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 middlebox-proof 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 toward 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
|
|
| 8. |
- Rajiullah, Mohammad, 1981-, et al.
(författare)
-
Understanding Multistreaming for Web Traffic : An Experimental Study
- 2017
-
Ingår i: 16th International IFIP TC6 Networking Conference, Networking 2017. - : IEEE. - 9783901882944
-
Konferensbidrag (refereegranskat)abstract
- This paper explores the design trade-offs needed for an Internet transport protocol to effectively support web access over HTTP/1.1. It explores use of a multistreaming transport protocol mechanism and studies these using a practical methodology utilising the transport features of TCP and SCTP. This is used to evaluate the relative benefit of key transport mechanisms and analyse how these impact web access performance. Our conclusions help identify the root causes of performance impairments and suggest appropriate choices when selecting a suitable transport protocol.
|
|
| 9. |
- Weinrank, Felix, et al.
(författare)
-
A NEAT Way to Browse the Web
- 2017
-
Ingår i: Applied Networking Research Workshop (ANRW) 2017, Prague, Czech Republic, July 15, 2017.. - New York, NY, USA : Thomas Dreibholz.
-
Konferensbidrag (refereegranskat)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.
|
|
