[Webpush] Spencer Dawkins' Yes on draft-ietf-webpush-encryption-08: (with COMMENT)

Spencer Dawkins <spencerdawkins.ietf@gmail.com> Tue, 15 August 2017 16:15 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: webpush@ietf.org
Delivered-To: webpush@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8F6EB1320BD; Tue, 15 Aug 2017 09:15:22 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Spencer Dawkins <spencerdawkins.ietf@gmail.com>
To: "The IESG" <iesg@ietf.org>
Cc: draft-ietf-webpush-encryption@ietf.org, Phil Sorber <sorber@apache.org>, webpush-chairs@ietf.org, sorber@apache.org, webpush@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.58.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <150281372252.21061.13568867134437858167.idtracker@ietfa.amsl.com>
Date: Tue, 15 Aug 2017 09:15:22 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/GbI3lrviyYfO5BoIVtQ8W4DaDJg>
Subject: [Webpush] Spencer Dawkins' Yes on draft-ietf-webpush-encryption-08: (with COMMENT)
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Discussion of potential IETF work on a web push protocol <webpush.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/webpush>, <mailto:webpush-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/webpush/>
List-Post: <mailto:webpush@ietf.org>
List-Help: <mailto:webpush-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/webpush>, <mailto:webpush-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Aug 2017 16:15:22 -0000

Spencer Dawkins has entered the following ballot position for
draft-ietf-webpush-encryption-08: 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-webpush-encryption/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

This is really well written and clear. Thank you for that.

I found “for efficiency reasons” in this text

  For efficiency reasons, multiple users of Web Push often share a
   central agent that aggregates push functionality.

To be so broad that I wasn’t sure what you were telling the reader. Are there
any specific efficiencies that you could call out, so that we’d better
understand why central agents are used? And if that’s already written down
someplace, adding a pointer would be even better.

I’m curious about algorithm agility, but I’m not the person to ask that
question ...