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> Thu, 14 February 2019 23:37 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 C42F8131096; Thu, 14 Feb 2019 15:37:46 -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 aaPyDt4K8W-C; Thu, 14 Feb 2019 15:37:44 -0800 (PST)
Received: from mail-wr1-x432.google.com (mail-wr1-x432.google.com [IPv6:2a00:1450:4864:20::432]) (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 560FA128B36; Thu, 14 Feb 2019 15:37:44 -0800 (PST)
Received: by mail-wr1-x432.google.com with SMTP id x10so8389312wrs.8; Thu, 14 Feb 2019 15:37:44 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=oLk1HBShX515oCelejvyfL15VvP3ymgaPty3R4FErdI=; b=OEVjoe4tzzpCm4COUnMhXjUESdxdfuaJMyQXqjh5ZN8gBBVJdL5d83g4atRxTE+DLA YareadSDktD56V5fqT+wiUsgRWYKfmNl17bmjqBcaJblEEooeXI60bTBZGIDmelj27dh GWA0zl0Et1TERqEBEZS5svXG+MCo+OmsI715cNuLFtyRT1reaEVDFdG/shkiCGvKVM+l i/ppuYL/k8XsWf/zV8lVLxlTendznSS0jGW0X4XDGocXtdRB0GHMRc8akvV3BaArjpWQ TeIbjJz/LZxdrZ/ew51Q2Cd0i0HT63bt+c5LmewJVVWkJyNyhEOhstZ4J0H5C/BphnBS 8/yA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=oLk1HBShX515oCelejvyfL15VvP3ymgaPty3R4FErdI=; b=AUpBQQucXPnXUlfYzlOwiWdL5xCrWJutNpoT5gYBk3KmCJKqmo1HJ4e69005EokRIL 4zzDcdalNwlmxtVTB7BW4fBdQxTxTjaipDPakMUB/aRTu5EYPTRRDfT2wELrzRV/p841 8/86xLnKLEokchkWnsdr5zkz9tgjiFvKIbRLgx7BG5r1dj8UEHopU7Ea4rplfx3chU+L S3aLM7ZhaCfoQuMQF51h3oiI4IGpCtfiQJczq1ulX9G+1pawu5Czd6QoccWPZd+ajYht De78i2n7QKFnMijXNmeYlZ+kbKDsVXrmHWsHpgE0vqAAviEX5bPNVA25f+LnUBhpkfpw 5jvQ==
X-Gm-Message-State: AHQUAuaUMakHATOdmwaz34SQVd0cJEtTYm7P+pUZ9ksUUCK/5goRX2QX ZJN4DAwK0gPrW5uiKwEOwfE=
X-Google-Smtp-Source: AHgI3IYSYbZDkFk5aNUjzk4txfjJm77T9fhh0EeggY7k7a4Sp2wBg059lCieYHRVQPO41wYthjEmNw==
X-Received: by 2002:adf:ee4d:: with SMTP id w13mr4674608wro.16.1550187462801; Thu, 14 Feb 2019 15:37:42 -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 b3sm9210991wme.27.2019.02.14.15.37.41 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 14 Feb 2019 15:37:42 -0800 (PST)
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: Cullen Jennings <fluffy@iii.ca>, Ben Campbell <ben@nostrum.com>
Cc: Nils Ohlmeier <nohlmeier@mozilla.com>, IETF Crazy <ietf@ietf.org>, Emad Omara <emadomara@google.com>, Emil Ivov <emcho@jitsi.org>, perc@ietf.org, Harald Alvestrand <hta@google.com>, Alexandre GOUAILLARD <alex.gouaillard@cosmosoftware.io>, Lorenzo Miniero <lorenzo@meetecho.com>, Bernard Aboba <bernard.aboba@gmail.com>
References: <154889546931.10496.2408974719921724953.idtracker@ietfa.amsl.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> <37143A53-81C3-4391-998E-D7F2AD1F409C@nostrum.com> <417923aa-8771-863e-ee12-4107f674d918@gmail.com> <4CBF52C0-1D9F-4576-85B6-4F24F59CB3E6@nostrum.com> <88F12D70-CE7F-48FB-9F32-7827091E3768@iii.ca>
From: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Message-ID: <e21e9924-3ff2-08d2-ed43-6398e9d9d471@gmail.com>
Date: Fri, 15 Feb 2019 00:42:28 +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: <88F12D70-CE7F-48FB-9F32-7827091E3768@iii.ca>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/PrtJBF3tA_UI1PIrsCM8Aa1zkAY>
X-Mailman-Approved-At: Sun, 17 Feb 2019 19:46:41 -0800
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: Thu, 14 Feb 2019 23:37:47 -0000

On 15/02/2019 0:05, Cullen Jennings wrote:
> "JS access to media keys" is exactly the heart of the issue of the 
> SDES keying of SRTP vs. DTLS keying of SRTP - the WebRTC group had a 
> huge discussion on that topic.  This discussion finalized in a large 
> meeting at IETF-87 that including many of the SIP, WebRTC, and 
> Security folks at IETF. The consensus was extremely strong for not 
> doing the SDES solution that put the keys in JS. ( See 
> https://www.ietf.org/proceedings/87/minutes/minutes-87-rtcweb )
>
The DTLS key has never been proposed to be handled by js in anyway, so 
not sure how it breaks any previous consensus. A different history is 
that PERC has arbitrarily decided to integrate together the WebRTC DTLS 
key and the new end-to-end encryption key into a single one.

Best regards

Sergio

v2.23.0 | Report a Bug | By Email