datatracker.ietf.org
Sign in
Version 5.4.0, 2014-04-22
Report a bug

Congestion control for the Saratoga protocol
draft-wood-tsvwg-saratoga-congestion-control-05

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2014-04-19
Intended RFC status: Unknown
Other versions: plain text, pdf, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

Network Working Group                                            L. Wood
Internet-Draft                                             Surrey alumni
Intended status: Experimental                                    W. Eddy
Expires: October 21, 2014                                    MTI Systems
                                                              W. Ivancic
                                                                    NASA
                                                          April 19, 2014

              Congestion control for the Saratoga protocol
            draft-wood-tsvwg-saratoga-congestion-control-05

Abstract

   Saratoga is a data transfer protocol designed to carry potentially
   large volumes of data over difficult network paths, often including
   only a single high-rate link and only one application flow.  As the
   requirements for use vary across deployment environments, the base
   Saratoga specification only assumes that an implementation will be
   able to clock packets out at a configurable rate, and beyond this
   specifies no inherent or particular congestion-control behaviour.
   The design of Saratoga deliberately supports the integration of
   congestion-control algorithms without modification to the base
   protocol.  This document describes how congestion control can be
   supported in the Saratoga transfer protocol.  Saratoga is intended
   for use in private networks, where its use is engineered as a single
   flow to fill a link.  However, as Saratoga is implemented over UDP,
   it can be multiplexed, and can be run across the public Internet, in
   which case congestion control in accordance with the UDP Guidelines
   becomes necessary.

Status of This Memo

   This Internet-Draft is submitted to IETF in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on October 21, 2014.

Wood, et al.            Expires October 21, 2014                [Page 1]
Internet-Draft         Saratoga congestion control            April 2014

Copyright Notice

   Copyright (c) 2014 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.

   This document may not be modified, and derivative works of it may not
   be created, except to format it for publication as an RFC or to
   translate it into languages other than English.

Table of Contents

   1.  Background and Introduction . . . . . . . . . . . . . . . . .   2
   2.  Approaches to congestion control  . . . . . . . . . . . . . .   3
     2.1.  TCP-friendly rate control . . . . . . . . . . . . . . . .   3
     2.2.  Explicit Congestion Notification  . . . . . . . . . . . .   3
   3.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   4.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   5.  Acknowledgements  . . . . . . . . . . . . . . . . . . . . . .   4
   6.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     6.1.  Normative References  . . . . . . . . . . . . . . . . . .   4
     6.2.  Informative References  . . . . . . . . . . . . . . . . .   4
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Background and Introduction

   The Saratoga data transfer protocol is described in
   [draft-wood-tsvwg-saratoga].  Given that Saratoga was originally
   developed for scheduled peer-to-peer communications over dedicated
   links in private networks, where each application has the entire link
   for the duration of its transfer, many Saratoga implementations
   deliberately lack any form of congestion control and send at line
   rate to maximise throughput and link utilisation in their
   environments.  Congestion control is necessary for use in the public
   Internet, in accordance with the UDP Guidelines [RFC5405].  Newer
   Saratoga implementations may use timestamps to perform TCP-Friendly
   Rate Control (TFRC) [RFC5348] or other congestion control mechanisms

[include full document text]