Re: DTLS-SDP: TLS support added
Christer Holmberg <[email protected]>
| Newsgroups | gmane.ietf.mmusic |
|---|---|
| Message-ID | <[email protected]> |
Hi, Based on the input from Roman, I’ve updated the pull request. https://github.com/cdh4u/draft-dtls-sdp/pull/26 I used separate commits for the ‘connection attribute clarification’ and the ‘TLS justification’. Regards, Christer From: Roman Shpount [mailto:[email protected]] Sent: 10 April 2017 23:01 To: Christer Holmberg <[email protected]> Cc: mmusic (E-mail) <[email protected]>; [email protected]; Ben Campbell <[email protected]> Subject: Re: [MMUSIC] DTLS-SDP: TLS support added On Sun, Apr 9, 2017 at 3:14 AM, Christer Holmberg <[email protected]<mailto:[email protected]>> wrote: Now, I think we do need some text on WHY we also cover TLS connections since, as far as creating new connections is concerned, the ‘connection’ attribute can be used. We know that it would be needed for draft-thomson-avtcore-sdp-uks (https://datatracker.ietf.org/doc/draft-thomson-avtcore-sdp-uks/). But, AFAIK that work has not been adopted yet, so I don’t think we can use it as justification at this point? I was thinking that we should include something like: The pair of newly defined SDP 'tls-id' attribute values from the offer and the corresponding answer can be used to uniquely identify TLS or DTLS association. This unique identifier can be used by TLS protocol extensions to differentiate between multiple TLS and DTLS association and correlate these associations with specific offer/answer exchanges. _____________ Roman Shpount _______________________________________________ mmusic mailing list [email protected] https://www.ietf.org/mailman/listinfo/mmusic