Add use_srtp extension about dtls HOT 9 OPEN

This is rfc5764. To be clear, SRTP I/O should do any other package. This package only for dtls. The use_srtp extension might be implemented by this package.The internal socket of dtls I/O might be reused. It's just a duplex stream:

Anyway, SRTP is a part of Media API which is not my priority. I focused only on datachannels. Only any business interests and support may change my internal priority 😸 .

from dtls.

Let my clarify that I'm not asking for this dtls lib to do SRTP I/O at all. I just meant that it may enable it by negotiating use_srtp DTLS extension in the handshake.

Now, sorry for the off-topic:

What it comes to my mind when I see all these stun, ice, dtls, etc great libs is the ability to create a modular DataChannel or a SRTP stack in Node. Let me show it in pseudo-code:

const ice = require('@nodertc/ice');
const dtls = require('@nodertc/dtls');
const rtp = require('@foo/rtp');
const srtp = require('@foo/srtp');
const is_rtp = require('is-rtp');

// Create a ICE connection.
const iceConnection = ice.connect(
  {
    remoteCandidates : [ {}, {}, {}... ],
    userFrag : 'iaasdgjahsdgjh',
    password : '1234'
  });

// Wait for ICE to be established.
await new Promise((resolve) => iceConnection.on('connected', resolve));

// Create a DTLS association on top of the ICE connection.
// Note that iceConnection.getSocket() does not return a net.Socket
// but a special object with similar interface. This is because ICE
// may move to a different ip:port tuple at any time due to reconnections
// after ICE disconnections.
const dtlsConnection = dtls.connect(
  {
    socket  : iceConnection.getSocket(),
    useSrtp : true
  });

// Wait for DTLS to be connected.
await new Promise((resolve) => dtlsConnection.on('connected', resolve));

// Create a SRTP session with the material negotiated via DTLS.
const srtpSession = srtp.createSession(
  {
    keys : dtlsConnection.getSrtpKeys()
  });

// Create a dummy RTP packet.
const rtpPacket = rtp.createPacket(
  {
    payloadType : 111,
    seq         : 12345,
    timestamp   : Date.now(),
    payload     : new Buffer(...)
  });

// Encrypt the packet with SRTP.
const srtpPacket = srtpSession.encrypt(rtpPacket);

// Send the SRTP packet.
iceConnection.send(srtpPacket.getRaw());

// Listen for incoming SRTP packets.
iceConnection.on('packet', (packet) =>
{
  if (is_rtp(packet))
  {
    const srtpPacket = rtp.parse(packet);
    const rtpPacket = srtpSession.decrypt(srtpPacket);

    console.log(
      'received RTP packet [payloadType:%d, seq:%d]',
      rtpPacket.getPayloadType(), rtpPacket.getSeq());
  }
});

Do you have something like this in mind? Jjust ignore the RTP/SRTP stuff above, please, it can be done by a 3rd party library.

from dtls.

Yes, you're right. It may look somethings like this. One note: srtp/rtp should wait for complete dtls connection:

//...
dtlsConnection.once('connect', () => {
	// ready for any i/o.
});
//...

from dtls.

Yes, I already waited for DTLS connection in my pseudo code above:

// Wait for DTLS to be connected.
await new Promise((resolve) => dtlsConnection.on('connect', resolve));

:)

from dtls.

Let me just one question more, please.

I'm looking for the best way to implement DataChannel in my SFU mediasoup. mediasoup is Node with C++ subprocesses that handle media (UDP, TCP, ICE, DTLS, SRTP, etc). The Node layer controls those C++ subprocesses via UnixSocket.

Once the DTLS is established, I already have a C++ API to send and receive "DTLS application data":

• https://github.com/versatica/mediasoup/blob/v3/worker/src/RTC/DtlsTransport.cpp?ts=2#L810
• https://github.com/versatica/mediasoup/blob/v3/worker/src/RTC/DtlsTransport.cpp?ts=2#L804

If we assume that those "DTLS application data" are SCTP packets, I can push them verbatim to the mediasoup Node.js layer and use your sctp and datachannel libs to process them, am I right?

Assuming that, it's not clear to me how to combine both sctp and datachannel libs. I expect that received DTLS data should be given to the sctp lib. However, it seems that sctp requires a transport (got via dtls.connect()), and dtls requires a UDP socket which breaks my modular design. Basically I don't want that Node.js does networking at all, I already do networking at C++ level.

Is my use case possible using your libs? Perhaps the dtls Socket can be provided with a Node Stream pair instead of having to pass a UDP socket?

P.S. I do not see any API in sctp for sending data to the remote endpoint. Do I miss something?

from dtls.

First, sctp was implemented by not me. I fixed only 2 things:

• i deleted native dependencies
• internal udp transport might be just a duplex stream

This module may have bugs and do not follow my standards of code quality. You may ask @latysheff as original author sctp about stability.

As i sayd before, after my fixes tansport may be just a duplex stream. See

https://github.com/nodertc/nodertc/blob/a7bd7aca00bd389723f3cdc665653459667c408a/index.js#L328-L350

for details. It's nodertc prototype.

from dtls.

P.S. I do not see any API in sctp for sending data to the remote endpoint. Do I miss something?

The API of sctp module is the same as Node's Net module. That is, use socket.write() to send data. There are also examples of how to use sctp sockets.
p.s. For now, there is no active support for the module, code is not covered by unit tests, but overall stability is fairly good, if viewed as black box. I have conducted long-running load tests, compatibility tests, etc, and noticed no memory leaks or crashes.

from dtls.

Thanks to both for your comments. So now there are two Node SCTP implementations that can run over DTLS:

• @nodertc/sctp, which accepts a duplex stream as transport.
• @latysheff/node-sctp, which requires a real UDP socket (so not valid for my use case).

@reklatsmasters, if you are building a complete DataChannel stack I assume you'll have to eventually work on @nodertc/sctp as a core component of that DataChannel stack, am I right?

from dtls.

@ibc yes.See https://github.com/nodertc/nodertc/blob/a7bd7aca00bd389723f3cdc665653459667c408a/index.js to understand how it’s work.

from dtls.