[Webpush] draft-chiussi-webpush-subscription-less-framework-01 and request for feedback on Subscription Management

Fabio Chiussi <fabiochiussi@gmail.com> Mon, 02 November 2015 02:27 UTC

Return-Path: <fabiochiussi@gmail.com>
X-Original-To: webpush@ietfa.amsl.com
Delivered-To: webpush@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id B1C6A1ACEAA for <webpush@ietfa.amsl.com>; Sun, 1 Nov 2015 18:27:44 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
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
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id p32XM8V8z5RI for <webpush@ietfa.amsl.com>; Sun, 1 Nov 2015 18:27:42 -0800 (PST)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 48F581ACEAE for <webpush@ietf.org>; Sun, 1 Nov 2015 18:27:41 -0800 (PST)
Received: by igpw7 with SMTP id w7so40557264igp.1 for <webpush@ietf.org>; Sun, 01 Nov 2015 18:27:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=7L/kcENTG1ldRP/0V0SoF24t9It8wEvBpvcXm9Z3dQU=; b=sMdbjtLVqTXFZQ9fLOD9ftwyz9m6/hgldeCrzoiLZ6s14zLFPikFtLa6XYpVHguZ7V kXKP56Vp7gyM4vvLZ21bI/7txPZ8grwV0JMrW4YLQY0isaXSl+ZBPI15F5g5R2eI4l2K gScFMmW5d++klJdfMmGGkZ6n6RXRQyDGx/Dk60KElvgGS9vmV3+nHzFUXUEHX0WvFCnE hLo9v6Ugajr0CqI5BlTP6wJJ3y9v8PlUL6P3kWHQqs2v00/UKwuM9676BOSDraofnvFd +tQfXwduakya7PZkkUS+XXWhEyKNX9N/Zal0sljhtDIf6OovASoUG2MeqohPmKgA3VIh zaOw==
MIME-Version: 1.0
X-Received: by with SMTP id sa4mr9071883igb.76.1446431260625; Sun, 01 Nov 2015 18:27:40 -0800 (PST)
Received: by with HTTP; Sun, 1 Nov 2015 18:27:40 -0800 (PST)
Date: Sun, 1 Nov 2015 18:27:40 -0800
Message-ID: <CAD3o52u+N1TA2m8Dm-ybDZkQ7PQY7FAML+YtEPkQLdMV1mJbig@mail.gmail.com>
From: Fabio Chiussi <fabiochiussi@gmail.com>
To: webpush@ietf.org
Content-Type: multipart/alternative; boundary=001a1134bce27b4fdd052385851d
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/e0Yw8-hHvWXikL5BFG_EXXBJzjQ>
Subject: [Webpush] draft-chiussi-webpush-subscription-less-framework-01 and request for feedback on Subscription Management
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: Mon, 02 Nov 2015 02:27:44 -0000

Hi All,

I submitted a new draft: draft-chiussi-webpush-subscription-less-framework-01,
which I will briefly present at the WG meeting tomorrow. This draft
discusses two issues: i) a number of relevant use cases for webpush may
benefit from a "relaxed" model of subscription, and ii) there is an
emerging need for global management of webpush traffic across applications.

As a possible solution for both issues, this draft advocates the
introduction of a notion of trusted "Subscription Authority" in charge of
controlling webpush traffic to each UA.

Beyond the specific solution proposed in this draft, I would like to
solicit feedback from the mailing list on the more general issue of
Subscription Management, which we can discuss tomorrow at the meeting.
Specifically, any comments would be greatly appreciated on the following.

1. For the reasons outlined in the draft, Subscription Management seems a
very relevant practical issue that needs to be addressed.

2. In the current core protocol WG document, Subscription Management is
only addressed in passing, by assuming some kind of control policy in
assigning the subscriptions. At this time, neither the issues and use cases
related to Subscription Management, nor the possible solutions have been
fully studied in the draft. I think this is simply due to the fact that the
core protocol design, for obvious reasons, has been the focus of the work
so far, and there has not been sufficient time yet to fully address other
relevant issues, such as Subscription Management

3. However, the state of the work on the core protocol design has reached
sufficient maturity that the WG should start considering to address some of
these other topics as well. Subscription Management seems a critical and
urgent one, since it has very important practical ramifications. The
solution proposed in this draft is simply one of possible candidates, and
Subscription Management certainly deserves a more comprehensive study, and
possibly develop a framework for Subscription Management. Because of its
practical relevancy, subscription Management should become a WG item.

I'll compile any comments that the mailing list may have on these topics,
and bring them forward for discussion at the meeting tomorrow.