Re: [dispatch] Proposal for a new WG: Privacy Enhanced RTP Conferencing (PERC)

Paul Kyzivat <pkyzivat@alum.mit.edu> Tue, 14 April 2015 14:00 UTC

Return-Path: <prvs=3546cb706d=pkyzivat@alum.mit.edu>
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 A313C1A0277 for <dispatch@ietfa.amsl.com>; Tue, 14 Apr 2015 07:00:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level:
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 Uo1l9tDHUnOk for <dispatch@ietfa.amsl.com>; Tue, 14 Apr 2015 07:00:15 -0700 (PDT)
Received: from alum-mailsec-scanner-4.mit.edu (alum-mailsec-scanner-4.mit.edu [18.7.68.15]) by ietfa.amsl.com (Postfix) with ESMTP id 43EC91A00C2 for <dispatch@ietf.org>; Tue, 14 Apr 2015 07:00:01 -0700 (PDT)
X-AuditID: 1207440f-f792a6d000001284-28-552d1d60f01c
Received: from outgoing-alum.mit.edu (OUTGOING-ALUM.MIT.EDU [18.7.68.33]) by alum-mailsec-scanner-4.mit.edu (Symantec Messaging Gateway) with SMTP id 57.5A.04740.06D1D255; Tue, 14 Apr 2015 10:00:00 -0400 (EDT)
Received: from Paul-Kyzivats-MacBook-Pro.local (c-50-138-229-151.hsd1.ma.comcast.net [50.138.229.151]) (authenticated bits=0) (User authenticated as pkyzivat@ALUM.MIT.EDU) by outgoing-alum.mit.edu (8.13.8/8.12.4) with ESMTP id t3EDxxki024733 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for <dispatch@ietf.org>; Tue, 14 Apr 2015 10:00:00 -0400
Message-ID: <552D1D5E.1090504@alum.mit.edu>
Date: Tue, 14 Apr 2015 09:59:58 -0400
From: Paul Kyzivat <pkyzivat@alum.mit.edu>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: dispatch@ietf.org
References: <55134454.9050302@ericsson.com> <DF642B61-47ED-4F33-BE7F-3F70FF80B294@nostrum.com> <5527E01F.9040507@nostrum.com> <552B7F5C.9060107@ericsson.com> <552C5F01.3090207@nteczone.com>
In-Reply-To: <552C5F01.3090207@nteczone.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrMIsWRmVeSWpSXmKPExsUixO6iqJsgqxtqcOWHmsXSSQtYHRg9liz5 yRTAGMVtk5RYUhacmZ6nb5fAnXFk/STmgv1yFfdWdrA0MD6W6GLk5JAQMJFoPvCeEcIWk7hw bz1bFyMXh5DAZUaJlh+HGSGc/0wSrdtPsYBU8QpoS+yY28kMYrMIqEp0d29mArHZBLQk5hz6 D1YjKpAs0fLqFlS9oMTJmU/AbBEBUYn5Kxaxg9jCApESv5/2gdlCAnsZJda0uYHYnAI6El++ /gSbzyxgJjFv80MoW16ieets5gmM/LOQjJ2FpGwWkrIFjMyrGOUSc0pzdXMTM3OKU5N1i5MT 8/JSi3RN9HIzS/RSU0o3MUICkH8HY9d6mUOMAhyMSjy8J3x0QoVYE8uKK3MPMUpyMCmJ8lqy 6YYK8SXlp1RmJBZnxBeV5qQWH2KU4GBWEuE9wA+U401JrKxKLcqHSUlzsCiJ86ovUfcTEkhP LEnNTk0tSC2CycpwcChJ8J6XBmoULEpNT61Iy8wpQUgzcXCCDOeSEilOzUtJLUosLcmIB8Vk fDEwKkFSPEB7j4C08xYXJOYCRSFaTzEqSolDJARAEhmleXBjYWnlFaM40JfCvL9BqniAKQmu +xXQYCagwVkqWiCDSxIRUlINjOFCcXvf3e7+x/1YPbEyaGvSDYtv5s4yp22N/q7+YaJ6U86y 43pV7IOX13VKnqjNnhax6JTuvkQ56cqmhe0Z33YyBDmHxrvmd/QWTy+X+ORVF3f8eLPll6V3 HV8YVS/6Yuh9eMJ95aAwDc7r5jPvd3va+LzZkzZVzjFX9oM6u5FZrP1UlpocJZbijERDLeai 4kQATzo63wYDAAA=
Archived-At: <http://mailarchive.ietf.org/arch/msg/dispatch/l6pZqp_xSj7NAThbXYgB9X-lKkI>
Subject: Re: [dispatch] Proposal for a new WG: Privacy Enhanced RTP Conferencing (PERC)
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: Tue, 14 Apr 2015 14:00:17 -0000

On 4/13/15 8:27 PM, Christian Groves wrote:
> Hello,
>
> Please see below [CNG].
>
> Regards, Christian
>>> What is the motivation for declaring any extensions to signalling
>>> systems out of scope? (Not saying I see any that need to be created, but
>>> I'm surprised that it's not something that the group might need to
>>> investigate rather than making that call at chartering time)?
>>>
>> My reasons is to keep this WG focused on what it actually needs to
>> produce and not get completely tied up in discussion of exactly how one
>> will integrate this into ones signalling system. So I know people want
>> this in WebRTC and SIP based conferences. I haven't heard anyone saying
>> CLUE, but that is likely. These integrations are quite different,
>> especially in what pieces you will trust when it comes to client
>> software. Thus, my view was that WG working with signalling systems is
>> the ones that should provide any necessary integration towards the
>> framework.
> [CNG] I don't see CLUE being a lot different from normal SIP based
> conferences apart from the RTP header issue raised by Paul K. All CLUE
> is really doing is providing metadata to endpoints to allow them to
> select media captures more intelligently. If an endpoint is using
> private media there may be some consideration of "how much" CLUE
> metadata to provide to a 3rd party switch.

You highlight an interesting point.

If the goal is for the participants to conference without trusting the 
intermediary that does the "switching", then they may also not trust 
that intermediary to see the clue metadata that describes the media and 
the participants. There might need to be a way for the advertisements by 
the endpoints to be encrypted, so that the intermediary can only collect 
them and pass them on to the other endpoints.

	Thanks,
	Paul

>> I do note that this consideration of integration is mentioned in this
>> paragraph under Non-Goals:
>>
>> "The WG is not chartered to extend any signaling system used to
>> establish the RTP based conferences. It will however, need to consider
>> in its architecture how the solution may integrate with these systems."
> [CNG] I think this is the important thing. Whilst the proposed WG may
> not actually do extensions, I think its important to consider how PERC
> will be integrated and this should be documented up front as part of the
> architecture. I think that will be an aid to further discussions.
>
>>
>> But, I guess one could be more explicit and require the WG to consider
>> how one integrate into WebRTC, SIP and CLUE so that the framework is
>> functional for these systems.
>>
>> When it comes to the key-management function, I think there exists an
>> assumption here. That is that signalling and its nodes can't be trusted,
>> only possible be used as a transport for key-management system
>> information. But that will require that the communication fails if
>> someone strips or modify such information.
>>
>> Does this help clarify the situation.
>>
>> 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
>
> _______________________________________________
> dispatch mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch