2.8.3 Datagram Congestion Control Protocol (dccp)

NOTE: This charter is a snapshot of the 76th IETF Meeting in Hiroshima, Japan. It may now be out-of-date.

Last Modified: 2009-06-26


Thomas Phelan <tphelan@sonusnet.com>
Pasi Sarolahti <pasi.sarolahti@iki.fi>

Transport Area Director(s):

Magnus Westerlund <magnus.westerlund@ericsson.com>
Lars Eggert <lars.eggert@nokia.com>

Transport Area Advisor:

Lars Eggert <lars.eggert@nokia.com>

Mailing Lists:

General Discussion: dccp@ietf.org
To Subscribe: dccp-request@ietf.org
In Body: (un)subscribe
Archive: http://www.ietf.org/mail-archive/web/dccp/index.html

Description of Working Group:

The Datagram Congestion Control Protocol working group is maintaining
the Datagram Congestion Control Protocol (DCCP).

DCCP is a minimal, general-purpose transport protocol that provides two
main functions: (1) the establishment, maintenance and tear-down of an
unreliable packet flow and (2) congestion control of that packet flow.

The DCCP WG is chartered to work in four areas:

* maintenance of the core DCCP protocol
* maintenance of the TFRC congestion control protocol
* promoting the use of DCCP by upper layers
* modular extensions to DCCP

In the first area, the WG focuses on maintenance issues (i.e., bug
fixes) to the current DCCP specifications. It also provides the venue
for moving the DCCP specifications along the Standards Track. To
maintain stable specifications, work in this area is tightly controlled
and requires strong justification.

The second area of work, maintains the TCP Friendly Rate Control (TFRC)
congestion control protocol. This includes identification of issues, bug
fixes, and progression of the specification along the Standards Track.

In the third area, the WG will promote and support the adoption and use
of DCCP by upper-layer applications and protocols. This includes
specifications for using existing and emerging protocols and
applications with DCCP (such as RTP over DCCP and DTLS over DCCP) as
well as supporting documents that enhance DCCP deployment and management.

In the fourth area, the WG identifies and develops modular extensions to
the DCCP specifications that increase the usefulness of DCCP. The goal
of this work is to make DCCP attractive to upper-layer protocols and
applications. The WG will consider both requirements brought to it from
external groups that develop or use upper-layer protocols and
applications and may also itself identify a limited number of
prospective applications and upper-layer protocols to investigate. 

This work will provide refinements to the existing congestion control
schemes  currently provided by DCCP and may also include, for example,
mobility support for DCCP. (The acceptance of new work items on mobility
requires the approval of the IESG.) This work includes the provision of
new congestion control profiles, which are variants of existing ones,
that better serve certain applications, for example, interactive
applications. The WG may consider to recharter in the future to support
the IRTF Internet Congestion Control Research Group (ICCRG) in the
development of new congestion control algorithms through the definition
of concrete specifications for these algorithms.

New work items in the latter two areas must satisfy four conditions:
(1) WG consensus on the suitability and projected quality of the
proposed  work item. (2) A core group of WG participants with sufficient
energy and  expertise to advance the work item according to the proposed
schedule. (3) Commitment from the WG as a whole to provide sufficient
and timely review of the proposed work item. (4) Agreement by the AD,
who, depending on the scope of the proposed work item, may decide that
an IESG review is needed first.

The DCCP WG pursues its work in close collaboration with several other

Goals and Milestones:

Done  Publish summary of required protocol functions/requirements
Done  Decision to build on proposed DCCP protocol, alternate protocol, or quit and go home
Done  Detailed review of spec and CCIDs
Done  Public design review at IETF meeting
Done  Working group last call for spec and CCIDs
Done  Submit DCCP spec for IESG/IETF review to be Proposed Standard
Done  Submit DCCP CCIDs for IESG/IETF review to be Proposed Standard
Done  Complete WGLC draft-ietf-dccp-problem-xx as Informational
Done  Complete WGLC draft-ietf-dccp-tfrc-voip as Experimental
Done  Complete WGLC 'RTP over DCCP' as PS
Done  Complete WGLC 'DTLS over DCCP' as PS
Done  Complete WGLC for draft-ietf-dccp-rfc3448bis as PS
Done  Complete WGLC for draft-ietf-dccp-serv-codes as PS
Done  Complete WGLC draft-ietf-dccp-ccid4 as Experimental
Sep 2008  Complete WGLC draft-ietf-dccp-tfrc-faster-restart as Experimental
Done  Complete WGLC for draft-ietf-dccp-simul-open as PS
Done  Complete WGLC draft-ietf-dccp-quickstart as Experimental


  • draft-ietf-dccp-rtp-07.txt

    Request For Comments:

    RFC4336 I Problem Statement for the Datagram Congestion Control Protocol (DCCP)
    RFC4340 PS Datagram Congestion Control Protocol (DCCP)
    RFC4341 PS Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 2: TCP-like Congestion Control
    RFC4342 PS Profile for Datagram Congestion Control Protocol (DCCP) Congestion Control ID 3: TCP-Friendly Rate Control (TFRC)
    RFC4828 E TCP Friendly Rate Control (TFRC): the Small-Packet (SP) Variant
    RFC5238 PS Datagram Transport Layer Security (DTLS) over the Datagram Congestion Control Protocol (DCCP)
    RFC5348 PS TCP Friendly Rate Control (TFRC): Protocol Specification
    RFC5595 PS The Datagram Congestion Control Protocol (DCCP) Service Codes
    RFC5596 PS Datagram Congestion Control Protocol (DCCP) Simultaneous-Open Technique to Facilitate NAT/Middlebox Traversal
    RFC5622 E Profile for Datagram Congestion Control Protocol (DCCP) Congestion ID 4: TCP-Friendly Rate Control for Small Packets (TFRC-SP)
    RFC5634 E Quick-Start for Datagram Congestion Control Protocol (DCCP)

    Meeting Minutes


    DCCP WG Status
    DCCP User Guide - Going Forward?
    MulTFRC: TFRC with weighted fairness