Saratoga: A Scalable Data Transfer Protocol
draft-wood-tsvwg-saratoga-22

Document Type Expired Internet-Draft (individual)
Last updated 2018-06-24 (latest revision 2017-12-17)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
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-wood-tsvwg-saratoga-22.txt

Abstract

This document specifies the Saratoga transfer protocol. Saratoga was originally developed to transfer remote-sensing imagery efficiently from a low-Earth-orbiting satellite constellation, but is useful in many other scenarios, including ad-hoc peer-to-peer communications, large-scale scientific sensing, and grid computing. Saratoga is a simple, lightweight, content dissemination protocol that builds on UDP, and optionally uses UDP-Lite. Saratoga is intended for use when moving files or streaming data between peers which may have permanent, sporadic or intermittent connectivity, and is capable of transferring very large amounts of data reliably under adverse conditions. The Saratoga protocol is designed to cope with highly asymmetric link or path capacity between peers, and can support fully-unidirectional data transfer if required. Saratoga can also cope with very large files for exascale computing. In scenarios with dedicated links, Saratoga focuses on high link utilization to make the most of limited connectivity times, while standard congestion control mechanisms can be implemented for operation over shared links. Loss recovery is implemented via a simple negative-ack ARQ mechanism. The protocol specified in this document is considered to be appropriate for experimental use on private IP networks.

Authors

Lloyd Wood (lloydwood@users.sourceforge.net)
Wesley Eddy (wes@mti-systems.com)
Charles Smith (charlesetsmith@me.com)
Will Ivancic (ivancic@syzygyengineering.com)
Chris Jackson (C.Jackson@sstl.co.uk)

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