Re: [dispatch] Updated PERC Charter proposal

"Roni Even" <ron.even.tlv@gmail.com> Sun, 07 June 2015 17:59 UTC

Return-Path: <ron.even.tlv@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6097D1ACCE3 for <dispatch@ietfa.amsl.com>; Sun, 7 Jun 2015 10:59:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.7
X-Spam-Level:
X-Spam-Status: No, score=0.7 tagged_above=-999 required=5 tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=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 uYP3Ns_qPn_a for <dispatch@ietfa.amsl.com>; Sun, 7 Jun 2015 10:59:35 -0700 (PDT)
Received: from mail-wg0-x22f.google.com (mail-wg0-x22f.google.com [IPv6:2a00:1450:400c:c00::22f]) (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 275C91ACCE1 for <dispatch@ietf.org>; Sun, 7 Jun 2015 10:59:35 -0700 (PDT)
Received: by wgme6 with SMTP id e6so87376955wgm.2 for <dispatch@ietf.org>; Sun, 07 Jun 2015 10:59:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-type:content-transfer-encoding:thread-index :content-language; bh=DV8MN15g6TtGel27NAwIdJftWNqfDbslmfodlJK8Y04=; b=x+l487G85ZDo6JMGHuOomiOOdK9pHa2Wh2Mhu03ikiSl/K13u7XG9JsSJB1cve/3PG jvlb/Tv0JxBxXyzQCfWpW5wg83jnbSJS7daKyPYuuLhth8ERwniZbxIMZOBRjC2ZzCKZ C9MEqp8wP42LeTX0KFjgGKltgjbu+0KhSzuBp7nxlpuPbLfTYuxsYU7MsEKqsZSj58Zb VWiaBRBc2o8aSx4Gan20YlGvXrIoui3JkpjcOfg3TLxqNP7aUaf8cGbaz3DlrLiQWzH/ alD/eBfWxzWRpZlyGbSTvphmGxADNKo0UQZ3IwJIRGNl037CzFbS5Me4DcQ87z1DLgbP Ar9A==
X-Received: by 10.194.5.74 with SMTP id q10mr23748405wjq.27.1433699973856; Sun, 07 Jun 2015 10:59:33 -0700 (PDT)
Received: from RoniE (bzq-79-178-33-123.red.bezeqint.net. [79.178.33.123]) by mx.google.com with ESMTPSA id q4sm471577wja.24.2015.06.07.10.59.31 (version=TLSv1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 07 Jun 2015 10:59:32 -0700 (PDT)
From: Roni Even <ron.even.tlv@gmail.com>
To: 'Magnus Westerlund' <magnus.westerlund@ericsson.com>, "'Hutton, Andrew'" <andrew.hutton@unify.com>, "'Ram Mohan R (rmohanr)'" <rmohanr@cisco.com>
References: <CAHBDyN6BeyL-wh_=t7jN+tfhTTnZK0uTBra-F7MR11x9eFkGpg@mail.gmail.com> <D188F24E.14D48%goran.ap.eriksson@ericsson.com> <55683230.3020600@ericsson.com> <CAHBDyN68U=KiyM8aTzbmmFzN9cZJ_MgZs00VPCODyufMn=JpUA@mail.gmail.com> <556C2A44.8010805@ericsson.com> <D193CBFB.32759%rmohanr@cisco.com> <CABcZeBMGUG0A8ypCz2kF8hqfsKemXK4CX8ujLFOi2HjGWunJ9g@mail.gmail.com> <556DDC0C.3010107@andyet.net> <CABcZeBPtc-Wp=4WSc_NXCZM+SSY6o0eFDbnPE+zCLTB_LY7PvQ@mail.gmail.com> <556DF837.8050704@alum.mit.edu>, <D1946A1E.32827%rmohanr@cisco.com> <A634ECAF-9D68-41B7-85C6-F521F5BC821B@MRS> <556EFA0E.8050408@ericsson.com>
In-Reply-To: <556EFA0E.8050408@ericsson.com>
Date: Sun, 07 Jun 2015 20:59:24 +0300
Message-ID: <0b9601d0a14b$b2374490$16a5cdb0$@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
X-Mailer: Microsoft Outlook 14.0
Thread-Index: AQMeczP7p56zGI9386mjnB7ayVQMqQMrehJXAnvFbc0CR27rYgKr26SIAeyhdVIBb+KmngIamlaNAobT3r8B/JK9fAGtG1EQAYQ0ClYB6V2rt5o4LW6Q
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/5wlZp5GhhVmAweRuLXVCCz5N7Qs>
Cc: dispatch@ietf.org
Subject: Re: [dispatch] Updated PERC Charter proposal
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 07 Jun 2015 17:59:37 -0000

Hi,
My personal view is that if there is a requirement to record a multipoint
conference as specified in section 3.1.5 of RFC7245, you should not use a
PERC conferencing server for conferencing. 

Magnus two cases are correct but will not supply a good recording solution.

My view is that the recorded content should be managed by the conference
server (it will be the SRC as defined in SIPREC)  and not by a conference
participants, so in the first case where the recorder is a participant it
will not have a full view of the conference but will get what the PERC
server sends it as a regular participant invited by another participant
(e.g. not aware of side conference or get only part all the media streams in
the conference). The PERC server cannot define the recorder as a special
user since this will contradict the requirement that it is not trusted to
render the media.
In the second case, if the PERC server send the media to the recorder
encrypted this phase will work but why should the recorder get the keys from
the KMF if the decision to send the media to it was done by the non-trusted
PERC server.

Roni Even 

> -----Original Message-----
> From: dispatch [mailto:dispatch-bounces@ietf.org] On Behalf Of Magnus
> Westerlund
> Sent: 03 June, 2015 3:59 PM
> To: Hutton, Andrew; Ram Mohan R (rmohanr)
> Cc: dispatch@ietf.org
> Subject: Re: [dispatch] Updated PERC Charter proposal
> 
> Hutton, Andrew skrev den 2015-06-03 10:42:
> > I agree there is some value in exploring the recording use case it is
> > one of the first questions everybody asks when discussing PERC.
> 
>  From my perspective there are two ways of doing recording of media
content
> in PERC.
> 
> 1. Invite the recorder as a full fledged authenticated session participant
that
> use the normal way of getting the keys to the media as any other endpoint.
> 
> 2. The recorder only stores the encrypted media content, thus being a
semi-
> trusted entity to that are allowed to get a copy or be integrated into the
central
> forwarders. At the time one wants to access the recorded content one will
have
> to request the relevant keys from the key-management function, that will
also
> have to have stored the relevant group keys for the session to enable
> decryption.
> 
> I would claim that the second one is the securer, and enables better
tracking of
> who access recordings of a secured conference.
> 
> >
> > Hope we are allowed to consider this.
> 
> The charter talks about informing and coordinating with SIPREC. This to
have
> an exchange about the possibilities. However, it is not a work item of the
PERC
> WG to specify a solution for recording. I would expect any technical work
on
> solving PERC recording would need to be chartered in the most relevant WG.
I
> think the ones interested in recording should be active in the WG work to
> ensure that the developed solution do support recording. If there are
> contention between the goals, then we will need to have a serious
discussion.
> But, remember that we have clear goals of ensuring end to end security,
thus
> compromises to the security model to fit recording will be unlikely to be
> accepted.
> 
> Cheers
> 
> Magnus Westerlund
> 
> ----------------------------------------------------------------------
> Services, Media and Network features, Ericsson Research EAB/TXM
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Färögatan 6                 | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
> 
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch