Re: [Perc] Adam Roach's Yes on draft-ietf-perc-private-media-framework-10: (with COMMENT)

"Paul E. Jones" <paulej@packetizer.com> Tue, 14 May 2019 01:19 UTC

Return-Path: <paulej@packetizer.com>
X-Original-To: perc@ietfa.amsl.com
Delivered-To: perc@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EDF441200FF; Mon, 13 May 2019 18:19:16 -0700 (PDT)
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, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=packetizer.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 tsvfPRWQ6k6N; Mon, 13 May 2019 18:19:15 -0700 (PDT)
Received: from dublin.packetizer.com (dublin.packetizer.com [IPv6:2600:1f18:24d6:2e01:e842:9b2b:72a2:d2c6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id CA5C912008C; Mon, 13 May 2019 18:19:11 -0700 (PDT)
Received: from authuser (localhost [127.0.0.1])
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=packetizer.com; s=dublin; t=1557796749; bh=jXaLOcEv/LQq0wY26UfGhhbWCT8bIPwC82J0f77Ew8g=; h=From:To:Subject:Cc:Date:In-Reply-To:References:Reply-To; b=gcSLWdq/0CK7ORQbOF9X3iIL7WOKqQ+lerPPrivg5nSEXOEfzLMXVWJjVwBhHFa0b bURr/yyB7P95X0gTGHCJ259c2GVhKdznqq6mg0RcfSIjPVWcKuUUwL+GDV1mZQIT+J w63Gnqnnlv1xqaDILiqMXhyLxsFP0iuZDUJBSATA=
From: "Paul E. Jones" <paulej@packetizer.com>
To: Adam Roach <adam@nostrum.com>, The IESG <iesg@ietf.org>
Cc: draft-ietf-perc-private-media-framework@ietf.org, Nils Ohlmeier <nohlmeier@mozilla.com>, perc-chairs@ietf.org, nohlmeier@mozilla.com, perc@ietf.org
Date: Tue, 14 May 2019 01:19:03 +0000
Message-Id: <em099e7bfe-78c8-4e78-a05a-95d21a0fe979@sydney>
In-Reply-To: <155778680114.23612.8118531689244716936.idtracker@ietfa.amsl.com>
References: <155778680114.23612.8118531689244716936.idtracker@ietfa.amsl.com>
Reply-To: "Paul E. Jones" <paulej@packetizer.com>
User-Agent: eM_Client/7.2.34711.0
Mime-Version: 1.0
Content-Type: text/plain; format="flowed"; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/perc/WDZ_nz7JUPvkAxcqfZPF9xPnHxs>
Subject: Re: [Perc] Adam Roach's Yes on draft-ietf-perc-private-media-framework-10: (with COMMENT)
X-BeenThere: perc@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Privacy Enhanced RTP Conferencing <perc.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/perc>, <mailto:perc-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/perc/>
List-Post: <mailto:perc@ietf.org>
List-Help: <mailto:perc-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/perc>, <mailto:perc-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 May 2019 01:19:17 -0000

Thanks, Adam.  All good comments that I've made locally.  The changes 
will appear in the next revision.

Note that section 6.5 also has keys in a different order.  Since that 
deals with multiple HBH keys, I'm not sure that it makes sense to 
re-order the table, since I can't get a 1:1 mapping.  However, I'm happy 
to move anything around if you thinks it lends to readability.

Paul

------ Original Message ------
From: "Adam Roach via Datatracker" <noreply@ietf.org>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-perc-private-media-framework@ietf.org; "Nils Ohlmeier" 
<nohlmeier@mozilla.com>; perc-chairs@ietf.org; nohlmeier@mozilla.com; 
perc@ietf.org
Sent: 5/13/2019 6:33:21 PM
Subject: Adam Roach's Yes on draft-ietf-perc-private-media-framework-10: 
(with COMMENT)

>Adam Roach has entered the following ballot position for
>draft-ietf-perc-private-media-framework-10: Yes
>
>When responding, please keep the subject line intact and reply to all
>email addresses included in the To and CC lines. (Feel free to cut this
>introductory paragraph, however.)
>
>
>Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
>for more information about IESG DISCUSS and COMMENT positions.
>
>
>The document, along with other ballot positions, can be found here:
>https://datatracker.ietf.org/doc/draft-ietf-perc-private-media-framework/
>
>
>
>----------------------------------------------------------------------
>COMMENT:
>----------------------------------------------------------------------
>
>I'm glad to see this work finally ready for publication. As I've already
>given several rounds of input on this document, I have only minor
>editorial comments.
>---------------------------------------------------------------------------
>
>§2:
>
>>   This may
>>   include embedded user conferencing equipment or browsers on
>>   computers, media gateways, MCUs, media recording device and more that
>>   are in the trusted domain for a given deployment.
>
>Nit: "...media recording devices, and more..."
>                    pluralize _/  \_ add comma
>
>
>---------------------------------------------------------------------------
>
>§2:
>
>>   In the context of
>>   WebRTC...
>
>Please add an informative citation to https://www.w3.org/TR/webrtc/
>
>---------------------------------------------------------------------------
>
>
>§2:
>
>>   It operates according to the Selective
>>   Forwarding Middlebox RTP topologies [RFC7667] per the constraints
>>   defined by the PERC system, which includes, but not limited to,
>
>Nit: "...but is not limited to..."
>
>---------------------------------------------------------------------------
>
>§6.1:
>
>Nit: The keys are described in the sections that follow in the order
>they are typically acquired, but listed in a different order in Figure 4.
>This confused me for several moments. Consider reordering Figure 4 to match
>the order in which the keys are described.
>
>---------------------------------------------------------------------------
>
>