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

Suhas Nandakumar <suhasietf@gmail.com> Thu, 25 April 2019 04:36 UTC

Return-Path: <suhasietf@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 39BF6120189 for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 21:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.018
X-Spam-Level:
X-Spam-Status: No, score=-1.018 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, HTML_FONT_FACE_BAD=0.981, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no 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 QnwLhKIedO4Z for <ietf@ietfa.amsl.com>; Wed, 24 Apr 2019 21:36:23 -0700 (PDT)
Received: from mail-vs1-xe29.google.com (mail-vs1-xe29.google.com [IPv6:2607:f8b0:4864:20::e29]) (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 1A32412017F for <ietf@ietf.org>; Wed, 24 Apr 2019 21:36:23 -0700 (PDT)
Received: by mail-vs1-xe29.google.com with SMTP id g187so11729139vsc.8 for <ietf@ietf.org>; Wed, 24 Apr 2019 21:36:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=K8G4/MYdrNcArt7aq5pGrwZWx/SLyDMug0h9TRo0Lh8=; b=McdFf+/gJo4yPklC59/qLYplib5rhVzKZ8iJcDU3CAdIp0KPBXIStAKBfY2qJjiTqb eEtMxTBi/X+IhFWS+3z8w9O2voJanp/JDj2eYrPu2tpJEuojk/fB74dh3emArrGSkwss y5IG49ctryxEZKYGAg0al74B7kusae+BoRFNBeMaGZwFMYDiatZbpWZ6KIZAiJ3xN3zV yA8NVhJxaIhXCg6V3jqLSPFgzoV6yJEPjGWMMQ+9ZKJjf+k7a7Z2aX388lgvrmew+NYl pHOQuTyU0m4kCKiMBpCmjCLUq7pbU3tmIPeQv/9SWjNqNXjnsc4mMizHcj7NJzdQQZBS zH/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=K8G4/MYdrNcArt7aq5pGrwZWx/SLyDMug0h9TRo0Lh8=; b=pUm+cdMG6vEeqlGGZM8763zeiOlpv2mojrsiccjww+K/LKjpfrRWBB1MpzBMv74/e5 RPnaJPUs9NmNz8KyBQ/QiO19uJfjBfndDB42dMvHE5vzEFxrDTfj6Pq4DdQNnQAVtdS3 7UI36L4uGxbUW8Md0LbGLF+rbKSkWWtWx0JsTiCTusP1gfdiM7QaK5VKIKh5f1sGIV+6 tJQR1Y7LopxN1Gc6WVwPlppCJh0fJKrEupTq1mU10ard8vY6QRH9QLSrUZRWm6vGZMem Y0C/RRPhAfi/3h0dX0aDa20gnPVZOBqSNxTo+8LwiPXQhftVfDUONEv/pSwr+BfhJP4c X1Ew==
X-Gm-Message-State: APjAAAUMR4SSxvU/9gaJxcmROHXTUNL786/HqEPHGby+zkjPIVfee9Fl QxZx6VPA6C0LEdzEbvu29bmnZzJEM2DlX4+aQ6wu7K2uH2U=
X-Google-Smtp-Source: APXvYqxmIejLkvm8GZyn1pRzRWQiuET9DFf7kNSAFFnLtCXchNE6QlZ0iFUTzCv5W54joth/xC/h5P5nV0DKkxwNiqM=
X-Received: by 2002:a67:76d6:: with SMTP id r205mr18037133vsc.26.1556166981707; Wed, 24 Apr 2019 21:36:21 -0700 (PDT)
MIME-Version: 1.0
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> <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> <CAPvvaaLOporQmn7XfPzR9V=j3qxDj1+95EnT22=JZ+DUjPjNrQ@mail.gmail.com> <CACtMSQXJg_W9gHDWoMgnQ5zPZMHL2Lmc8TL88gtKYJMAe4Swog@mail.gmail.com>
In-Reply-To: <CACtMSQXJg_W9gHDWoMgnQ5zPZMHL2Lmc8TL88gtKYJMAe4Swog@mail.gmail.com>
From: Suhas Nandakumar <suhasietf@gmail.com>
Date: Wed, 24 Apr 2019 21:36:09 -0700
Message-ID: <CAMRcRGRbPir2BVw5GOwh=382YSbvL726RgRFpDuSPtFxJrm2tg@mail.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: ietf@ietf.org
Cc: Ben Campbell <ben@nostrum.com>, Alexey Melnikov <aamelnikov@fastmail.fm>, Adam Roach <adam@nostrum.com>
Content-Type: multipart/alternative; boundary="00000000000027ef080587535c2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/CWhyuXkJ-1BbkvWaQDl1oy1eoGo>
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, 25 Apr 2019 04:36:25 -0000

Considering the concerns raised on this thread, the chairs and ADs
discussed options keeping in mind PERC's scope, historical context on these
concerns and context from this thread. We converged on following as the
decision summary on how we want to proceed.

"Some objections were raised in the working group, and re-raised during the
first IETF LC, proposing that the encryption applied by PERC should be
split so that in the WebRTC case, E2E keys could be supplied by someone
other than the browser. It became clear in both WG discussions and post-LC
discussions involving the ADs that this would be counter to the WebRTC
security model, which is required in the PERC charter. So any work to
address these concerns would be future work, and not blocking on the
current documents. "

Furthermore, there are discussions going on in the W3C WebRTC NV usecases
for enabling secure conferencing (PERC based or otherwise here:
http://lists.w3.org/Archives/Public/public-webrtc/2019Apr/0013.html#start13
).

Regards
PERC Chairs




On Thu, Feb 14, 2019 at 8:27 PM Alexandre GOUAILLARD <
Alex.GOUAILLARD@cosmosoftware.io> wrote:

> I do not agree with everything culled say, but still,
> I wanted to say something for his defence on his point where i think he is
> being given credits for my mistake.
>
> You had discussions with people. I was not an active part of them. You put
>> my name on a slide of "supporters" and you were about to present to that to
>> the WG. I saw that and asked you to remove my name. Please do not imply
>> sudden whimsical changes of positions.
>>
>
> I am the culprit for bringing your name in at IETF 99. Sergio and I spoke
> with cullen to try to find a consensus, and we brought to the table what we
> though was important for you. As you clearly stated later, you had not
> asked us to do that, so it s my bad. When I thought we found a consensus, i
> kindly asked cullen tot put your name before presenting it, to show we had
> also included your concerns in our discussion and teh corresponding
> solution.
>
> this one is on me, and I apologise, again, for it.
>
> _______________________________________________
> Perc mailing list
> Perc@ietf.org
> https://www.ietf.org/mailman/listinfo/perc
>