A new Request for Comments is now available in online RFC libraries.
RFC 4341
Title: Profile for Datagram Congestion Control
Protocol (DCCP) Congestion Control ID 2:
TCP-like Congestion Control
Author: S. Floyd, E. Kohler
Status: Standards Track
Date: March 2006
Mailbox: floyd@xxxxxxxx,
kohler@xxxxxxxxxxx
Pages: 20
Characters: 47868
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-dccp-ccid2-10.txt
URL: http://www.rfc-editor.org/rfc/rfc4341.txt
This document contains the profile for Congestion Control Identifier
2 (CCID 2), TCP-like Congestion Control, in the Datagram Congestion
Control Protocol (DCCP). CCID 2 should be used by senders who would
like to take advantage of the available bandwidth in an environment with
rapidly changing conditions, and who are able to adapt to the abrupt
changes in the congestion window typical of TCP's Additive Increase
Multiplicative Decrease (AIMD) congestion control. [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@xxxxxxxxx Requests to be
added to or deleted from the RFC-DIST distribution list should
be sent to RFC-DIST-REQUEST@xxxxxxxxxxxxxxx
Details on obtaining RFCs via FTP or EMAIL may be obtained by sending
an EMAIL message to rfc-info@xxxxxxxxxxxxxx with the message body
help: ways_to_get_rfcs. For example:
To: rfc-info@xxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx Please consult RFC 2223, Instructions to RFC
Authors, for further information.
Joyce K. Reynolds and Sandy Ginoza
USC/Information Sciences Institute
...
