From nobody Sun Feb 12 18:36:57 2017 Return-Path: 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 885E2129463 for ; Sun, 12 Feb 2017 18:36:55 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jGvF7F-EWrWy for ; Sun, 12 Feb 2017 18:36:54 -0800 (PST) Received: from mail-pg0-x244.google.com (mail-pg0-x244.google.com [IPv6:2607:f8b0:400e:c05::244]) (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 1BFA81294A4 for ; Sun, 12 Feb 2017 18:36:54 -0800 (PST) Received: by mail-pg0-x244.google.com with SMTP id v184so8429273pgv.1 for ; Sun, 12 Feb 2017 18:36:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=LJCfVoU+j1YGbmXxeuc3zpuHM6YAvWnkUEngfWRxky4=; b=EcMRkvNWnZoeEY2nJGkDSgYtmE0DAPM9/w9dOpnGWnaIh1LGbdM9DwO8hTZ1PPm9By MJNR9S28oBp9c5kWH3XICJMEIqsYD8red+c15DnSAM01eHe2TJRXoDJ2ErZojhsHM7di UH40V07vWZi6eetA8O1f72dt6IRQGyVFgku9INZqDuxZNNGkmEMxp2fLn2ahg6PKsECx 2LkONOIHHuNU7wzjyzC48n6VOuwQfaCRLOaY1sCw9nZgbE/6+Luk9CLtkLbXdfPu7DmL R85rB5QSG0/CzuwB4T5tcp8pMMksc+Un+4ZOC39Hr+DOLuR/fJThW1LY8FPUgUuWCtN3 ZhPg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=LJCfVoU+j1YGbmXxeuc3zpuHM6YAvWnkUEngfWRxky4=; b=lOC8c3KT+gLyXLkw0W1WuPOzkkNkx33H0nqU6IJQEHNWoFBmZ+S1GEllJwrhuMpUpD FITf3qMoGeKmQ1wUlAZtyiAYhvkOoYc9Sfg0HWHJApFjcEQOug/7LbWXMkWNzLOGGsSH CvySKzggoLEdMfQgHkxaOlTwtCg2QAzdyTgj99zqPiHEVTxiGUgNyOQtKkO4KZO3OO/Q HGSamotCQ3VDPVP2De9NWmeT5D0JZRFczHTgp5QaeiJmXbO/Hmtnz0kVE67mD3AXsO2Y CTwMS4Lp9O5J5Maj/+H77TQDYvGFeMy6aVcy2IJo2gJeFLPMB8RxHPiVI8d3sNf6p3B1 Ol3g== X-Gm-Message-State: AMke39kt//YR/r3C+uitVXtuhhFnOtpjw2tKQfInNH2o67c2NLSqNO+b9rTLeyD3DTs4TA== X-Received: by 10.99.133.65 with SMTP id u62mr24284447pgd.70.1486953413527; Sun, 12 Feb 2017 18:36:53 -0800 (PST) Received: from ?IPv6:2601:647:204:5d2f:61c3:d318:b1d7:60b8? ([2601:647:204:5d2f:61c3:d318:b1d7:60b8]) by smtp.gmail.com with ESMTPSA id o66sm10819084pfa.119.2017.02.12.18.36.52 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 12 Feb 2017 18:36:53 -0800 (PST) From: Shida Schubert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <04EFDA44-A77F-4B9A-A95E-6DCA2A8AB1CD@gmail.com> Date: Sun, 12 Feb 2017 18:36:51 -0800 To: webpush@ietf.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Archived-At: Subject: [Webpush] WGLC for draft-ietf-webpush-encryption-07 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 02:36:55 -0000 Belated happy new year; Martin Thomson submitted the revised vapid draft and the encryption = draft before Christmas of the last year. =20 This is an announcement to commence WGLC on = draft-ietf-webpush-encryption.=20 https://tools.ietf.org/html/draft-ietf-webpush-encryption-07 As we will be running WGLC for two drafts, the duration of the last call = will be three weeks ending on March 6th.=20 As usual, please help with the followings; 1. Read the draft and address any issues (please try to provide = constructive suggestion/fixes) 2. If you only find nits, they can be sent directly to the author(s) 3. If you have read the draft but you see no issues and you are = satisfied to progress, then please let the WG know by submitting an ACK = or +1 to the list.=20 Many thanks!=20 Shida= From nobody Sun Feb 12 18:38:16 2017 Return-Path: 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 56FEA129450 for ; Sun, 12 Feb 2017 18:38:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: 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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XnqiPuz_KFuJ for ; Sun, 12 Feb 2017 18:38:13 -0800 (PST) Received: from mail-pg0-x243.google.com (mail-pg0-x243.google.com [IPv6:2607:f8b0:400e:c05::243]) (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 A68751294DC for ; Sun, 12 Feb 2017 18:38:12 -0800 (PST) Received: by mail-pg0-x243.google.com with SMTP id 194so8440068pgd.0 for ; Sun, 12 Feb 2017 18:38:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:subject:message-id:date:to :mime-version; bh=Ucc+zyTeqUyMQecW/gZceQtkUjXv7/C1s5YnU9oktOI=; b=HE++u1V20JLndSGtxnQqN+7fGaYjkEM20Chvgfjulb5JOn/+hkj/M8l2GqcA+6RHfL xeUOkipuKOtO3VvvYVgsaqpH4I0Nw0t0pmzdxNde+XkNetGextQAslQSs6QukaHPWaN4 6Xq/ZCmtj/EgoATW+I1Eymp62GOPXqEbJ5Lrzgl3gh+Ocodq5QzoKvvVE1UOd/6WRt1d 61g8ufX3tkJMAoaM6hCMJZHdSVimzwCTH6QbbiWrY3199PPqAzIgnwIdvdDvpjzI4aeV 4qQ54Ihqv0FwMtJJEZX5a4Ia/oe1PE0AXrKfaFx3qVpq4A8gnHaPDsjFwl+yjFnGcxdY vrUQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:subject :message-id:date:to:mime-version; bh=Ucc+zyTeqUyMQecW/gZceQtkUjXv7/C1s5YnU9oktOI=; b=iJPPpOaQTqmwZbjhYlQ7BJcAIC67n9s/1Tjr3qtulm6ymkxB33kohIsYZsTMC9URfc TfGDUo86UXB4HR/mQkIYKV8+CRNoiE5hcLYXuJZeXoS/3PwlJATt32pdTy2tcKg9HWQG bkx12+hJ4SyvyvT9KLk2PlVQKXan396rp+nETMzmkWr2NgOcnzykcCxvDIyDVQcCZOIS yIGbjQao7WKhEiTTH+Y26JZPSXpOeMMSnp2+yMMLH4jZqDJsPn9BY/kH+/IAVIuzUt8L DNicsr05Z6h5O8FtnndvnonQzI658KDgD76+nqaIEYWdm/iRkvXAlrjnIeXTVyKaPHnD OoiQ== X-Gm-Message-State: AMke39nHfHHUiF99BvZg8tA/RU/TCW07SCvHzlWPsn5ETSLSnLp8wnQRGPjokopXhgK1/w== X-Received: by 10.84.233.132 with SMTP id l4mr27136860plk.15.1486953492148; Sun, 12 Feb 2017 18:38:12 -0800 (PST) Received: from ?IPv6:2601:647:204:5d2f:61c3:d318:b1d7:60b8? ([2601:647:204:5d2f:61c3:d318:b1d7:60b8]) by smtp.gmail.com with ESMTPSA id t12sm9848407pfg.4.2017.02.12.18.38.11 for (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Sun, 12 Feb 2017 18:38:11 -0800 (PST) From: Shida Schubert Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Message-Id: <9D16243B-BABC-466A-BAE0-A009DA106DA1@gmail.com> Date: Sun, 12 Feb 2017 18:38:10 -0800 To: webpush@ietf.org Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Archived-At: Subject: [Webpush] WGLC for draft-ietf-webpush-vapid-02 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 02:38:14 -0000 And here is another one.=20 This is an announcement to commence WGLC on draft-ietf-webpush-vapid.=20 https://tools.ietf.org/html/draft-ietf-webpush-vapid-02 As we will are running another WGLC, the duration of the last call for = this draft will be three weeks ending on March 6th.=20 As usual, please help with the followings; 1. Read the draft and address any issues (please try to provide = constructive suggestion/fixes) 2. If you only find nits, they can be sent directly to the author(s) 3. If you have read the draft but you see no issues and you are = satisfied to progress, then please let the WG know by submitting an ACK = or +1 to the list.=20 Many thanks!=20 Shida= From nobody Mon Feb 13 01:35:43 2017 Return-Path: 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 91769129551 for ; Mon, 13 Feb 2017 01:35:42 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mozilla.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 5BU2zg-9m-im for ; Mon, 13 Feb 2017 01:35:41 -0800 (PST) Received: from mail-qk0-x231.google.com (mail-qk0-x231.google.com [IPv6:2607:f8b0:400d:c09::231]) (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 137811294E1 for ; Mon, 13 Feb 2017 01:35:41 -0800 (PST) Received: by mail-qk0-x231.google.com with SMTP id s186so88478147qkb.1 for ; Mon, 13 Feb 2017 01:35:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mozilla.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AiheLmnZmRB+4B0syOyqh6JSxjSuzwnXcqzEHapTWDA=; b=P6BqOJK/LplfLXxjaDn5JVevqBk0ORqO9MAzLrdrU450OmmXx26bMJIzPDJv8KJRER 55916OkOB3ULCaSl7REhS6+3A41KGM6OWsBDxtn23NHqumveBPdTKEGjm5wCZdEvhY01 bJRcHtfr0Yguv1VWkb1rRWaqPfwWYmQ9e+9tc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AiheLmnZmRB+4B0syOyqh6JSxjSuzwnXcqzEHapTWDA=; b=LFqTZKFy5fJmyBSqcpd/JFmDeXUFeF/L3DCBKJ5JheWYWzijBjvlhpRjkZlLI07d19 YvQMUbYyfQgUMk19Z9WpjDVRpdcyQEDZNwMOSw2679qYfYzoKsnrgOiyEkrs58nAPi8K mzLtFhRh7VO8mz08147OZ1qFd8zv/vmUhXsDGGVuV7K85qjZH8SF4s/qal4KyqUqBkm8 vjp3dNWNlBm+Yg6uyY4d3SXkOQYURtwa84i1MOZIjRQ9GcRrAcMIrHAI/HGrVPlllGSo pH7L1RiRlvy9lRd98BuG8+ohAcCcd+D11002vxH9xcBVM8FzR/RclnD/dI9lC2mjcMO3 eDhA== X-Gm-Message-State: AMke39ky4Nu0h3+awaI24/5Bc43HgUx/tXujcqLIF5X7RP4GBJ0ur9NLRZz/3yMcalSfzSWOLWUa3Fnij2T8Uudx X-Received: by 10.55.87.198 with SMTP id l189mr19905526qkb.106.1486978540139; Mon, 13 Feb 2017 01:35:40 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.20.49 with HTTP; Mon, 13 Feb 2017 01:35:39 -0800 (PST) In-Reply-To: <04EFDA44-A77F-4B9A-A95E-6DCA2A8AB1CD@gmail.com> References: <04EFDA44-A77F-4B9A-A95E-6DCA2A8AB1CD@gmail.com> From: Kit Cambridge Date: Mon, 13 Feb 2017 01:35:39 -0800 Message-ID: To: Shida Schubert Content-Type: multipart/alternative; boundary=001a114dbb78ace02f0548662ba7 Archived-At: Cc: webpush@ietf.org Subject: Re: [Webpush] WGLC for draft-ietf-webpush-encryption-07 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 09:35:42 -0000 --001a114dbb78ace02f0548662ba7 Content-Type: text/plain; charset=UTF-8 Thank you for sending this out, Shida! Sorry if this is a silly question: since this draft relies substantially on http://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html, does it make sense to defer last call until that's ready, or include ECE in the last call alongside this one? Cheers, - kit On Sun, Feb 12, 2017 at 6:36 PM, Shida Schubert wrote: > > Belated happy new year; > > Martin Thomson submitted the revised vapid draft and the encryption draft > before Christmas of the last year. > > This is an announcement to commence WGLC on draft-ietf-webpush-encryption. > > https://tools.ietf.org/html/draft-ietf-webpush-encryption-07 > > As we will be running WGLC for two drafts, the duration of the last call > will be three weeks ending on March 6th. > > As usual, please help with the followings; > > 1. Read the draft and address any issues (please try to provide > constructive suggestion/fixes) > 2. If you only find nits, they can be sent directly to the author(s) > 3. If you have read the draft but you see no issues and you are satisfied > to progress, then please let the WG know by submitting an ACK or +1 to the > list. > > Many thanks! > Shida > _______________________________________________ > Webpush mailing list > Webpush@ietf.org > https://www.ietf.org/mailman/listinfo/webpush > --001a114dbb78ace02f0548662ba7 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Thank you for sending this out, Shida! Sorry if this is a = silly question: since this draft relies substantially on htt= p://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html<= /a>, does it make sense to defer last call until that's ready, or inclu= de ECE in the last call alongside this one?

Cheers,
- kit

On Sun, Feb 12,= 2017 at 6:36 PM, Shida Schubert <shida.at.ietf@gmail.com> wrote:

Belated happy new year;

Martin Thomson submitted the revised vapid draft and the encryption draft b= efore Christmas of the last year.

This is an announcement to commence WGLC on draft-ietf-webpush-encryption.<= br>
https://tools.ietf.org/html/draft-i= etf-webpush-encryption-07

As we will be running WGLC for two drafts, the duration of the last call wi= ll be three weeks ending on March 6th.

As usual, please help with the followings;

1. Read the draft and address any issues (please try to provide constructiv= e suggestion/fixes)
2. If you only find nits, they can be sent directly to the author(s)
3. If you have read the draft but you see no issues and you are satisfied t= o progress, then please let the WG know by submitting an ACK or +1 to the l= ist.

Many thanks!
Shida
_______________________________________________
Webpush mailing list
Webpush@ietf.org
https://www.ietf.org/mailman/listinfo/webpush<= br>

--001a114dbb78ace02f0548662ba7-- From nobody Mon Feb 13 13:44:36 2017 Return-Path: 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 C822B12998B for ; Mon, 13 Feb 2017 13:44:33 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.699 X-Spam-Level: X-Spam-Status: No, score=-2.699 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, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 q0VS9St12MO6 for ; Mon, 13 Feb 2017 13:44:32 -0800 (PST) Received: from mail-qt0-x232.google.com (mail-qt0-x232.google.com [IPv6:2607:f8b0:400d:c0d::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 3723A12998A for ; Mon, 13 Feb 2017 13:44:32 -0800 (PST) Received: by mail-qt0-x232.google.com with SMTP id w20so95324224qtb.1 for ; Mon, 13 Feb 2017 13:44:32 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SnZfnnrIRFfSRUpC5f5F1t925gfwr8iDqyyGRgImu7k=; b=jxLgYntK/AJgmW5FxWZx5MNBj52gxD4WK7TZzJnO0YssYRQodICA6EWJuhQXeT6Wmu OmgjnAiioh21EhKsFrAtQwfdR5fEDa+qIkhZAHS9UJOhjva0sy/0GsOk3kcaSd9LCBTx yNI493bG57xtWH0AeAe/nxh6UUeYA8CeCR/3Rx6pVzzHPB1hT9lNVFQ5MnPH3uh0X1Cy DiObxarst7v2rLlN8e3zKLLXvR/dP6syUeC/vwpD+hBVq+0y0C7dN7SYGv55tf/T4w6b vRoN2IMfBoB/JO6BieQ7eCaJ1R/TELc1BIZyDLKWhteBeLWLfytMhGR5aW/YATrp8v+w /MpA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SnZfnnrIRFfSRUpC5f5F1t925gfwr8iDqyyGRgImu7k=; b=EN8gEKpnqG4GSKv6mH1qOeIgAISv2MlccA7HRa5wP1YzbmB6sLgPJ4aIlfWHzK3hZ3 TRGAS1piOTuDBkqPXOF5pcxtg/YLI7kQLRNfFXhLALAavQ8uwe3HgiqZpamsEyq+x9Hs IZsT8Wu8eq5SjpOwliy2/GCJ7Dt+j1MEy0K3Ytd4n99YvXZidC2Pn7GuhXMe2BZCRb08 xxIQOLbF7k04qXp7E0mTKQ2sYR09N8mwDsUNGxEFCByd2dyxJM7XsMMiDN2vQF2IacNe uC5BQDu70LhLErhZaUZeGFxpADnJe0seXnkopaBoeRkvPsCsCj2uJU4tUdk9fq1MF0aS rA6w== X-Gm-Message-State: AMke39mwmJWu3L1l8D0Jh4pE2fNWM2ns1vfaPV2A95zOjdvMsc2nxBcho1zV8zNfo1LBB2317Fx+V/meLPi12g== X-Received: by 10.200.57.199 with SMTP id v65mr23424312qte.13.1487022271283; Mon, 13 Feb 2017 13:44:31 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.19.112 with HTTP; Mon, 13 Feb 2017 13:44:30 -0800 (PST) In-Reply-To: References: <04EFDA44-A77F-4B9A-A95E-6DCA2A8AB1CD@gmail.com> From: Martin Thomson Date: Tue, 14 Feb 2017 08:44:30 +1100 Message-ID: To: Kit Cambridge Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "webpush@ietf.org" , Shida Schubert Subject: Re: [Webpush] WGLC for draft-ietf-webpush-encryption-07 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Feb 2017 21:44:34 -0000 On 13 February 2017 at 20:35, Kit Cambridge wrote: > Thank you for sending this out, Shida! Sorry if this is a silly question: > since this draft relies substantially on > http://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html, > does it make sense to defer last call until that's ready, or include ECE in > the last call alongside this one? Yes, there have been changes there that were the result of discussions in HTTP. That should be resolved in a few weeks. From nobody Mon Feb 13 18:01:08 2017 Return-Path: X-Original-To: webpush@ietf.org Delivered-To: webpush@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 8AE8A129432; Mon, 13 Feb 2017 18:01:06 -0800 (PST) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: internet-drafts@ietf.org To: X-Test-IDTracker: no X-IETF-IDTracker: 6.43.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <148703766652.22257.7966602521715986135.idtracker@ietfa.amsl.com> Date: Mon, 13 Feb 2017 18:01:06 -0800 Archived-At: Cc: webpush@ietf.org Subject: [Webpush] I-D Action: draft-ietf-webpush-encryption-08.txt X-BeenThere: webpush@ietf.org X-Mailman-Version: 2.1.17 List-Id: Discussion of potential IETF work on a web push protocol List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2017 02:01:06 -0000 A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Web-Based Push Notifications of the IETF. Title : Message Encryption for Web Push Author : Martin Thomson Filename : draft-ietf-webpush-encryption-08.txt Pages : 11 Date : 2017-02-13 Abstract: A message encryption scheme is described for the Web Push protocol. This scheme provides confidentiality and integrity for messages sent from an Application Server to a User Agent. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-webpush-encryption/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-webpush-encryption-08 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-webpush-encryption-08 Please note that it may take a couple of minutes from the time of submission until the htmlized version and diff are available at tools.ietf.org. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/ From nobody Mon Feb 13 18:02:15 2017 Return-Path: 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 856C31299F7 for ; Mon, 13 Feb 2017 18:02:14 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, 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=gmail.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 JutJLHZ0L0b2 for ; Mon, 13 Feb 2017 18:02:13 -0800 (PST) Received: from mail-qk0-x234.google.com (mail-qk0-x234.google.com [IPv6:2607:f8b0:400d:c09::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 D68A6129501 for ; Mon, 13 Feb 2017 18:02:12 -0800 (PST) Received: by mail-qk0-x234.google.com with SMTP id p22so18953017qka.0 for ; Mon, 13 Feb 2017 18:02:12 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=DS05paL+aRQpjM99FLfz6QgikfaZBo8hLaPNRONcXUY=; b=rQVvO7058N33wyjGj1c9ob3vtF5mEnRNBAxRflOYr7yVtSpPWTy4nwmzsqeQywAsMM slJI5sA2CqPyt5y/wc/imSedb4oWuKdtGfPsmjTp4wdnbvYktSO+zYJYOHN1tCDPhRVN Wa/Do5dwnC39aBKJxKdGgPPNkbwbbjchfriMMcHANFtlHfRkbZV/x6K7ZrbO/ZI6tSWc jXelTriOSTSZrwtbnkE+8rDbPdcoOcm1We39tZhw36op0s2fc1nFhW6PuicwS0HM5c3F bAqlhEI3JBdcqxdCkwN4Ex+eMIvXE6Ie5r30FN/oO7GbVvpw2a2dLKUDG8504WtXp/nh /BQQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=DS05paL+aRQpjM99FLfz6QgikfaZBo8hLaPNRONcXUY=; b=OdeeQ9f6Wka6S2brVwnGpmkZEItZ4WSweGPsNuqNlhePJAqK6arIrJp+JGC79V699N SZonT2RviS7YkJ1Ubl0VIO7+nxM0XTGl3RmCyxC3rHKZT2CO9EYA3tJ+r9au7yOJ4zdN PAkdLddOhzXPi4+WqCUfpAiLK1SxeMy7t7WzJvSIQe4dVNl/dGPzRkmXL6fCX8+vHna0 OUpoQV6x3JALDpwFyIYXu6KhG/YWlhY5b7UqIZ9bCe0YfeTWVY54NBjfcLOZrx2H2/ps f/pqak+/sNwz421y6EWU7FlHFb4zc3j3Zu9yRM3Y2KMa7lM/2OH62LE26BssCElpJYRK 6opg== X-Gm-Message-State: AMke39lEAo/YqhiQHHCyv9q9eUzX0bjtPxnnyDzcgNIT6a/McDi7ea34VCb0ljxta0YvdEVjNiag978YyH+7Zg== X-Received: by 10.233.235.66 with SMTP id b63mr26691317qkg.144.1487037731945; Mon, 13 Feb 2017 18:02:11 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.19.112 with HTTP; Mon, 13 Feb 2017 18:02:11 -0800 (PST) In-Reply-To: References: <04EFDA44-A77F-4B9A-A95E-6DCA2A8AB1CD@gmail.com> From: Martin Thomson Date: Tue, 14 Feb 2017 13:02:11 +1100 Message-ID: To: Kit Cambridge Content-Type: text/plain; charset=UTF-8 Archived-At: Cc: "webpush@ietf.org" , Shida Schubert Subject: Re: [Webpush] WGLC for draft-ietf-webpush-encryption-07 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Feb 2017 02:02:14 -0000 I have just pushed new versions of the affected drafts. Given that the changes are pretty small in the webpush doc, perhaps we can just use -08 instead. On 14 February 2017 at 08:44, Martin Thomson wrote: > On 13 February 2017 at 20:35, Kit Cambridge wrote: >> Thank you for sending this out, Shida! Sorry if this is a silly question: >> since this draft relies substantially on >> http://httpwg.org/http-extensions/draft-ietf-httpbis-encryption-encoding.html, >> does it make sense to defer last call until that's ready, or include ECE in >> the last call alongside this one? > > > Yes, there have been changes there that were the result of discussions > in HTTP. That should be resolved in a few weeks. From nobody Tue Feb 21 16:30:37 2017 Return-Path: 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 1B86B1294A0 for ; Tue, 21 Feb 2017 16:30:36 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.7 X-Spam-Level: X-Spam-Status: No, score=-2.7 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, TVD_SPACE_RATIO=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 EKxM7hwL6LUP for ; Tue, 21 Feb 2017 16:30:35 -0800 (PST) Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::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 BEA0212949F for ; Tue, 21 Feb 2017 16:30:34 -0800 (PST) Received: by mail-lf0-x235.google.com with SMTP id b80so35620491lfe.3 for ; Tue, 21 Feb 2017 16:30:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=AuMfChKBuSs76efnNfPGrSjXH4pN2QizHKt7ECAbZEA=; b=LlXLNcXL9qHavfRhjtqbsLQibVQaBHCtxXyEXCOBXcaKd908th39dyed/yqA8sFx8x dv7r/hDAogpYrVmmlzGEZ21RYf8OkfaR/KZwjdtZWHh4EFt87TjTDjJjMgY28lxsCrmA 16taoMUTHrN96pMCCcb5NFhhW0/SPD9+vqm4cHWMaT1DmcWQBK4z3quSWUVlptxjETz8 rNnINingtJh2GiOFDAf1YEZzzor0rhu6GG7IYW4pDN87MAY4OuN8RwZIUKuqZSATbRDw v+O+pRjGaqe5EN/fOcQuX5ZrsIS/DeieTesjdt7a0DGpQi0QNp7VNd+o6PcERtr/HD0p Elig== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=AuMfChKBuSs76efnNfPGrSjXH4pN2QizHKt7ECAbZEA=; b=RopHDmsCWXuSCH7xGF2y6tOmn72K7cyeQvIyiitsJplI2sNf1A7Fn4peAUUR3wzcNz ANBTfw4RbnY7ZBcm0dAMiEiVZk+w5N4AGfjXkTR3+WYTegzqJ/gvhBawsyEnvyzypQvL NDtiI7OmPJDkqUucqrv9iap/QUGTBpVc/4dL6KYGWXi3GV2dpDq5BHKAwjMbQmUCQTS7 8azl6ttdkcG5NffN0fH+LV68UeYIXoRxtHr26ZC3vr8WSQpx4Q47sDHgD8nGzPg9nwuN Gjekzr/tTJmby92OMxkMs2C2/4nQBPHSXytkizNy8c+HQ3Fe6JXh/ygN8LE2ZkSB2Asm vANw== X-Gm-Message-State: AMke39n3cP6TWy+d+CXajU6hBYKrFrcbubdXM9wseBpWiEBw1A3Vq9ptNNw80ocvg601TE2Mb5yxljBIDmb8htkh X-Received: by 10.25.221.132 with SMTP id w4mr1244641lfi.59.1487723432596; Tue, 21 Feb 2017 16:30:32 -0800 (PST) MIME-Version: 1.0 From: Costin Manolache Date: Wed, 22 Feb 2017 00:30:20 +0000 Message-ID: To: webpush@ietf.org Content-Type: multipart/alternative; boundary=94eb2c0c8ae0b9ca710549139af0 Archived-At: Subject: [Webpush] up.corp.google.com - MOMA Single Sign Onopidopikkpjtpiopikkikkopikplijipopieopielkpi 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 22 Feb 2017 00:30:36 -0000 --94eb2c0c8ae0b9ca710549139af0 Content-Type: text/plain; charset=UTF-8 chrome://history/ --94eb2c0c8ae0b9ca710549139af0 Content-Type: text/html; charset=UTF-8
chrome://history/
--94eb2c0c8ae0b9ca710549139af0--