IETF Logo Mail Archive

Re: [Webpush] Non-blocking comments on -05

Kit Cambridge <kcambridge@mozilla.com> Thu, 09 June 2016 19:00 UTC

Return-Path: <kcambridge@mozilla.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 B0C4E12D934 for <webpush@ietfa.amsl.com>; Thu, 9 Jun 2016 12:00:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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=mozilla-com.20150623.gappssmtp.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 Lbp9buUIflW4 for <webpush@ietfa.amsl.com>; Thu, 9 Jun 2016 12:00:53 -0700 (PDT)
Received: from mail-pf0-x236.google.com (mail-pf0-x236.google.com [IPv6:2607:f8b0:400e:c00::236]) (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 9652512D914 for <webpush@ietf.org>; Thu, 9 Jun 2016 12:00:41 -0700 (PDT)
Received: by mail-pf0-x236.google.com with SMTP id t190so15494949pfb.3 for <webpush@ietf.org>; Thu, 09 Jun 2016 12:00:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla-com.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LnR+a39qL7CQTXFVUiM7+Nt089EVog1+2i8+MmtaRhw=; b=TT/9xqHF9DOh91GZXwBiKqQRqZXLX2qkr74ovSTtOOeSPWCbs8ZgF2k+2G9HoST1MS 4KmaDdxBmEhkJWGTiJNbKfPPCPZvLOcKCnVXJI6XLyR1f5k82flumtpWrTIvQiGZVqMT TiNfsIkte2PH0h1JrGwn8IeF+dMushAu3dQgDsBCCvG2vjY3/2p+r5LetIqtiLpHeKFS ZNgaCLntmQwIFLKZYBRxsEGdRScWkZJ6EH9U9K4qd0fOv/cnfDu3OP1vrs1DiZaQLYa9 XT8e0xGCxpjrspRwrzpJ/qQwsdmqJxGQEH3XYQ35ubHkfOI6nffHHee+gkXpa3MVgAN2 JyNA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=LnR+a39qL7CQTXFVUiM7+Nt089EVog1+2i8+MmtaRhw=; b=IzWhHZVGU5A+7/i6IRoPQy/hAiD+uMWoqMUMlUUqAX/R+sAdv916l6H5OaMqNF2zoF MrNiUlEOccUPx89R7MGq/Mx8ZhYbEmKQcoeW/elqzrm3Giv/Bk1afEuLfYPOeBU1CMOo Jqtib7ZsnhOlEIsJPaEBao2oggtzZHXKtPiyuk7qdnXc6BHQMPMTYIfRfUi9EsIxTV2U q6glGT8yKto7xDnZ5rdMIjQRiw5gyM9oeiHXCQ8O2OaBMCTP4CI1E1zSUmiKjZK0rikp Yx6b+A0v1reo+11U5TeYct4AlQhsziln6dCoUPyC3lwKtD6JBCx1fhKXxkQYfvMreErS uDKQ==
X-Gm-Message-State: ALyK8tI356dmCF4SeyHv6HeLTw9/HGEbQipizBS28lMj3AS6yLaZ660ARE8+fcEhg+AOXPMU
X-Received: by 10.98.29.81 with SMTP id d78mr356905pfd.142.1465498841036; Thu, 09 Jun 2016 12:00:41 -0700 (PDT)
Received: from [10.252.28.174] (corp.mtv2.mozilla.com. [63.245.221.32]) by smtp.gmail.com with ESMTPSA id c13sm11842744pfc.40.2016.06.09.12.00.39 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Thu, 09 Jun 2016 12:00:40 -0700 (PDT)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Kit Cambridge <kcambridge@mozilla.com>
In-Reply-To: <CO2PR03MB2407918AF75578E3AE378FC3835E0@CO2PR03MB2407.namprd03.prod.outlook.com>
Date: Thu, 9 Jun 2016 12:01:12 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <2953D35A-1FC9-4765-BBE0-83DBCA8CAC10@mozilla.com>
References: <CALt3x6=_yc9TegOut_g+6W5fvhP7sfW+_gwRZnEVFA5PNgER6Q@mail.gmail.com> <6af49c2baf1b4e4f884b812d573b947e@Antiope.crf.canon.fr> <CABkgnnWebfxnPOLMXK+n+2G=c8DOG4Eb4AWMsWXJmmdnE4pUwg@mail.gmail.com> <989D9268-BE9A-47F7-9181-C0F323D1DA1F@mozilla.com> <1464858574.5342.12.camel@crf.canon.fr> <CO2PR03MB2407918AF75578E3AE378FC3835E0@CO2PR03MB2407.namprd03.prod.outlook.com>
To: Brian Raymor <Brian.Raymor@microsoft.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/DF1p_jDpSpZTpKekMEewtNL6QBM>
Cc: Costin Manolache <costin@gmail.com>, "beverloo@google.com" <beverloo@google.com>, "martin.thomson@gmail.com" <martin.thomson@gmail.com>, "webpush@ietf.org" <webpush@ietf.org>, RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Subject: Re: [Webpush] Non-blocking comments on -05
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, 09 Jun 2016 19:00:56 -0000

On Jun 8, 2016, at 1:44 PM, Brian Raymor <Brian.Raymor@microsoft.com> wrote:

> Kit - does the PR address your feedback below?

Yes, “monitoring subscriptions for other clients” is clearer. Thank you!

> Costin raised a concern about this specific sentence:
>  Each subscription set can then be managed independently, which might include being moved between user agents.
> 
> noting:
> 
>> BTW - I am also interested in the 'move between UA' use case, but I don't think there is enough implementation and data around it.
> 
> Does anyone else share this concern?

Does moving a subscription set mean another UA would be able to receive messages sent to subscriptions in that set? (That is, without requiring the old UA to drop all its subscriptions and the new UA to reregister).

v2.8.7 | Report a Bug | By Email