IETF Logo Mail Archive

Re: [Perc] Last Call: <draft-ietf-perc-private-media-framework-08.txt> (A Solution Framework for Private Media in Privacy Enhanced RTP Conferencing) to Proposed Standard

Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com> Wed, 13 February 2019 17:12 UTC

Return-Path: <sergio.garcia.murillo@gmail.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E6C40130DE9; Wed, 13 Feb 2019 09:12:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 juHU1o2xjzr8; Wed, 13 Feb 2019 09:12:30 -0800 (PST)
Received: from mail-wr1-x42f.google.com (mail-wr1-x42f.google.com [IPv6:2a00:1450:4864:20::42f]) (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 C137E1288BD; Wed, 13 Feb 2019 09:12:29 -0800 (PST)
Received: by mail-wr1-x42f.google.com with SMTP id r2so3368940wrv.10; Wed, 13 Feb 2019 09:12:29 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:subject:to:cc:references:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=th4S9HwI226H+6alob99/9x0DAfJak5O+hPh1C7TbhM=; b=YLrSGKj81skwFpjwm6zzbZMbOdI1nUW7/2yJFYoGHoW7DQVZr51aYaTfp9r/VaTbzk y9q3GsKs8ygfflokeSKDfMMCqlpKTj/wt4wbLCqDVE7ojNrV6yoUQXWUSYUytVzrkzD9 Olw/1ymAlSch/bTOuRkBsjy4bj10BXNH7ummktrkbjlVwo+BEypOT7fxsV1VhkSg80L+ wH+pec0Z5eIiX6wcwc0WjENvWlplzJ/A7g7i7o/ZqxvUUaTWoqVdwgxB3zYIy/RkbiN9 e4J7ofPkQm5tlHX5YlJanpyCUUAzyzwBH2OY4/2w6Uk4onXcc+wf0JiJM2uDL4ICQ4IP KRDA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:subject:to:cc:references:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=th4S9HwI226H+6alob99/9x0DAfJak5O+hPh1C7TbhM=; b=Fj/GAwPtH2KpXvwEtpQl1IT4wvFA5a5sfwqpH4vTFddryN6APBXDqI17nUPpabaAnu tBURaNE6Jo7Q4ApbHagZJOeeOCtkBY26SQ3/vUP3bz2N8G+Xsrd4UPAa0AnnNKvAbL0J skTQZzByjTVwkO/t3muRazkxN+LLOWkFGKPuPwy6gGqPnY5QpbAg7+HSHzKPkYK7fXQu 5qZaq3rpVXxnLpDknxZz7BxnYn1RSFdxE2kFSg94zAZvLAb9wmwYHwAdiZXDeSyzTUzr Y+sHoSSUiNITve3Q/ItVjGL9gEWVxlfRWS4QXJVsNsRfHJmOc7CBijV3qE5HArSKJ0oX fY2Q==
X-Gm-Message-State: AHQUAuaj4wgHRI88ebSMqI8x/2tu9DLpyWpZNw3zyl2bG80uo5KCj2kR fSoxcFfmfG2/ydaGNPS+Q1M9rijN
X-Google-Smtp-Source: AHgI3IZNwGdWcyBYTycVh8+uk1xcgc5w1Lp73sMTNsz6TW91Of96vSMXeGxNnDQhZOZrDWqNChI7sQ==
X-Received: by 2002:adf:eb85:: with SMTP id t5mr1162674wrn.157.1550077947910; Wed, 13 Feb 2019 09:12:27 -0800 (PST)
Received: from [192.168.0.11] (79.108.125.160.dyn.user.ono.com. [79.108.125.160]) by smtp.googlemail.com with ESMTPSA id n3sm8673477wmf.46.2019.02.13.09.12.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 09:12:27 -0800 (PST)
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Subject: Re: [Perc] Last Call: <draft-ietf-perc-private-media-framework-08.txt> (A Solution Framework for Private Media in Privacy Enhanced RTP Conferencing) to Proposed Standard
To: Bernard Aboba <bernard.aboba@gmail.com>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, IETF discussion list <ietf@ietf.org>, Emad Omara <emadomara@google.com>, Emil Ivov <emcho@jitsi.org>, perc@ietf.org, "hta@google.com" <hta@google.com>, Alexandre GOUAILLARD <alex.gouaillard@cosmosoftware.io>, Lorenzo Miniero <lorenzo@meetecho.com>
References: <154889546931.10496.2408974719921724953.idtracker@ietfa.amsl.com> <CAOW+2dtxnSYOPPWxodN633O=dPOQaUnu7eYvgUYkPYRt6iWbaw@mail.gmail.com> <CAPvvaaK_VUXvy2=1TBGfBWWYxiBdXBzuR=Y-rnAdJyg=M8OfQQ@mail.gmail.com> <5486C91C-48EA-4AA1-85EE-05A0B01C1E70@meetecho.com> <C6FEAEB9-CF8E-48AF-B03F-1406FF9CB303@cosmosoftware.io> <CAOW+2ducgj400pk3xPFAkRYxnYvqwhMsE9rOO0u9PgLpniaaRA@mail.gmail.com> <CAPvvaaLYFeNkZ4Pfdh4pa2btNW6EGZBnAOvXzVZ9egU8V-gBNQ@mail.gmail.com> <CAOW+2dvom822NgjF7OAa2A8YDeqZ+mbCqA=fUcq-Y49oFyGpsA@mail.gmail.com> <CAPvvaa+EzwgMXB_t7ZVTBgZH2y4=neUm1RymUNKnMV-6zyGPaQ@mail.gmail.com> <a74a8239-27dc-5704-096b-05cc5e02bd18@gmail.com> <543375ED-9A4F-452C-AE51-9499DAD5CEE0@gmail.com> <80a1f634-0888-c5e2-f6be-729d4cca3b28@cosmosoftware.io> <06d91175-b071-49fe-01cc-4a1323ad85f7@gmail.com> <91A16283-A392-4217-97E1-B04A5C8AD245@mozilla.com> <9c4149c0-184b-5ee9-e0a4-2b41420d3279@gmail.com> <632D3A5E-0F15-40D8-B6F8-1307ECDCDBC9@gmail.com>
Message-ID: <96e177cb-a407-bd41-767d-5f0951fb7ee8@gmail.com>
Date: Wed, 13 Feb 2019 18:17:12 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.0
MIME-Version: 1.0
In-Reply-To: <632D3A5E-0F15-40D8-B6F8-1307ECDCDBC9@gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/p9rxOMK4zrYX4DafAU3ObBaNAuk>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 13 Feb 2019 17:12:32 -0000

On 13/02/2019 16:41, Bernard Aboba wrote:
> On Feb 13, 2019, at 2:53 AM, Sergio Garcia Murillo<sergio.garcia.murillo@gmail.com>  wrote:
>> This liaison statement basically blows away any rough consensus from IETF 99 as the basis of my joint proposal was that it could be possible to proceed with the PERC lite proposal and that alternative keying mechanism could be studied without involving the PERC group.
> [BA] Is there documentation on the PERC-lite proposal?

The original proposal and slides can be found here:

https://docs.google.com/presentation/d/1cwwg36z8bZlgUaBifiuQU9vWhwx4fbbdIrlvQ77578M

https://www.dropbox.com/s/8qxielk88y1veol/draft-perc-lite.txt.pdf?dl=0

Also:

https://ieeexplore.ieee.org/document/8169749

https://ieeexplore.ieee.org/document/8169752


> Does it avoid the problems with FEC/RTX processing and Triple protection?

The information required to decrypt the outer payload is bundled withing 
the inner encrypted payload, so there is no issue with FEC/RTX, triple 
or ssrc rewriting. Only framemarking support is required.


> Has it been deployed?

As only frame marking is required, it is supported in Jitsi, Janus and 
Medooze SFUs. We have two deployments with PERC-Lite, one with VP8 and 
with Jitsi for Symphony and another one with VP9 SVC and Medooze. We are 
also working alternative per frame encryption methods for lower 
bandwidth overhead.


Best regards

Sergio

v2.23.0 | Report a Bug | By Email