Re: [dccp] HEADS UP: charter update proposal

[Lars Eggert <lars.eggert at netlab.nec.de>]

On Mar 16, 2006, at 10:37, Lars Eggert wrote:
> Please take a look and send your comments!

While preparing some agenda slides, I came across some minor wording  
nits in the charter proposal I emailed previously. Below is a gnu  
wdiff between the previous and current versions, with changes marked  
in curly braces.

Lars


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 three areas:
        * maintenance of the core DCCP protocol
        * modular extensions to DCCP
        * promoting the use of DCCP by upper layers

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. In  
order to maintain stable specifications, work in this area is tightly  
controlled and requires strong justification.

In the second 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.  
Work in this {+second+} area will provide refinements to the existing  
congestion control schemes currently provided by DCCP and may also  
include, for example, mobility support for DCCP. Work items will also  
provide new congestion control profiles, which are variants of  
existing ones, that better serve certain applications, for example,  
interactive applications. For entirely new {+congestion control+}  
algorithms, the DCCP [-group-] {+WG+} may support the IRTF's Internet  
Congestion Control Research Group (ICCRG) by specifying concrete  
implementations of algorithms under serious investigation in the ICCRG.

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.

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 IETF WGs and IRTF RGs, including TSVWG, AVT, MMUSIC, BEHAVE,  
ICCRG and TMRG.

Initial Milestones:

Jun 2006        Complete WGLC draft-ietf-dccp-tfrc-media-xx as  
Informational
Jun 2006        Complete WGLC draft-ietf-dccp-tfrc-faster-restart-xx  
as Experimental
Jun 2006        Complete WGLC draft-ietf-dccp-tfrc-voip-xx as  
Experimental
Jun 2006        Complete WGLC draft-ietf-dccp-user-guide-xx as  
Informational
Mar 2007        Complete WGLC of RTP over DCCP as Proposed Standard
Jun 2007        Complete WGLC of DTLS over DCCP as Proposed Standard
Jun 2007        Complete WGLC of DCCP mobility extensions as Proposed  
Standard

--
Lars Eggert                                     NEC Network Laboratories

Attachment: smime.p7s
Description: S/MIME cryptographic signature