Re: Mirja Kühlewind's Discuss on draft-ietf -mmusic-sctp-sdp-23: (with DISCUSS)
Christer Holmberg <[email protected]>
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <[email protected]> |
Hi, … >The only question is what should appear in the m= proto line. Even if nobody puts it in the m= line, I think it’s useful to keep it in the document, as it gives an overview how it’s realized etc. It doesn’t cause any harm to keep it, and it’s “future proof” IF someone wants to use it without ICE at some point. Regards, Christer > Am 16.02.2017 um 16:02 schrieb Eric Rescorla <[email protected]<mailto:[email protected]>>: > > As Christer says. This design is optimized for making the media stack simpler, which > using TLS here would not do. > > -Ekr > > > > > On Thu, Feb 16, 2017 at 7:00 AM, Christer Holmberg <[email protected]<mailto:[email protected]>> wrote: > Hi, > > ---------------------------------------------------------------------- > DISCUSS: > ---------------------------------------------------------------------- > > >>> Why is this using TCP/DTLS/SCTP instead of TCP/TLS/SCTP? > >>> > >> Because the way it is realized is by transporting SCTP on top of DTLS (as defined in draft-ietf-tsvwg-sctp-dtls-encaps) and > >> transporting DTLS on top of TCP (defined in RFC 4571). > > > > I got this but DTLS is a mapping to use TLS with UDP because UDP is an unreliable datagram transport. If you use TCP, you > > should use TLS. And rfc4571 is not a mapping of DTLS to TCP. > > The framing mechanism of RFC 4571 is used, with DTLS packets sent instead of RTP packets. > > Regards, > > Christer > > _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic