TFRC-based Congestion Control for Saratoga
draft-eddy-tsvwg-saratoga-tfrc-09
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2016-05-03
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
Network Working Group W. Eddy
Internet-Draft MTI Systems
Intended status: Experimental L. Wood
Expires: November 4, 2016 Surrey alumni
W. Ivancic
NASA
May 3, 2016
TFRC-based Congestion Control for Saratoga
draft-eddy-tsvwg-saratoga-tfrc-09
Abstract
This document specifies the use of TCP-Friendly Rate Control (TFRC)
with the Saratoga data transfer protocol. The necessary conventions
that a Saratoga sender and receiver implementation must follow if
they wish to enable the use of TFRC are described.
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 November 4, 2016.
Copyright Notice
Copyright (c) 2016 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.
Eddy, et al. Expires November 4, 2016 [Page 1]
Internet-Draft Saratoga TFRC May 2016
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. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Receiver-Side Behavior . . . . . . . . . . . . . . . . . . . 3
3. Sender-Side Behavior . . . . . . . . . . . . . . . . . . . . 4
4. Security Considerations . . . . . . . . . . . . . . . . . . . 6
5. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
6. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 7
7. References . . . . . . . . . . . . . . . . . . . . . . . . . 7
7.1. Normative References . . . . . . . . . . . . . . . . . . 7
7.2. Informative References . . . . . . . . . . . . . . . . . 7
Appendix A. Differences from Shahriar et al. . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 8
1. Introduction
In order to support use of the Saratoga protocol
[draft-wood-tsvwg-saratoga] on networks with multiple data flows,
multiple hops, and/or experimentally on the Internet, some form of
congestion control is required. Particularly, for use on the
Internet, rather than the private links and networks that Saratoga
was originally developed for, congestion control is a requirement, as
indicated by the UDP Guidelines [RFC5405].
This document provides the specification of one type of congestion
control, based on TCP-Friendly Rate Control (TFRC), which is intended
to be fairly conservative in terms of performance. Better-performing
congestion-control algorithms are possible in terms of throughput,
but this TFRC-based algorithm has the advantages of being relatively
simple and based on the well-established TFRC components, rather than
on a newer and less well-tested mechanism.
Saratoga data flow occurs within uniquely identified transactions
between a sender and receiver. Saratoga primitively supports link-
local multicast to a set of receivers, but that use case is not
considered further in this specification and is considered out of
scope for this document. The congestion control mechanism specified
in this document operates within a single transaction between a
sender and a receiver. Subsequent or concurrent transactions between
the same nodes use distinct congestion control state.
TFRC has "receiver-based" and "sender-based" variations, as
Show full document text