Re: [Perc] Question on diet Design?

Eric Rescorla <ekr@rtfm.com> Thu, 23 March 2017 11:13 UTC

Return-Path: <ekr@rtfm.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0CB8C131591 for <perc@ietfa.amsl.com>; Thu, 23 Mar 2017 04:13:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.com
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 0m_GBrnAu3TQ for <perc@ietfa.amsl.com>; Thu, 23 Mar 2017 04:13:33 -0700 (PDT)
Received: from mail-yw0-x234.google.com (mail-yw0-x234.google.com [IPv6:2607:f8b0:4002:c05::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 12CD813158C for <perc@ietf.org>; Thu, 23 Mar 2017 04:13:33 -0700 (PDT)
Received: by mail-yw0-x234.google.com with SMTP id p77so143792913ywg.1 for <perc@ietf.org>; Thu, 23 Mar 2017 04:13:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AXOHg7MQW/b1Jwl5GfWQ7jwblIdK9iSlcet/yq8E2EI=; b=dSQJhUGOZl7NWECI/b4175JLV9WyogFpmtkdc/ON2XFdS0xA9ekXJ2WO1/HyMpENjl TeaO/bJSfO2G9WcwpPbj613azPPgw95ng+xGGChzuq70HjH8/LFmPh5Xzv72dt3ancKl d5wutWGjHGdWS/NMEJhckMiwTuqOk5fIA7Rf3tb2h40oCjFrQpZlFHYUHouU9j77W/3O vy/+kxBgB+pVwAFtKosL097nxLfvMZ+SNzif6v/KEzZBPB4m10S2mjUZIPT6/pC7kraM euTZTvtm6UcSSIGAdZgvTrzGSWsLH85HXUnX2fxh/PSc54P2g0aNyNSI82M7j66kWM5P WJtg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AXOHg7MQW/b1Jwl5GfWQ7jwblIdK9iSlcet/yq8E2EI=; b=pvqqNCQF0TntJZSdxVdhtJELGIrWVcvKQw/uwTwsx1F4Qbh6np6Oe/gyqJ3BkF2pXo 9SYyxEdEzrjUGc+V1jno5T8D6vZmxCwjV82emdYia4DBtbEqyU1KQ9wqq8GQ0dSUbEKh HYb20i9f+4Ofc7A/eYMvKWbh2COk6XILbbLr6cohvnF9K2ZAse9QCLJO6JEvz/7NOXCs 8kWK3Xr6BGbhSVoKybKCSrFOKwoFXrUjQxrIgAL/cFTP5VBEeqrsNyvj9omrZ8VVUM6k 2wiYe8Vg/DWTv4FZqkofsxiZexmCSTj6/CN/LdFfZWyP4JBzyZF7EnQfqFzHwaPhHA9n pTPA==
X-Gm-Message-State: AFeK/H2klTkMgDUWHWM9snzAW5bUtwQluNYcOdgP6QWn7y47Pi2xNuiEnl43BCHq2dQmA2W+aLfi0BJ0eWeQng==
X-Received: by 10.37.115.201 with SMTP id o192mr1295041ybc.107.1490267612319; Thu, 23 Mar 2017 04:13:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.129.154.210 with HTTP; Thu, 23 Mar 2017 04:12:51 -0700 (PDT)
In-Reply-To: <emb912fdf7-1123-46c4-ba3d-8ff4d73e87b2@sydney>
References: <CABcZeBPbFJYyCBUGhtryn1Z6W9feLUiS-sVB+HM7UUUR3-ZbQg@mail.gmail.com> <em918d187a-1839-494c-a969-b298d03965d7@sydney> <CABcZeBNFSmM4VjKzKLmrTzTEMxke=gYzH7x9GuhPcv=gFqRvQQ@mail.gmail.com> <ema2355ca7-fc19-48f6-972e-7dd73ac7a9a9@sydney> <CABcZeBMXWoQ1jeDFGUU2maO3ehJ4Z9-o6_pckUaC_wbmNPPnGg@mail.gmail.com> <emba00a16e-6ca9-41ac-85ae-e53f6115c95c@sydney> <CABcZeBPSATAonu87OaJuUX1QWkuPufi=HpKQQ5AZZB6ZWP759A@mail.gmail.com> <emb912fdf7-1123-46c4-ba3d-8ff4d73e87b2@sydney>
From: Eric Rescorla <ekr@rtfm.com>
Date: Thu, 23 Mar 2017 04:12:51 -0700
Message-ID: <CABcZeBNFbpAKu-PkuB+zxxpduJStViJX=_xZD5s7R4ejCMx5FA@mail.gmail.com>
To: "Paul E. Jones" <paulej@packetizer.com>
Cc: perc@ietf.org
Content-Type: multipart/alternative; boundary="94eb2c097eb2a73260054b63f72e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/otgsgkFWo_sXXxqawzKnKssZFak>
Subject: Re: [Perc] Question on diet Design?
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 23 Mar 2017 11:13:35 -0000

It's part of the SRTP KDF.

-Ekr


On Wed, Mar 22, 2017 at 9:42 PM, Paul E. Jones <paulej@packetizer.com>
wrote:

> Eric,
>
> I think what you propose would work, but each stream from a given endpoint
>> would need to have a unique key since we do not want the any two media
>> flows using the same key. Thus, I think we'd need:
>>   KDF(K_g, ID || stream_id)
>>
>
> The SSRC addresses that, no?
>
>
> Yeah, SSRC is fine for that.  We just need to ensure it is a part of the
> KDF input.
>
> Paul
>