2021-10-27

[kenyonja]

Notes from meeting on 27 October 2021.

• Need to determine which SDP to use to create MPD - initial offer, final response, etc.
• Ofer asked about including everything in one adaptation set in the MPD
  • Thomas said that you need to have them separate for multiple language support
• WebRTC server has negotiation to get SDP; don't expect to repeat all data in SDP in the MPD.
• Goal is to use DASH to describe content
  • Customers have standard DASH players, but if you want to do WebRTC you need a custom player
  • MPD should have everything needed by player UI to present options to users.
  • If stuff for UI (audio language, etc.) then include in MPD, as well as content IDs, etc., anything you want to tell the - server when requesting the content.
  • Need an MPD example with all options.
  • Assume that the entity that created MPD knows about the stream
  • May need an API that the DASH player can call to WebRTC engine.
  • Julia to work with Ofer to make picture of discovery process
• Need to break up SDP and format into m-lines and a-lines
  • Reformatted example for readability: https://gist.github.com/englishm/dc613aad494af3d104559e1e3ade52fc
  • So in the example SDP, interesting lines are:
  • m=audio 9 UDP/TLS/RTP/SAVPF 111 103 104 9 0 8 106 105 13 110 112 113 126
  • m=video 9 UDP/TLS/RTP/SAVPF 96 97 98 99 100 101 122 102 121 127 120 125 107 108 109 124 119 123 118 114 115 116 35
• Mike English to add content from
  https://webrtcforthecurious.com/docs/02-signaling/#what-is-the-session-description-protocol-sdp
  to Annex to clarify SDP content

Please add to the discussion if anything in these notes is missing or incorrect.