1 / 5

DCP: Datagram Control Protocol

DCP: Datagram Control Protocol. Tim Sohn and Eiman Zolfaghari March 11, 2002. Motivation and Problem. Motivation Growth of real time applications (e.g. IP telephony) UDP avoids built-in congestion control Problem Arbitrary delay when using TCP reliability

nodin
Download Presentation

DCP: Datagram Control Protocol

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DCP: Datagram Control Protocol Tim Sohn and Eiman Zolfaghari March 11, 2002

  2. Motivation and Problem • Motivation • Growth of real time applications (e.g. IP telephony) • UDP avoids built-in congestion control • Problem • Arbitrary delay when using TCP reliability • Difficult to implement own congestion control tsohn@cs.berkeley.edu, eiman@uclink.berkeley.edu

  3. Solution • New Transport Protocol (DCP) • Offers unreliable delivery • Accommodates different congestion control • Congestion Control IDs • TCP-friendly Rate Control (TFRC) • TCP-like congestion control • Half-Connection • Data Packets sent in one direction tsohn@cs.berkeley.edu, eiman@uclink.berkeley.edu

  4. Status • Studied Relevant Work • TCP-friendliness, measurements • Testbed • 2 computers • 1 running NistNet (network emulator) • Send packets between computers tsohn@cs.berkeley.edu, eiman@uclink.berkeley.edu

  5. Future Plans • Complete connection handling and CCID interface in main DCP code (end of March) • Done by students under Kevin Lai • Design measurement tests and implement CCID code (beginning of April) • Run test and analyze results (end of April) • Write report (beginning of May) tsohn@cs.berkeley.edu, eiman@uclink.berkeley.edu

More Related