QUIC for SATCOM
draft-kuhn-quic-4-sat-06

Document Type Replaced Internet-Draft (individual)
Authors Nicolas Kuhn  , Gorry Fairhurst  , John Border  , Stephan Emile 
Last updated 2020-10-30
Replaced by draft-jones-tsvwg-transport-for-satellite
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-jones-tsvwg-transport-for-satellite
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-kuhn-quic-4-sat-06.txt

Abstract

QUIC has been designed for use across Internet paths. Initial designs of QUIC focused on common deployment scenarios for web traffic. This document focuses on the performance when using a path with a large Bandwidth-Delay Product (BDP). A large BDP path can result from using a satellite communication (SATCOM) system. The BDP is also high for paths where a satellite network segment is combined with other network technologies (Ethernet, cable modems, WiFi, cellular, radio links, etc), resulting in more complex characteristics. These path characteristics have implications on the efficiency of the network traffic and unless considered in a design can impact the end-to-end quality of experience by the transport service. This memo identifies the characteristics of a SATCOM link that impact the operation of the QUIC transport protocol. It proposes regression tests to evaluate QUIC over SATCOM links. It discusses how to ensure acceptable protocol performance.

Authors

Nicolas Kuhn (nicolas.kuhn@cnes.fr)
Gorry Fairhurst (gorry@erg.abdn.ac.uk)
John Border (border@hns.com)
Stephan Emile (emile.stephan@orange.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)