1 / 6

Mbus Update

Mbus Update. draft-ietf-mmusic-mbus-transport-03.txt. Jörg Ott jo@tzi.uni-bremen.de Colin Perkins csp@east.isi.edu Dirk Kutscher dku@tzi.uni-bremen.de. Quick Reminder. Local coordination mechanism Specification split into three pieces Requirements overview

mia-schultz
Download Presentation

Mbus Update

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. Mbus Update draft-ietf-mmusic-mbus-transport-03.txt Jörg Ott jo@tzi.uni-bremen.de Colin Perkins csp@east.isi.edu Dirk Kutscher dku@tzi.uni-bremen.de 49. IETF, San Diego Ott/Perkins/Kutscher

  2. Quick Reminder • Local coordination mechanism • Specification split into three pieces • Requirements overview • Definition of the “transport protocol” • Message syntax, addressing, local multicast, reliability, authentication, ... • Definition of the message semantics • Call-control, media tools related commands 49. IETF, San Diego Ott/Perkins/Kutscher

  3. Overview of Changes indraft-ietf-mmusic-mbus-transport-03 • Allow for use of broadcast • Only when multicast is not available • Scope-relative multicast address • Yet to be assigned • MUST NOT use scopes larger than link-local • Resolution of timestamps now milliseconds • Bug-fixes • Message syntax ABNF, use CRLF throughout 49. IETF, San Diego Ott/Perkins/Kutscher

  4. Remaining Issues • Security • Currently advocating DES • Adopt AES, padding is already considered • IPv6 • Should already be considered, need to check once more • References in draft • Check normative references etc. • Congestion Control required? • Remember: link-local scope • Cannot determine link bandwidth reliably • There may not be receivers behind every bridge… • IANA • Scope-relative address and port number • Registration has been requested… 49. IETF, San Diego Ott/Perkins/Kutscher

  5. Next steps • Mbus-transport essentially stable • Pending small changes... • No further features/changes planned • One more draft submission before WG-last-call? • Standards Track or Informational? 49. IETF, San Diego Ott/Perkins/Kutscher

  6. http://www.dmn.tzi.org/ietf/mmusic/mbus/ 49. IETF, San Diego Ott/Perkins/Kutscher

More Related