%% You should probably cite draft-jones-tsvwg-transport-for-satellite-02 instead of this revision. @techreport{jones-tsvwg-transport-for-satellite-01, number = {draft-jones-tsvwg-transport-for-satellite-01}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-jones-tsvwg-transport-for-satellite/01/}, author = {Tom Jones and Gorry Fairhurst and Nicolas Kuhn and John Border and Stephan Emile}, title = {{Enhancing Transport Protocols over Satellite Networks}}, pagetotal = 28, year = 2021, month = oct, day = 13, abstract = {IETF transport protocols such as TCP, SCTP and QUIC are designed to function correctly over any network path. This includes networks paths that utilise a satellite link or network. While transport protocols function, the characteristics of satellite networks can impact performance when using the defaults in standard mechanisms, due to the specific characteristics of these paths. {[}RFC2488{]} and {[}RFC3135{]} describe mechanisms that enable TCP to more effectively utilize the available capacity of a network path that includes a satellite system. Since publication, both application and transport layers and satellite systems have evolved. Indeed, the development of encrypted protocols such as QUIC challenges currently deployed solutions, for satellite systems the capacity has increased and commercial systems are now available that use a range of satellite orbital positions. This document describes the current characterises of common satellite paths and describes considerations when implementing and deploying reliable transport protocols that are intended to work efficiently over paths that include a satellite system. It discusses available network mitigations and offers advice to designers of protocols and operators of satellite networks.}, }