- From: Bernard Aboba <Bernard.Aboba@microsoft.com>
- Date: Wed, 16 Dec 2015 17:13:25 +0000
- To: "public-ortc@w3.org" <public-ortc@w3.org>
- Message-ID: <BLUPR03MB149760720B4B5AD6752DD3EECEF0@BLUPR03MB149.namprd03.prod.outlook.com>
Fippo said: "nit: the definitions of the connecting and connected state in http://ortc.org/wp-content/uploads/2015/10/ortc.html#idl-def-RTCDtlsTransportState focus a little too much on DTLS-SRTP. Needs some wordsmithing for SCTP/data channels." [BA] Here are some thoughts: OLD: connecting DTLS is in the process of negotiating a secure connection. Once a secure connection is negotiated and DTLS-SRTP has derived keys (but prior to verification of the remote fingerprint, enabled by calling start()), incoming media can flow through. connected DTLS has completed negotiation of a secure connection (including DTLS-SRTP and remote fingerprint verification). Outgoing media can now flow through. NEW: How about this? connecting DTLS is in the process of negotiating a secure connection and verifying the remote fingerprint. Once a secure connection is negotiated (but prior to verification of the remote fingerprint, enabled by calling start()), incoming data can flow through (and media, once DTLS/SRTP key derivation is completed). connected DTLS has completed negotiation of a secure connection and verified the remote fingerprint. Outgoing data and media can now flow through.
Received on Wednesday, 16 December 2015 17:13:55 UTC