Re: Handling of unverified data and media
Iñaki Baz Castillo <[email protected]>
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <CALiegfkfntWj56NEXhr_waogJtsw9oy_P0Jo331ba_WNzBGRSQ@mail.gmail.com> |
AFAIK you dont need a SDP aswer for that. El 11/3/2017 16:24, "Christer Holmberg" <[email protected]> escribió: > Hi, > > In case of a Data Channel, you also need to establish the SCTP association > before you can send any content. > > Regards, > > Christer > > -----Original Message----- > From: mmusic [mailto:[email protected]] On Behalf Of Iñaki Baz > Castillo > Sent: 11 March 2017 17:12 > To: Roman Shpount <[email protected]> > Cc: Flemming Andreasen <[email protected]>; [email protected]; mmusic WG < > [email protected]> > Subject: Re: [MMUSIC] Handling of unverified data and media > > 2017-03-10 23:47 GMT+01:00 Roman Shpount <[email protected]>: > > My assumption always was that data is received, decoded and discarded > > until fingerprint is received and verified. This way DTLS handshake > > completes, key frames are decoded, but user is nor presented with any > unverified media. > > Just imagine an app (running in a computer with public IP) which sends the > SDP offer to a server, DTLS handshake is done, and the server sends > DataChannel messages to the browser *before* the browser receives the SDP > answer. > > Do you mean that such a DataChannel messages should be discarded? I > consider that catastrophic as the server may not know whether the browser > has yet received the answer or not. Apps should implement some kind of > 3-way signaling handshake (send offer, receive answer, send > ACK) before the server sends any DataChannel message. > > > -- > Iñaki Baz Castillo > <[email protected]> > > _______________________________________________ > mmusic mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/mmusic > _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic