IETF Logo Mail Archive

Re: [Webpush] WGLC for draft-ietf-webpush-encryption-07

Kit Cambridge <kit@mozilla.com> Mon, 13 February 2017 09:35 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 91769129551 for <webpush@ietfa.amsl.com>; 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 <webpush@ietfa.amsl.com>; 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 <webpush@ietf.org>; Mon, 13 Feb 2017 01:35:41 -0800 (PST)
Received: by mail-qk0-x231.google.com with SMTP id s186so88478147qkb.1 for <webpush@ietf.org>; 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 <kit@mozilla.com>
Date: Mon, 13 Feb 2017 01:35:39 -0800
Message-ID: <CAEeQnYK_cuapQhtZ1zcqeDyuofZeWyjpw=SX0UqkaaN3cwJ8Yw@mail.gmail.com>
To: Shida Schubert <shida.at.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="001a114dbb78ace02f0548662ba7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/yjC4dIkvilg1UTJndhUWCbbEzQ4>
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 <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, 13 Feb 2017 09:35:42 -0000

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 <shida.at.ietf@gmail.com>
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
>

v2.23.0 | Report a Bug | By Email