A new Request for Comments is now available in online RFC libraries.

        RFC 3448

        Title:      TCP Friendly Rate Control (TFRC):
                    Protocol Specification
        Author(s):  M. Handley, S. Floyd, J. Padhye, J. Widmer
        Status:     Standards Track
        Date:       January 2003
        Mailbox:    mjh@icir.org, floyd@icir.org,
        Pages:      24
        Characters: 52657
        Updates/Obsoletes/SeeAlso:    None

        I-D Tag:    draft-ietf-tsvwg-tfrc-05.txt

        URL:        ftp://ftp.rfc-editor.org/in-notes/rfc3448.txt

This document specifies TCP-Friendly Rate Control (TFRC).  TFRC is a
congestion control mechanism for unicast flows
operating in a best-effort Internet environment.  It is
reasonably fair when competing for bandwidth with TCP flows,
but has a much lower variation of throughput over time
compared with TCP, making it more suitable for applications
such as telephony or streaming media where a relatively smooth
sending rate is of importance.

This document is a product of the Transport Area Working Group of the

This is now a Proposed Standard Protocol.

This document specifies an Internet standards track protocol for
the Internet community, and requests discussion and suggestions
for improvements.  Please refer to the current edition of the
"Internet Official Protocol Standards" (STD 1) for the
standardization state and status of this protocol.  Distribution
of this memo is unlimited.

This announcement is sent to the IETF list and the RFC-DIST list.
Requests to be added to or deleted from the IETF distribution list
should be sent to IETF-REQUEST@IETF.ORG.  Requests to be
added to or deleted from the RFC-DIST distribution list should

Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body
help: ways_to_get_rfcs.  For example:

        To: rfc-info@RFC-EDITOR.ORG
        Subject: getting rfcs

        help: ways_to_get_rfcs

Requests for special distribution should be addressed to either the
author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.echo
Submissions for Requests for Comments should be sent to
RFC-EDITOR@RFC-EDITOR.ORG.  Please consult RFC 2223, Instructions to RFC
Authors, for further information.