DatagramCongestion Control Protocol WG (dccp)

THURSDAY, March 4 at 1300-1500
==============================

CHAIR: Aaron Falk <falk@isi.edu>

AGENDA:

1. Working Group Status and Plans (Falk)    10min


2. Spec & CCID Update (Handley)  20min


   The spec has been updated based on a with a large number of small
   changes meant to improve clarity and consistancy.  This is a chance
   to comment on changes including:


   Spec changes (draft-ietf-dccp-spec-06.txt):
    * Organization overhaul.
    * Add pseudocode for event processing.
    * Remove # NDP; replace with Ack Count.
    * Remove Identification, Challenge, ID Regime, and Connection Nonce.
    * Data Checksum (formerly Payload Checksum) uses a 32-bit CRC.
    * Switch location of non-negotiable features to clarify
      presentation; now the feature location controls its value.
    * Rename "value type" to "reconciliation rule".
    * Rename "Reset Reason" to "Reset Code".
    * Mobility ID becomes 128 bits long.
    * Add probabilities to Mobility ID discussion.
    * Add SyncAck.


   CCID2 changes (draft-ietf-dccp-ccid2-05.txt):
    * Disallow direct tracking of TCP standards.


   CCID3 changes (draft-ietf-dccp-ccid3-05.txt):
    * Added more text to the section on Congestion Control on Data
      Packets to make it more readable, and to summarize the key
      mechanisms specified in the TFRC spec.


    * Said that it is OK to use an initial sending rate of 2-4
      pkts/RTT, based on RFC 3390.  And that in the future an initial
      sending rate of up to 8 pkts/RTT might be specified, for very
      small packets.


    * Receive Rate is measured in bytes per second, as RFC 3448
      specifies.


    * New definition of Loss Intervals option, because old definition
      was 24-bit-sequence-number specific; and add an example.


3. Summary of Related Mail List Discussion  (Handley)  25min


   In December there was a spirited discussion on the dccp mailing
   list about the applicability of TFRC to multimedia streams.  Mark
   will summarize the discussion and how it applies to DCCP.


4. Update on DCCP User Guide (Phelan)  30min


   The approach in the User Guide has changed significantly from an
   API approach to be more of instructions on how to use DCCP to
   support various types of applications.  Tom will highlight
   areas which require more consensus and input.


   See draft-ietf-dccp-user-guide-01.txt.