[AVT] Sockets in multicast DTLS-SRTP

Romain Biehlmann <romain.biehlmann@gmail.com> Tue, 23 March 2010 12:29 UTC

Return-Path: <romain.biehlmann@gmail.com>
X-Original-To: avt@core3.amsl.com
Delivered-To: avt@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id EACDF3A6B0C for <avt@core3.amsl.com>; Tue, 23 Mar 2010 05:29:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.131
X-Spam-Level: *
X-Spam-Status: No, score=1.131 tagged_above=-999 required=5 tests=[BAYES_50=0.001, DNS_FROM_OPENWHOIS=1.13]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PGUjPEoNPDGr for <avt@core3.amsl.com>; Tue, 23 Mar 2010 05:29:09 -0700 (PDT)
Received: from mail-wy0-f172.google.com (mail-wy0-f172.google.com [74.125.82.172]) by core3.amsl.com (Postfix) with ESMTP id 197423A6B83 for <avt@ietf.org>; Tue, 23 Mar 2010 05:27:05 -0700 (PDT)
Received: by wyb29 with SMTP id 29so3005545wyb.31 for <avt@ietf.org>; Tue, 23 Mar 2010 05:27:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=y7OHlxCqUj7dnU3h6iLmssIVeoMXV6mCrbVa6FTJ3Fk=; b=JTaSPN5DGVKyszyHCDq/AqV9pBpiaF8OOtP12pkvNmMpua6hqNEcCnI0q//s0TJX6K YgG5+S84MjzzxwHjRrm6Ei8pyX+oIKwgYdzf6kkaAR0zOZ8XImX9wCEW4AHdxTzRKqsG mqx6CecgxMUAuA0jUoTkNa+BLBWvDuCusari0=
DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=CMMVr2LJJRZGbrILPhBTbZPb2D6nupFSf9N+rpToeHDYd62iSK1kNxvGVNJx3LMwES biOCsjyaNbeNpGXV8d+3IfJJ3GyzIVwKTApBHfrOCKF0j0GW5eHe1IXGRdrgk6M6MwCZ VYqULlCG1HXKh/PJzH4kfsCOfYD+x9k5DAeRQ=
MIME-Version: 1.0
Received: by 10.216.171.207 with SMTP id r57mr621209wel.146.1269347241618; Tue, 23 Mar 2010 05:27:21 -0700 (PDT)
Date: Tue, 23 Mar 2010 13:27:21 +0100
Message-ID: <9a06dcf1003230527q39fc7f9bye2ca616599e95cac@mail.gmail.com>
From: Romain Biehlmann <romain.biehlmann@gmail.com>
To: avt@ietf.org
Content-Type: text/plain; charset="ISO-8859-1"
Subject: [AVT] Sockets in multicast DTLS-SRTP
X-BeenThere: avt@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Audio/Video Transport Working Group <avt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/avt>
List-Post: <mailto:avt@ietf.org>
List-Help: <mailto:avt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/avt>, <mailto:avt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Mar 2010 12:29:14 -0000

Hi all,

I hope my question is not too dumb, and not too
implementation-oriented; if so, please accept my apologies and ignore
it.

In http://tools.ietf.org/html/draft-ietf-avt-dtls-srtp-07 chapter
5.1.1, we can read the following:
"When a user of DTLS wishes to send an RTP packet in SRTP mode it
delivers it to the DTLS implementation as an ordinary application data
write (e.g., SSL_write())."

>From that, I understand that in the case of a unicast session, only
one socket is needed for the transmission of STUN, SRTP and DTLS
datagrams.
I am not sure, though, to get how it should work in the case of a (one
to many) multicast session.

Isn't the server supposed to send SRTP datagrams to a broadcast
address, whereas DTLS data must be sent directly to (unicast)
designated clients? Is the sentence in the draft only applicable to
unicast?

I thank you in advance for your valuable insight.

Romain