RFC 4342 on Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)

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

        RFC 4342

        Title:      Profile for Datagram Congestion Control 
                    Protocol (DCCP) Congestion Control ID 3: 
                    TCP-Friendly Rate Control (TFRC) 
        Author:     S. Floyd,  E. Kohler, 
                    J. Padhye
        Status:     Standards Track
        Date:       March 2006
        Mailbox:    floyd@icir.org, 
                    kohler@cs.ucla.edu, 
                    padhye@microsoft.com
        Pages:      33
        Characters: 83054
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-dccp-ccid3-11.txt

        URL:        http://www.rfc-editor.org/rfc/rfc4342.txt

This document contains the profile for Congestion Control Identifier
3, TCP-Friendly Rate Control (TFRC), in the Datagram Congestion
Control Protocol (DCCP).  CCID 3 should be used by senders that want
a TCP-friendly sending rate, possibly with Explicit Congestion
Notification (ECN), while minimizing abrupt rate changes.  [STANDARDS TRACK]

This document is a product of the Datagram Congestion Control Protocol
Working Group of the IETF

This is now a Proposed Standard Protocol.

STANDARDS TRACK: 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
be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG.

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.

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.

Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute

...

_______________________________________________
IETF-Announce mailing list
IETF-Announce@ietf.org
https://www1.ietf.org/mailman/listinfo/ietf-announce