Re: [Webpush] Versioning aes128gcm-encoded messages
Martin Thomson <martin.thomson@gmail.com> Mon, 20 March 2017 03:52 UTC
Return-Path: <martin.thomson@gmail.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 54BC5129552 for <webpush@ietfa.amsl.com>; Sun, 19 Mar 2017 20:52:44 -0700 (PDT)
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 nDl4kW9ZRMNm for <webpush@ietfa.amsl.com>; Sun, 19 Mar 2017 20:52:42 -0700 (PDT)
Received: from mail-qk0-x229.google.com (mail-qk0-x229.google.com [IPv6:2607:f8b0:400d:c09::229]) (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 9ED68129551 for <webpush@ietf.org>; Sun, 19 Mar 2017 20:52:42 -0700 (PDT)
Received: by mail-qk0-x229.google.com with SMTP id y76so101084547qkb.0 for <webpush@ietf.org>; Sun, 19 Mar 2017 20:52:42 -0700 (PDT)
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=zIWLSOghMg7wdCXW+BqxuwBwd4cIdEJTIKR2nwibfyU=; b=un/Ve7W42CTILnCrnDb588bHZH26sdGGIauYZEOZnTKEUeKwDRzGShtopm7ttlmeP5 /+68ivKGZ2sbwLa7oDW4N1m2ijoXX2LWZndS4H2XRR17ZvEypVuyqBL+qlgqclSA0x8s y8pRoHiVBnau/gHubpbFqCYdjCKLOT6eewz+MlW/dxuHPNvJZSMxYDCuUfqrzrtUPz54 17Asx/ghMl7CqS5JY4WyFa8C05YTNhw6U57/wSQOPF8wO7BZvZ/KMzRVHn7vJYrcmIB0 /HNl4MmY9lnBAdxzOvl/Wcg0pPK4HkiQ10Uec4dr+ZzMziLFE2kNQGCSRJ0XCYKfyLag rlqQ==
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=zIWLSOghMg7wdCXW+BqxuwBwd4cIdEJTIKR2nwibfyU=; b=OqAmLi2G88lxKdTCdzXX3reiAj3tEsk7X18l748LoovmEfSHZd/ntuyrm92Qavx3P8 VDpXV0MMS4FJfKfG1fWem9PcCGqC38TlrOoj4ejN1cZ7wzTvVa90rdM/eQdMDEJja0Sm SaqFLHcmHyqsB9sgG8kb8bacnlGz9zV3cQ1JORpsgqR+QY+y6clj7Mg7TaH8VxLe8Rb1 cSVgiF1SCAFvnwLmQMSob/4SIUeEb1tCo4E6yKVQLwNj/PDm/scPAgvw/lT5uY49sI5C KC6Gf4pD57noFeW5rL5sY/N2CPZC7fvtw3in5hZ+wSG9YYRdZzL3/IY9j7bWtSOX5GVB 2GZw==
X-Gm-Message-State: AFeK/H26XUzQWnTsVAM9DutBauXLZOJKxYAZkO8R1W/PwGBM6ga8bU8XWAgiYIT1IZXecPiplP8ta/Rot6dCvA==
X-Received: by 10.233.237.20 with SMTP id c20mr24628425qkg.144.1489981961868; Sun, 19 Mar 2017 20:52:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.140.27.194 with HTTP; Sun, 19 Mar 2017 20:52:41 -0700 (PDT)
In-Reply-To: <CA+XEteNrHQvDZZch9u=BP1t4x0D24NMgEFZHWN9+_kqH5oeo1g@mail.gmail.com>
References: <CAEeQnYKmJ9-E3JQArvNxbwJuTZvjwRW2W9002sciLNGKJDbKhg@mail.gmail.com> <CABkgnnXTAO5OyPR5iMFiO0JLY4MtwNYEn1X9ksOyydbDvPsSTg@mail.gmail.com> <CA+XEteNrHQvDZZch9u=BP1t4x0D24NMgEFZHWN9+_kqH5oeo1g@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 20 Mar 2017 14:52:41 +1100
Message-ID: <CABkgnnV6Y6pWqWfgxdeeVhuYgxBkipcDOj2bd2RZFBty6VNumg@mail.gmail.com>
To: JR Conlin <jrconlin@mozilla.com>
Cc: Kit Cambridge <kit@mozilla.com>, "webpush@ietf.org" <webpush@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/webpush/FiPvLnqs7-YJc6RgG-LvEvcENqA>
Subject: Re: [Webpush] Versioning aes128gcm-encoded messages
X-BeenThere: webpush@ietf.org
X-Mailman-Version: 2.1.22
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, 20 Mar 2017 03:52:44 -0000
On 20 March 2017 at 14:12, JR Conlin <jconlin@mozilla.com> wrote: > Unfortunately, the current binary format starts with a randomized value, so > adding information to the header cannot easily be differentiated. I'm fine > if the eventual replacement for ECE either specifies a labeled prefix (I > hate to use DER as an example, but that sort of format is fairly predictable > and flexible.) Likewise, we could suffix the version onto the > Content-Encoding. It would break current clients, of course, but it at least > would provide some flexibility in the future. The problem with versioning inline is that it is invisible to HTTP content negotiation. Granted, that doesn't really make any difference to the push usage, but a label is visible. If you accept the need to have more labels, then the inline check is redundant.
- Re: [Webpush] Versioning aes128gcm-encoded messag… Kit Cambridge
- [Webpush] Versioning aes128gcm-encoded messages Kit Cambridge
- Re: [Webpush] Versioning aes128gcm-encoded messag… Martin Thomson
- Re: [Webpush] Versioning aes128gcm-encoded messag… JR Conlin
- Re: [Webpush] Versioning aes128gcm-encoded messag… Martin Thomson