Re: draft-dtls-sdp: Allow offerer to establish DTLS association before it has received the SDP answer?
Martin Thomson <[email protected]>
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <CABkgnnXY+uwW=iPjT3O=TmnYj4CD-PYRYkSMTWc5QiFEVBsNiA@mail.gmail.com> |
On 23 May 2017 at 19:59, Christer Holmberg <[email protected]> wrote: > If I understand correctly, you seem to suggest that we allow the handshake > to ³proceed² (see 1st paragraph of your reply), but not to ³complete². If > so, which endpoint is responsible to make sure that it doesn¹t ³complete²? Whichever endpoint is unable to acquire the information it needs in order to determine that the handshake is good. >>Second in preference to that is to allow received data to be saved, >>but not used. In no circumstance should we allow data to be *sent*. > > I assume that also includes e.g., SCTP messages, i.e., in case of a WebRTC > Data Channel it wouldn¹t be allowed to establish the SCTP association. Yes, if you don't know to whom you are sending things, the only safe action is not to send. You can carve out exceptions for things like handshaking SCTP on the proviso that they are found to contain no actionable content, but that's tricky. _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic