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

Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com> Wed, 12 October 2016 21:29 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 F1AB212978B; Wed, 12 Oct 2016 14:29:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level:
X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, 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 84MjT5goSOzD; Wed, 12 Oct 2016 14:29:58 -0700 (PDT)
Received: from mail-yw0-x22e.google.com (mail-yw0-x22e.google.com [IPv6:2607:f8b0:4002:c05::22e]) (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 BF9841297BC; Wed, 12 Oct 2016 14:29:43 -0700 (PDT)
Received: by mail-yw0-x22e.google.com with SMTP id t193so41201078ywc.2; Wed, 12 Oct 2016 14:29:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Td4CrnXUg2yvkNDcqM3RbKDVDEK1vOI0Fd1QJqjuTNQ=; b=GCbdW+bsRPpNojgYinse5quoTE5ICHcb18LYf8FerdGT66G1VlGNfqIaVGkNXK4pBi szX7UHl7pyO3x90iQIGqvhrZv9VreXylFLiiB7OKTwTNy4+DMiZuPrHJcpzqMkzLuODE bnxhUeF92cJV5HknCGtW5PwgRkoihkyAYNEwMue3I7C6o5ArRUzJuSqbnWmKclmikDT9 OSNdzqsLPIr0DpdK1pJFi/6RA7ixVUNzjha9LHSwJCZbi3ALGqhnfceBp152sNQDWLQs JOlNrbglznojfkLZiFRAaJ9ADf8WFDeuJeFWgJ2QYrBpFapHhHZFR5X6jS+9FqtFAIvh gLIg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Td4CrnXUg2yvkNDcqM3RbKDVDEK1vOI0Fd1QJqjuTNQ=; b=QCLEVIblNL/XG7Kp/LhxHkbQBn0YT/xPJNIzRFLf8K6Ky+GrSB+yBbKSY4sOSQHf0L NQ5Hm1NYVZoEPANAaY9n5BsMo8UBbNQzvt/LwJvnt1JGhEVoMgpogj6Fki7UkuvAvJ4H tO8+6LhPkPxI282bUl1bXU+DAJyIMzQZknM9BVolD3K558kLJRQ4FQO1xu+7uDYGZz16 gtIZC2fb84qgsDsSbrLOfURA8yYcJM7W0Km1GLRA+th//gdOSPOqW52LrppFo91S24Os HpjFzF2RbSmoA9im5iH4AhLJXCCTpUvfd14zQmVU9Vg8xy0k16MxIhoCJt4/wdllQpEl gasQ==
X-Gm-Message-State: AA6/9RkB8zlD/wPC4PJdvclSNUK6HAt7bL1Sse9VTQCdVbnMfoQ5Iu4Gkx15pphi0y9ECLpaU/eqDNHwBzT9ng==
X-Received: by 10.129.125.198 with SMTP id y189mr2749426ywc.234.1476307783065; Wed, 12 Oct 2016 14:29:43 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.92.67 with HTTP; Wed, 12 Oct 2016 14:29:42 -0700 (PDT)
In-Reply-To: <147630754676.6419.3793529940535426058.idtracker@ietfa.amsl.com>
References: <147630754676.6419.3793529940535426058.idtracker@ietfa.amsl.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 12 Oct 2016 16:29:42 -0500
Message-ID: <CAKKJt-fk5UaMHgKhHugpLbTH8TVTq8MWYzkhDLOwSL-kH3u94A@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>
Content-Type: multipart/alternative; boundary="001a114926a0fd291f053eb1b0e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/y9qUJ_VWRgoXhZ-AzhqsuftgY8A>
Cc: draft-ietf-webpush-protocol@ietf.org, Shida Schubert <shida@ntt-at.com>, webpush-chairs@ietf.org, The IESG <iesg@ietf.org>, webpush@ietf.org
Subject: Re: [Webpush] Ben Campbell's Yes on draft-ietf-webpush-protocol-11: (with COMMENT)
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.17
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, 12 Oct 2016 21:30:00 -0000

On Wed, Oct 12, 2016 at 4:25 PM, Ben Campbell <ben@nostrum.com> wrote:

> Ben Campbell has entered the following ballot position for
> draft-ietf-webpush-protocol-11: 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-protocol/
>
>
>
> ----------------------------------------------------------------------
> COMMENT:
> ----------------------------------------------------------------------
>
> Thanks for a well written document. I have a few questions on one topic,
> for which the answers may be obvious to people other than me:
>
> In section 8, 2nd paragraph: "Applications using this protocol MUST use
> mechanisms that provide
>    confidentiality, integrity and data origin authentication."
>
> What must it use those mechanisms for? Are we talking about communication
> between the UA and app servers? Are we just talking about data in motion?
>  As much as I like to see such requirements in general, is it reasonable
> for webpush to state requirements on the internal operation of the
> application?
>

For what it's worth, I didn't understand whether the mandatory HTTP over
TLS (right?) satisfies this MUST, or whether it meant something completely
different.

So I'm also curious about Ben's comment.