IETF Logo Mail Archive

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

Martin Thomson <martin.thomson@gmail.com> Thu, 13 October 2016 00:10 UTC

Return-Path: <martin.thomson@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 DC8D9129401; Wed, 12 Oct 2016 17:10:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable 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 OoldHaUGYuly; Wed, 12 Oct 2016 17:10:08 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::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 C23E9127735; Wed, 12 Oct 2016 17:01:14 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id z190so60509825qkc.2; Wed, 12 Oct 2016 17:01:14 -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=2AsmPHt28ukwJ2a99CVYDq+2Fp0uq01psMhyabuoSCY=; b=QaPHQiGx7/62DYYy5XpUA51T3iGMt9yy+dDzD+T1QvdhGQ8aaAQel/HOZd5HIS5PYT AXwTKWIgceugVjrT8m8oX7JVivq1/O+bQbioEfOg8GRetcJYIxaoW4/mPepxmoBn3Jv6 D50v3G8zjTugBuPR0TNCe7tA35EAPYw+z4NeSiB122HgZ2YCDb31ZqhmU9XmM/YfZhJq DoYwntKn4O1juOWtHrLSxW2vfsYUgoyMB37414OzW7YETnLz7v6eMJ9TCKfd4GNb1WfO TYPrmKrHQZFLPqfTTkOMOkSHo9vvou0rrhcruw3qhdi7xqnWSF2fNVdVDxJX51ucf7eS 2eig==
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=2AsmPHt28ukwJ2a99CVYDq+2Fp0uq01psMhyabuoSCY=; b=cb+B8pRlQPHIqGWDZHFjyljIk2RlElJmsWQuJC1mFfoLwwu5XcS2TyHSkJ/lgBDQI0 DHBqpSJK7AjuW87jiy8mpjnj/QBlCKiSCCrRp6dkJdiGzeTG/pTtMDvRMdjwPKd9WNwy 2i4lR1okI67itgl8lvBltLcr/SAq2hv8K/88nOcYtv+TlO1sKZCUx4EGVWMHhjst2+Vf 6Kk4avz0MvM6EWqJx5sGQeynLZ9DhKnZ9F1n3i4AbNpssf7bYm8HmeS5gpVKIVJxoTQZ pt0jtIo+t+GMPx3COHq0ux1tL4qVujnUasPxBjNTTOr1RRCwu5rAwz/souLaM1n5Q0Zh NhZA==
X-Gm-Message-State: AA6/9Rlr9RA6pxkHfgyLuJ7z0oy0I73wrv6iovKEHEhFocuInQxF81yNEba2Vl681EXwOnWmoERQl+VpgMpOeg==
X-Received: by 10.55.99.17 with SMTP id x17mr3585897qkb.147.1476316873904; Wed, 12 Oct 2016 17:01:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.85.7 with HTTP; Wed, 12 Oct 2016 17:01:13 -0700 (PDT)
In-Reply-To: <147630754676.6419.3793529940535426058.idtracker@ietfa.amsl.com>
References: <147630754676.6419.3793529940535426058.idtracker@ietfa.amsl.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 13 Oct 2016 11:01:13 +1100
Message-ID: <CABkgnnW9yP8NHC7xJwN-qt_0Oc=WrxRhWcMO3=YY_8qFvAyzhA@mail.gmail.com>
To: Ben Campbell <ben@nostrum.com>, "Brian Raymor (MS OPEN TECH)" <Brian.Raymor@microsoft.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/uywbXt2FZomIPtHChbPnhAdGoEM>
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" <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: Thu, 13 Oct 2016 00:10:10 -0000

On 13 October 2016 at 08:25, Ben Campbell <ben@nostrum.com> wrote:
> 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?

This specifically refers to the work in draft-ietf-webpush-encryption,
which covers these things.  We should add a f'rexample there.  Brian,
does that sound right?

(Yes, TLS is mandatory, but hop-by-hop mechanisms don't cover all the bases.)

v2.23.0 | Report a Bug | By Email