Re: [Webpush] VAPID as a WG item?
Peter Beverloo <beverloo@google.com> Mon, 14 March 2016 11:46 UTC
Return-Path: <beverloo@google.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 A759C12DA30
for <webpush@ietfa.amsl.com>; Mon, 14 Mar 2016 04:46:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7,
RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=google.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 3Iy14xD6TgNz for <webpush@ietfa.amsl.com>;
Mon, 14 Mar 2016 04:46:44 -0700 (PDT)
Received: from mail-lb0-x233.google.com (mail-lb0-x233.google.com
[IPv6:2a00:1450:4010:c04::233])
(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 657DE12D589
for <webpush@ietf.org>; Mon, 14 Mar 2016 04:46:44 -0700 (PDT)
Received: by mail-lb0-x233.google.com with SMTP id bc4so234764351lbc.2
for <webpush@ietf.org>; Mon, 14 Mar 2016 04:46:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:cc; bh=0ugc4ym/j7lxVtYEeGpVdaaChIdNasZBN3OlEiArt/g=;
b=KkpMUwVBQdAjvWArWX07hqbRAbXDlYT2xq3arHu9KgtM6SEwQY2HqBY9gNAKYV04Dy
6rkBJCBXKqaK1TWE0O8rEACwG+TeYRp+HbedKAgNWEdi5+RLw8a5a6GQxuiEnyB62mh6
P51EJClPFl3+RQmou3nzypmrJ0WIj5tq6iplb52vdFkSCGnHCtBGscXt3S+rOpiRioc6
EcxKtSxSlWGM+93+gvBX1InRD5PcUF6jsHdZolHF4owqZqlc012MW+f43rt4avfOBAEN
fd6/1EuldDmURph6iOjfLc+LfOCp/UBSv6nuuuh0aOcDGbxIwtjfxeOuTRCmsmk1ymKm
pXDw==
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:date
:message-id:subject:from:to:cc;
bh=0ugc4ym/j7lxVtYEeGpVdaaChIdNasZBN3OlEiArt/g=;
b=iCL6Xtly+fQ5hhAObq5UzdpRNX+DtTxeClx0xOEVY6L43aUpNDkFToHf7AGeZccYj3
7gBtZL1McSTLcwIGvrPQx+MHGHgc5gDwLGgVL0Sc/oPszzwaLoQW4j9TKPBkReO+sq5S
ATNkdUHM5Q9AvclIyB27hdZwmwBxU+Ui67SJxgelJPCZRt4mhuuYQq2njfTTRLNVxw5d
46Zg3L9sZD3DZ8vwAdfBhKcTtCTKcszvphw3Ba1kmi+Jv9NW78LaYQMqbolKxvl56erh
Vcepu5iMsbum0Ajxhn3qWyoPAbbk99x95cbMPklWTdFPjotBRFKHAJya58I5it0duyfh
hKKQ==
X-Gm-Message-State: AD7BkJKQvP2g3OF4ebTCzPZNTp3FG98fA2JJd4euuANkf6zeq6jqWEiO/T7USvs9oDuEt9JLd3WgGp6z1EUTgfHz
MIME-Version: 1.0
X-Received: by 10.25.141.82 with SMTP id p79mr8088680lfd.42.1457956002553;
Mon, 14 Mar 2016 04:46:42 -0700 (PDT)
Received: by 10.25.20.72 with HTTP; Mon, 14 Mar 2016 04:46:42 -0700 (PDT)
In-Reply-To: <B6007B58-573A-4E30-8AB2-E47E48ED95B9@ntt-at.com>
References: <B6007B58-573A-4E30-8AB2-E47E48ED95B9@ntt-at.com>
Date: Mon, 14 Mar 2016 11:46:42 +0000
Message-ID: <CALt3x6=3fGf880=7vvdzxODn8TdxqTUtnkU+mVccNVYrN_Syww@mail.gmail.com>
From: Peter Beverloo <beverloo@google.com>
To: Shida Schubert <shida@ntt-at.com>
Content-Type: multipart/alternative; boundary=001a11401c7aa1c983052e00d5b0
Archived-At: <http://mailarchive.ietf.org/arch/msg/webpush/ABb9XE0aubPXH94CEwvlRPe0wV8>
Cc: "webpush@ietf.org" <webpush@ietf.org>
Subject: Re: [Webpush] VAPID as a WG item?
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: Mon, 14 Mar 2016 11:46:46 -0000
Yes, we are. In addition, we're also working on an implementation and expect to feed back our experiences there in case anything comes up. Specific to question (1), there may be some overlap with Martin's question of whether to adopt it as the solution to Issue 44. http://www.ietf.org/mail-archive/web/webpush/current/msg00411.html Thanks, Peter On Sun, Mar 13, 2016 at 11:47 PM, Shida Schubert <shida@ntt-at.com> wrote: > > All; > > I am wanting to hear people’s opinion on adopting > draft-thomson-webpush-vapid as a WG item. > > I will need to talk to AD about adding this to a milestone (or as part of > the core protocol milestone) but before I go ahead and do that, I want to > see if people in the WG are; > > 1. Interested to work on the problem it’s trying to solve. > 2. Willing to review and contribute to move this forward. > > Thanks! > Shida as co-chair > > _______________________________________________ > Webpush mailing list > Webpush@ietf.org > https://www.ietf.org/mailman/listinfo/webpush >
- [Webpush] VAPID as a WG item? Shida Schubert
- Re: [Webpush] VAPID as a WG item? Peter Beverloo
- Re: [Webpush] VAPID as a WG item? Shida Schubert