Re: [Webpush] Ben Campbell's Yes on draft-ietf-webpush-encryption-08: (with COMMENT)

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 16 August 2017 13:01 UTC

Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F385913219C; Wed, 16 Aug 2017 06:01:44 -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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 AoRcDco-tLo9; Wed, 16 Aug 2017 06:01:42 -0700 (PDT)
Received: from mail-yw0-x229.google.com (mail-yw0-x229.google.com [IPv6:2607:f8b0:4002:c05::229]) (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 829691325E2; Wed, 16 Aug 2017 06:01:40 -0700 (PDT)
Received: by mail-yw0-x229.google.com with SMTP id l82so21933822ywc.2; Wed, 16 Aug 2017 06:01:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=vlEnseVe2t+MC/0+KTy0v9PfFaJFdE2+J4+bbM99eTA=; b=vfzgINVKBU6uFrygSbMz8lS3WopFyBVEEmf8wVBnjbpDmWXGqjnHLr3AWTbfUowKBu zhvX/DXCGeXcW6gZ3jrjU9TiVtNiQXXTP204e57abt7DmqM+MjlERxYhRCU1JdkxAruw MdiSIfY6ADbt6AZXPGuPMNZgxhdFbTu+WnV+VaivxNQ9OMnwb/Vd9bMC+EFD44Z6yoHT LvK7DHAGcRqwX3tBT7kglkH87Jmsz9ZUP+ckxGwVXWf4H0mdDQGt6XORNpJuNG2G1MRI fUzvX1kca3712v3990SnDv6gMo74Vr8rKuX/E08j3YSB8t/yeKYgEbBiVtVumHu5pdm8 uG9g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=vlEnseVe2t+MC/0+KTy0v9PfFaJFdE2+J4+bbM99eTA=; b=JanKRcWPkNGl+w9RteREyO6PzYci3+TBkW6Bexff/1XgXRsBePD35QcVKXnoYWzXHo q/NaUrRpps0ww5vb1Z86Eng+7Ts1B1pOfc1jiri7XeClnxNPBsIFEm3moSGgJCdeInBn b0QFst1Uv+fUlSTu+AtFvqFvkr9bbBUgLcsxXxoOobxyjUef51zS4PPzIv8/7w4OlUBu AISVXYT73zKuQ7pIZ5uY6Vhnhlr7XhMB1LzP33A3g/12IzM8ozJ211cRnSzQvS+CwBWA wnO6TwL0NeRo6D+cPE9mJnxLBYEBIcOHf2gW6+JbuJBYZqS3sTZ7w3iuNRFhEkA4cTly yqTQ==
X-Gm-Message-State: AHYfb5hR3oU6dYinFgrsK1q5nNXmwuEPNlRBN4rbJKa3cpprS8XBOijU ZaU4KgVtpzXYFLZVOG23I+Xd5CM4Xw==
X-Received: by 10.13.213.148 with SMTP id x142mr1243253ywd.311.1502888499404; Wed, 16 Aug 2017 06:01:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.40.194 with HTTP; Wed, 16 Aug 2017 06:01:38 -0700 (PDT)
In-Reply-To: <CABkgnnV1MokRJZw=ks5s7iwumDj0AnUy0CVbHCUm_rOifTcJ9g@mail.gmail.com>
References: <150285392127.12601.16486468628540142046.idtracker@ietfa.amsl.com> <CABkgnnV1MokRJZw=ks5s7iwumDj0AnUy0CVbHCUm_rOifTcJ9g@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 16 Aug 2017 08:01:38 -0500
Message-ID: <CAKKJt-ffMW4Nu9WGnrAeE5=jN=X5E9RYdkKgjzaUv-+69ppesQ@mail.gmail.com>
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Ben Campbell <ben@nostrum.com>, "webpush@ietf.org" <webpush@ietf.org>, draft-ietf-webpush-encryption@ietf.org, webpush-chairs@ietf.org, The IESG <iesg@ietf.org>, Phil Sorber <sorber@apache.org>
Content-Type: multipart/alternative; boundary="001a114fa26624f0880556de7f07"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/fpfyVEPB_6Euc9IqPUbBwg6ild8>
Subject: Re: [Webpush] Ben Campbell's Yes on draft-ietf-webpush-encryption-08: (with COMMENT)
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
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: Wed, 16 Aug 2017 13:01:45 -0000

Hi, Martin,

On Wed, Aug 16, 2017 at 12:19 AM, Martin Thomson <martin.thomson@gmail.com>;
wrote:

> On 16 August 2017 at 13:25, Ben Campbell <ben@nostrum.com>; wrote:
> > - 1: "For efficiency reasons, multiple users of Web Push often share a
> >    central agent that aggregates push functionality."
> >
> > Is the "central agent" a push server, application server, or something
> else?
>
> With Spencer's comment addressed, this is now:
>
>   Multiple users of Web Push at the same user agent often share a
> central agent that aggregates push functionality.
>
> Does that make sense now?  PR here:
> https://github.com/webpush-wg/webpush-encryption/pull/21
>
>
Ben's thread, but Spencer appreciates the clarification.


> > -1: "Web Push messages are the payload of an HTTP message " - Plural
> disagreement.
>
> Fixed previously in response to directorate review or by a PR.
>
> > -4, first paragraph: s/ "... some of the length..." / "... sum of the
> length ..."
>
> As above.
>
>