IETF Logo Mail Archive

Re: [Perc] Question on diet Design?

"Paul E. Jones" <paulej@packetizer.com> Thu, 23 March 2017 04:42 UTC

Return-Path: <paulej@packetizer.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 E151E12943D for <perc@ietfa.amsl.com>; Wed, 22 Mar 2017 21:42:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.002
X-Spam-Level:
X-Spam-Status: No, score=-2.002 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.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 zsWUb2YfnA92 for <perc@ietfa.amsl.com>; Wed, 22 Mar 2017 21:42:09 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [75.101.130.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 67FC112943A for <perc@ietf.org>; Wed, 22 Mar 2017 21:42:09 -0700 (PDT)
Received: from [192.168.1.20] (cpe-098-122-167-029.nc.res.rr.com [98.122.167.29] (may be forged)) (authenticated bits=0) by dublin.packetizer.com (8.15.2/8.15.2) with ESMTPSA id v2N4g7T8005873 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 23 Mar 2017 00:42:08 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1490244128; bh=Cf+TVcagLwwvMkcxdDdjG+h3uAexG6ffFMtswQzUQoc=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=KqzYZ5cV+Es+w1xGK2WGG/62f83we/p+dcmgP1jLX//bttYZLZyA7mQAxmQgNV6GC SBIyuLUyCIJOEfB7VeFt/Lwk8aIVAm4hzdRNiC+x9De6yqyWvM0/b6Wqb8wqTEt/R0 XyfIXS1Dccd/QJl3tAqlHo7cH/W30i5F5xaBhURA=
From: "Paul E. Jones" <paulej@packetizer.com>
To: Eric Rescorla <ekr@rtfm.com>
Cc: perc@ietf.org
Date: Thu, 23 Mar 2017 04:42:07 +0000
Message-Id: <emb912fdf7-1123-46c4-ba3d-8ff4d73e87b2@sydney>
In-Reply-To: <CABcZeBPSATAonu87OaJuUX1QWkuPufi=HpKQQ5AZZB6ZWP759A@mail.gmail.com>
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>
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: eM_Client/7.0.28492.0
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="------=_MB310DFA81-53F7-4AF1-8033-B0CB196EA413"
X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.6.1 (dublin.packetizer.com [10.165.122.250]); Thu, 23 Mar 2017 00:42:08 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/Holyq6GWPaWY7-IBdIC79lAS7zA>
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 04:42:11 -0000

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

v2.23.0 | Report a Bug | By Email