Re: [dispatch] Updated PERC Charter proposal

"Ram Mohan R (rmohanr)" <rmohanr@cisco.com> Wed, 03 June 2015 15:27 UTC

Return-Path: <rmohanr@cisco.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 5A2F31A8F49 for <dispatch@ietfa.amsl.com>; Wed, 3 Jun 2015 08:27:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.511
X-Spam-Level:
X-Spam-Status: No, score=-14.511 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_DKIM_WL=-7.5] 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 1iZZPKNkBMB9 for <dispatch@ietfa.amsl.com>; Wed, 3 Jun 2015 08:27:23 -0700 (PDT)
Received: from alln-iport-4.cisco.com (alln-iport-4.cisco.com [173.37.142.91]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C23E51A3BA1 for <dispatch@ietf.org>; Wed, 3 Jun 2015 08:27:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=2935; q=dns/txt; s=iport; t=1433345243; x=1434554843; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=6Nwz2YXAObu+WxA/HcKzgzA3YI1//2NK7p1Zky6O67o=; b=cMM/PaO7RjsbiMqfNYdErXDPt35ytZysSe44/+ZueKvJAtf4rYP1mswG liJBc5uOyWwqzeVsd2yxe/mdzZYN4o8hL+XF8g7rlNX0yWqpIxPIudMjU NpTtHsARoi0KBnM7vBb52vVqmmreCTxiNeY5Pg0hGJvItvrvDlNkiAxZt Y=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0ApBQDyG29V/5xdJa1bgxCBMgbGJwICAoE/OxEBAQEBAQEBgQqEIgEBAQQMXB0CAgIBCBEDAQIoBxsXFAkIAgQBEhuIEttFAQEBAQEBAQEBAQEBAQEBAQEbBIs/hQ0GhCcFhmyFIoRHgj+LH5dEJGGDF2+BRoEBAQEB
X-IronPort-AV: E=Sophos;i="5.13,547,1427760000"; d="scan'208";a="156068550"
Received: from rcdn-core-5.cisco.com ([173.37.93.156]) by alln-iport-4.cisco.com with ESMTP; 03 Jun 2015 15:27:22 +0000
Received: from xhc-aln-x12.cisco.com (xhc-aln-x12.cisco.com [173.36.12.86]) by rcdn-core-5.cisco.com (8.14.5/8.14.5) with ESMTP id t53FRMaL030127 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 3 Jun 2015 15:27:22 GMT
Received: from xmb-aln-x05.cisco.com ([169.254.11.78]) by xhc-aln-x12.cisco.com ([173.36.12.86]) with mapi id 14.03.0195.001; Wed, 3 Jun 2015 10:27:22 -0500
From: "Ram Mohan R (rmohanr)" <rmohanr@cisco.com>
To: Magnus Westerlund <magnus.westerlund@ericsson.com>, "Hutton, Andrew" <andrew.hutton@unify.com>, "dispatch@ietf.org" <dispatch@ietf.org>
Thread-Topic: [dispatch] Updated PERC Charter proposal
Thread-Index: AQHQnhHIkh59aGNCBkW9506d2tXpsg==
Date: Wed, 03 Jun 2015 15:27:21 +0000
Message-ID: <D1950355.32D1F%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>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.4.7.141117
x-originating-ip: [10.65.59.238]
Content-Type: text/plain; charset="iso-8859-1"
Content-ID: <FD0428C23BF51547A5ABAAF91EEC946E@emea.cisco.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/-LguHCLlrbMrqeIu9WD6MwqtQRY>
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: Wed, 03 Jun 2015 15:27:25 -0000

Hi Magnus,

-----Original Message-----
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Date: Wednesday, 3 June 2015 6:28 pm
To: "Hutton, Andrew" <andrew.hutton@unify.com>, Cisco Employee
<rmohanr@cisco.com>
Cc: "dispatch@ietf.org" <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.

This is some thing similar to what I was visualising as well. The recorder
and KMS needs interactions to get access to recordings.

>
>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 am not too worried about where it is done as long as we are doing it.
Perhaps SIPREC may be a place given that it was already doing recording
for existing models.


>I think the ones interested in recording should be
>active in the WG work to ensure that the developed solution do support
>recording. 

Agree.

Regards,
Ram
>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
>----------------------------------------------------------------------
>