1 / 5

Some Transport Requirements for Telephony / MM Conferencing (non-exhaustive)

Some Transport Requirements for Telephony / MM Conferencing (non-exhaustive). Jörg Ott TELES AG / Universität Bremen TZI. Applications. Call setup / call control Registration, authorization, (monitoring) Intra-/inter-domain reporting Remote device control …

phyllis-reilly
Télécharger la présentation

Some Transport Requirements for Telephony / MM Conferencing (non-exhaustive)

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. Some Transport Requirements forTelephony / MM Conferencing(non-exhaustive) Jörg Ott TELES AG / Universität Bremen TZI 43rd IETF - RUTS BOF

  2. Applications • Call setup / call control • Registration, authorization, (monitoring) • Intra-/inter-domain reporting • Remote device control • … • No traditional bulk data transfer 43rd IETF - RUTS BOF

  3. Sample Types of Traffic Call Remote control Reporting 1 1 2 3 4 5 6 1 5 9 1 1 2 4 1 1 2 3 4 43rd IETF - RUTS BOF

  4. Transport Requirements • End-to-end reliability • Implicit “connection setup” • Robust against denial of service attacks • Tunable parameters:per “connection” and per datagram • reliability level, timeout, retransmissions, … • initial congestion window • substitution / (forced) expiration of queued data 43rd IETF - RUTS BOF

  5. Current Solutions Application layer reliability • Partially PDU-specific timeouts • fixed timeouts + backoff mechanisms • Simple acknowledgement mechanism • lock step or windowing • Allow reliable + unreliable data within the same “connection” • Solutions tailored to respective problem • but general purpose transport desirable 43rd IETF - RUTS BOF

More Related