[Webpush] Provide a method to indicate rate-limit issues

Benjamin Bangert <bbangert@mozilla.com> Fri, 30 October 2015 19:24 UTC

Return-Path: <bbangert@mozilla.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 8FD061B3AE3 for <webpush@ietfa.amsl.com>; Fri, 30 Oct 2015 12:24:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.278
X-Spam-Level:
X-Spam-Status: No, score=-1.278 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=no
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 T1pkMOcdgUNo for <webpush@ietfa.amsl.com>; Fri, 30 Oct 2015 12:24:06 -0700 (PDT)
Received: from mail-wi0-x234.google.com (mail-wi0-x234.google.com [IPv6:2a00:1450:400c:c05::234]) (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 C96711B3AE2 for <webpush@ietf.org>; Fri, 30 Oct 2015 12:24:05 -0700 (PDT)
Received: by wikq8 with SMTP id q8so17500869wik.1 for <webpush@ietf.org>; Fri, 30 Oct 2015 12:24:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla_com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:subject:from:to:content-type; bh=iRzVtllCZgb/HzbXpxcYEscXN/pdUu7AVzdk9mLwomY=; b=ldr7kw+rRHou0lerFFrAP2FuNXDGYijRT7Vk62jVCaYfY8c0BhfDkvmxDFo85SSfzu 5fS8MZXgf+xjjaGwtiPdmanzyrJ7MRuh+Kn1odMtx8X8hX76Z0nyhjZ7rqeLpfGoNEuZ DTaj8jmkS3Li3tVkWUVYel73FNNHlCkh2TWPsVy0clDs0yOPP/GhUqaLD0M4HxNDJNSe Xx15MeHBRxe8N7r21tmqrhJQ6zYi/3nsjAxv4ccwnv1YNRZD/is7Jhtt55CVmX4keLOu tvt74Cc0eRgA2WhIekBbHLSDx9+eQin1QY5rvnf5kNfhKb2eUaPzmVPjfRAt08iavr3W tpsQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:date:message-id:subject:from:to :content-type; bh=iRzVtllCZgb/HzbXpxcYEscXN/pdUu7AVzdk9mLwomY=; b=NOZdVTMEzZjV+OSeAa9woGBc1XdNAekLlrvspRWy4netjJkWTQsrZCpK7qwJWtkBTb OQmo0oH/LDUKZK1MG0VDY7nEDktMIEavoYb8uJiddok6Ql1eTEDf/Ho9ueqxr/MgbQjL 4l7CsGLbWc0QOfrVY0C/8n1ORHxVcF3RF+hpXjloUOX2qT39e+oZUgNf5kkGcdM3sxth 8EPx+1dcMMpkWoiKtv+JakHAm235LFd9VQ4/Wc7HurC8vICud/q7ZUOTFPb2vl+TfYYX kQSfYAOVpwoPiikZz7yZyXFZk0s4h8oeIlSbxKsWJU7YtKqysVtgKCi4LxXc9UqRYbR+ pypQ==
X-Gm-Message-State: ALoCoQm8bpNDXGfuXLmoYCP1aok0wV2ctlQpWxQHPq5+lnAiGA2nDTR4+hZm6m6wlSMGo3xAgKz9
MIME-Version: 1.0
X-Received: by 10.194.63.7 with SMTP id c7mr10391651wjs.70.1446233044162; Fri, 30 Oct 2015 12:24:04 -0700 (PDT)
Received: by 10.27.155.207 with HTTP; Fri, 30 Oct 2015 12:24:04 -0700 (PDT)
Date: Fri, 30 Oct 2015 12:24:04 -0700
Message-ID: <CABp8EuKLJQQbyPCbRTTq=ZxYaQaMCQPYe+FUveUs=3tGF4MHpg@mail.gmail.com>
From: Benjamin Bangert <bbangert@mozilla.com>
To: "webpush@ietf.org" <webpush@ietf.org>
Content-Type: multipart/alternative; boundary="047d7b86d9ccdc409c0523575ef6"
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/-KNcha12mRkXkdCAOU7OI4lhEro>
Subject: [Webpush] Provide a method to indicate rate-limit issues
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: <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: Fri, 30 Oct 2015 19:24:07 -0000

It would be nice to have a uniform way to indicate to an Application Server
that its being rate-limited and it should back-off on its sending, in a
separate way than using a 503. 503's are used for a variety of issues,
separate from rate-limiting, perhaps a different status code, and/or a
header indicating when the app-server should resume.

Cheers,
Ben