Re: [Webpush] Authorization to send messages

Martin Thomson <martin.thomson@gmail.com> Thu, 05 March 2015 20:43 UTC

Return-Path: <martin.thomson@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D5D791A8AD4 for <webpush@ietfa.amsl.com>; Thu, 5 Mar 2015 12:43:40 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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, SPF_PASS=-0.001] autolearn=ham
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 KNZxMVCqOL0d for <webpush@ietfa.amsl.com>; Thu, 5 Mar 2015 12:43:39 -0800 (PST)
Received: from mail-oi0-x232.google.com (mail-oi0-x232.google.com [IPv6:2607:f8b0:4003:c06::232]) (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 9908B1A8AC5 for <webpush@ietf.org>; Thu, 5 Mar 2015 12:43:39 -0800 (PST)
Received: by oibg201 with SMTP id g201so14027365oib.10 for <webpush@ietf.org>; Thu, 05 Mar 2015 12:43:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=MYOC47jMkwHnRcZl9PEhWVhUImfDxyajaCzzBDwTh4Y=; b=V++nrN2fEVD1Iq4EWe+Fc+uNXwFNeqlHfXuTPcgWfJDxFvDvancTXDSE6Qm48zvSrw MV/jWFhUbri/OoeutkvQ6JFpVyLQRdCJKwpjzL6MklzFaZIVxBtn9QrKoCIUAzrqjp7Q k8kTkeVUCckaohdTy0XWE6TH9SfI2ww386LtMiZ5VUnk5DG7r9u8jROCIACPU+yZDPzM CwCE4y796mCzOHPdKOwUJXiUm+Dsa+76qk9vxDTlj38xFkj9QqNl+SQ1FNC89CeM1zAS H8mccpOjU41aLP1ot1MioStX3Sv3s8uNAysGUY4fR7pyAewmFW4+oQxMAYk4ZiiLxJX3 5f0w==
MIME-Version: 1.0
X-Received: by 10.182.60.197 with SMTP id j5mr8317270obr.85.1425588219131; Thu, 05 Mar 2015 12:43:39 -0800 (PST)
Received: by 10.202.225.135 with HTTP; Thu, 5 Mar 2015 12:43:39 -0800 (PST)
In-Reply-To: <CABp8EuLYjSwJBQS8BsRXsO2D155GyEFGzUF19VAkUJrrww9b4A@mail.gmail.com>
References: <CABp8EuLYjSwJBQS8BsRXsO2D155GyEFGzUF19VAkUJrrww9b4A@mail.gmail.com>
Date: Thu, 05 Mar 2015 12:43:39 -0800
Message-ID: <CABkgnnUGEQuXXbP_=Y7Xzeu2JjUVWKQd844-KZ5o8caNxnP=Lg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
To: Benjamin Bangert <bbangert@mozilla.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/ocJkd5QHu1fzM-N45LG8GZAGAZk>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] Authorization to send messages
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 05 Mar 2015 20:43:41 -0000

On 5 March 2015 at 11:33, Benjamin Bangert <bbangert@mozilla.com> wrote:
> In webpush http2-02, section 8.3 Authorization doesn't mention how the Push
> Service should deal with authenticating an Application Server wishing to
> send messages. From conversations I've heard, it does sound like all major
> vendors plan on requiring Application Server's to provide some form of
> authentication/token as GCM/APNS/etc already do.

It has always been my view that knowledge of the endpoint is necessary
and sufficient here.  But I've gained a more nuanced view over time.

In particular, Costin has suggested that we build a system whereby a
sender can register, thereby establishing a continuous, if
pseudonymous, identity.  That helps with DoS mitigation strategies,
largely because the Push Server can build up a reputation for each
identity over time.