Tom Jones ([tj])

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.

Quality of Service markings can benefit real time traffic. A survey we conducted on a mobile cellular testbed (Monroe) has revealed how differentiated services traffic is treated in practical networks, and shows many networks do not respect diffserv markings resulting unpredictable real-time performance.

This motivates a change to the network programming API for real-time traffic to provide dynamic transport selection and fallback, enabling successful use of network QoS. The API is presented in the context of the NEAT1 open source project.