Re: [rtcweb] security-arch: RTP and RTCP Key Management (mux and non-mux)

Bernard Aboba <bernard.aboba@gmail.com> Tue, 22 July 2014 17:18 UTC

Return-Path: <bernard.aboba@gmail.com>
X-Original-To: rtcweb@ietfa.amsl.com
Delivered-To: rtcweb@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 768681B29AD for <rtcweb@ietfa.amsl.com>; Tue, 22 Jul 2014 10:18:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id M8Xj8mW1FMpw for <rtcweb@ietfa.amsl.com>; Tue, 22 Jul 2014 10:18:57 -0700 (PDT)
Received: from mail-we0-x231.google.com (mail-we0-x231.google.com [IPv6:2a00:1450:400c:c03::231]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E03381A0180 for <rtcweb@ietf.org>; Tue, 22 Jul 2014 10:18:56 -0700 (PDT)
Received: by mail-we0-f177.google.com with SMTP id w62so9524346wes.22 for <rtcweb@ietf.org>; Tue, 22 Jul 2014 10:18:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=awSfcUHbqFg+RotIWqRF5bpg8mRrizeRydK8I6Ak06E=; b=cbW4ej95gp2ncbP0rgdHd2NNhCSLuASow7W8TUKJoZcnuBou438WF0wPe3p5xUewo3 WV4voDBV6waLBHfIfmbG332+heQdbAi+Sx9I59ImqvJGYY/ncP+0s9GVONkTwi38VjC4 kLK5CY/bPqhDL522cdYOjxmSBeMot/GCp5p79fO45A1pJ497ZcjNAr96Ey/kxaOqN58g 1rE3yJ1ff2qPZuGCUMJeAPNZtGqsY8gReSVDaRXQBjN/e1kuBQCMBHqlGR8Tr8QhwJBB WL4sCRICxE8vEF9XTq9g0ctFyM2RnJtYvqN59QukH+H6bVhO2EQcumQIvWQs1WbUcApy ZUfQ==
X-Received: by 10.180.93.8 with SMTP id cq8mr16538169wib.17.1406049535454; Tue, 22 Jul 2014 10:18:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.217.122.65 with HTTP; Tue, 22 Jul 2014 10:18:35 -0700 (PDT)
In-Reply-To: <CABkgnnXOm0325god-vL0K0PNf4df2vxs5hJLe4430=8Dq=b64g@mail.gmail.com>
References: <CAOW+2dsAyiKxAVCHBv-Qi2_2G4xOBE_xFiniUvhAO=Ft78TkDw@mail.gmail.com> <CABkgnnXOm0325god-vL0K0PNf4df2vxs5hJLe4430=8Dq=b64g@mail.gmail.com>
From: Bernard Aboba <bernard.aboba@gmail.com>
Date: Tue, 22 Jul 2014 13:18:35 -0400
Message-ID: <CAOW+2dsXVq+Yg=TfLdcjAjhxqZ_d9duEkOp9W4nHN7anZ+Zd8A@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="f46d043892b118f4e704fecb6b18"
Archived-At: http://mailarchive.ietf.org/arch/msg/rtcweb/NArWM1YdyBqrNnFivu1cBO6NrpQ
Cc: "rtcweb@ietf.org" <rtcweb@ietf.org>
Subject: Re: [rtcweb] security-arch: RTP and RTCP Key Management (mux and non-mux)
X-BeenThere: rtcweb@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Real-Time Communication in WEB-browsers working group list <rtcweb.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rtcweb/>
List-Post: <mailto:rtcweb@ietf.org>
List-Help: <mailto:rtcweb-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rtcweb>, <mailto:rtcweb-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 Jul 2014 17:18:58 -0000

Martin said:

"Yeah, keying multiple SRTP sessions from a single DTLS session could
(would) lead to key reuse if the different sessions use the same SSRC
values.  That's why 5764 says what it says."

[BA] Yes - but the question was about deriving SRTCP and SRTP keys from a
single DTLS session when RTP and RTCP are not multiplexed.   That wouldn't
result in key reuse.


On Tue, Jul 22, 2014 at 11:59 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On 21 July 2014 20:33, Bernard Aboba <bernard.aboba@gmail.com> wrote:
> > [BA] My question is whether WebRTC permits DTLS-SRTP sessions to share a
> > single DTLS session or not.
>
> Yeah, keying multiple SRTP sessions from a single DTLS session could
> (would) lead to key reuse if the different sessions use the same SSRC
> values.  That's why 5764 says what it says.
>
> Writing this down makes sense, though we need only lean on what 5764 says.
>