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

Bernard Aboba <bernard.aboba@gmail.com> Wed, 13 February 2019 15:41 UTC

Return-Path: <bernard.aboba@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 529C9129441; Wed, 13 Feb 2019 07:41:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 RQS3ug5lLkvg; Wed, 13 Feb 2019 07:41:27 -0800 (PST)
Received: from mail-pf1-x42a.google.com (mail-pf1-x42a.google.com [IPv6:2607:f8b0:4864:20::42a]) (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 8A5B3126C7E; Wed, 13 Feb 2019 07:41:27 -0800 (PST)
Received: by mail-pf1-x42a.google.com with SMTP id f132so1307189pfa.6; Wed, 13 Feb 2019 07:41:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JMwo1BqN+JoO4dAyrwxU4GdPVoerYKLjVU88+rG9xcM=; b=CsYf2LQ6xOFSuTcEOoqW76Q6IVYnwYgTDqIBpV+8AQ2g2u1b3WvRcgE9p3QSBkYwu1 172IE326P7hpv3aN19qlOw5wrjY13yMj/Ezq9Hbgtsd4P3wGEJvbSm63f6f8rSCFSkEh VDrxYpNMTBY+EVJdGdsMpIGU1soX9SMX3mhohS2RHvQVB7YjYyhLVQySYBoTjp8d8ljO BexfDTYqXkLLVrT/9x6B7tS6Osr7s1qjU/kdQlsO6KkM84O/7dzsh4oG/1qsdrLLmoIk LLM0OOnynFUHimzOqmUvrDVBWXMUFlid5dh0AtCp3YWapkgHHdIeKftlM16WlNt2lEE/ KNZg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=JMwo1BqN+JoO4dAyrwxU4GdPVoerYKLjVU88+rG9xcM=; b=EhjQmFU0SiuxevYMkrLC2h1aCYK9U9ftyhWwYKH7uYDKcW31kyNqIc/EX4BLkWIgBD GEfr2TUdAXpHtC+nn5RURE7kwXx5LujxVUB3gb3yN0U+3KCZJLSNo0yei1ASKV1rFY14 9wpdJX4lHl7HNUhWrk7WTA9Gnoht6yr2h2iKAW8Do18Mne/lln6MYINn3lCN/ilwZU+X iA4CUPgVxOaLeHgCKtS1ZsuTRlliRYL5lZ3shJfAe+k5TJQoN9EChKxC3kLqbPikoflF Sw1GtIZqRSOlagiZCKaviJNuzBZZoby0lbgvvZNyh1ffKDSmArxt7awYaJ8DTEQSWSot 76BQ==
X-Gm-Message-State: AHQUAuZDFyWSGxlyE+LgWxDfdOZNXJSieRaVnoEN+KMpXghsW9J0rrr/ zpBRh16z4ErncJEC90ajF2Y=
X-Google-Smtp-Source: AHgI3IYuL2iA4tjOMtEii7GZJMtmpkHHOvMazXVy8cIEHgOBb+yTjgKSxtzT9A7f3g582GxuF8x5fw==
X-Received: by 2002:a63:a:: with SMTP id 10mr990755pga.121.1550072486500; Wed, 13 Feb 2019 07:41:26 -0800 (PST)
Received: from [192.168.1.104] (c-98-225-39-241.hsd1.wa.comcast.net. [98.225.39.241]) by smtp.gmail.com with ESMTPSA id m67sm28772602pfm.73.2019.02.13.07.41.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Feb 2019 07:41:25 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (1.0)
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
From: Bernard Aboba <bernard.aboba@gmail.com>
X-Mailer: iPhone Mail (16D57)
In-Reply-To: <9c4149c0-184b-5ee9-e0a4-2b41420d3279@gmail.com>
Date: Wed, 13 Feb 2019 07:41:24 -0800
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>
Content-Transfer-Encoding: quoted-printable
Message-Id: <632D3A5E-0F15-40D8-B6F8-1307ECDCDBC9@gmail.com>
References: <154889546931.10496.2408974719921724953.idtracker@ietfa.amsl.com> <CAL02cgSip2cLr8a1+zfK2cg+n8gqUMc9CKPmb7mWd2iLSiRf-g@mail.gmail.com> <8e40d0db-cacb-db93-f2fe-db5b4a7cf7cf@gmail.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>
To: Sergio Garcia Murillo <sergio.garcia.murillo@gmail.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/_SBtE8gbZQSVUssXp3yidSRFuzQ>
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 15:41:29 -0000

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? Does it avoid the problems with FEC/RTX processing and Triple protection? Has it been deployed?

v2.23.0 | Report a Bug | By Email