IETF-58 Minneapolis1

1
Datagram Congestion Control (DCCP) working group

• Slides are available at
• http//www.icir.org/kohler/dccp/ietf58
• Mailing list
• http//www1.ietf.org/mailman/listinfo/dccp

2
DCCP Meeting Agenda

• Agenda bashing, schedule discussion, etc 10 min
• Design Review Followup 60 min
• Open issues
• Changes made
• No change needed
• CCID-3 Thin discussion 15 min
• User Guide 15 min

3
DCCP Working Group Schedule

• Sep-Nov 03 Incorporate review
  and implementation feedback into spec
• Oct 03 Collaborate with avt wg on API
• IETF-58 Prepare for WGLC
• Nov 03 WGLC for spec, CCIDs
• Dec 03 WGLC on User Guide

4
Revised Schedule

• IETF-58 Collaborate with avt wg on API
• IETF-58 Prepare for WGLC
• Nov 03 Revise spec, CCIDs
• Dec 03 WGLC for spec, CCIDs
• Dec 03 Publish user-guide rev1
• Feb 04 Publish user-guide rev2
• Mar 04 WGLC on User Guide

5
API feedback from AVT

• Some discussion of issues on dccp list
• Issue summary sent to mmusic
• Forwarded to avt
• Eddie on AVT agenda, Wed 0900

6
(No Transcript)
7
CCID-3 Thin poll

• Should DCCP take draft-ietf-dccp-ccid3-thin-00.tx
  ton as a new deliverable?
• How hard is this?
• Pretty simple
• Keep thinking about how to express this task as a
  possible future work item
• Consider making CCID3-thin an appendix to spec as
  an existence proof of simplicity
• Why not multiple profiles all requiring state
  machine changes is BAD
• May be premature, consider CCID-4 future

8
Work to be done

• Can you send slightly above congestion control
  allowed rate? (up to twice allowed rate)
• Possibly a work item in tsvwg
• During slow start or after idle, are you allowed
  to send at more than twice the current rate?
• Clearly research
• TFRC w/variable packet sizes
• Expected in tsvwg, on Sallys list

9
Moving forward, a poll

• How many are following the working group (reading
  list, drafts)?
• Of those, how many are planning on going to Korea?

10
Adjourn.

• Thanks!