IETF Logo Mail Archive

Re: Set-Cookie and Cookie Optimized Binary Encoding

James M Snell <jasnell@gmail.com> Sun, 20 January 2013 02:17 UTC

Return-Path: <ietf-http-wg-request@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E9A621F8767 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 19 Jan 2013 18:17:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.299
X-Spam-Level:
X-Spam-Status: No, score=-9.299 tagged_above=-999 required=5 tests=[AWL=1.299, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mtrc+-sAvc4y for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sat, 19 Jan 2013 18:17:06 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 3B6DC21F86EF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sat, 19 Jan 2013 18:17:05 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Twjls-0002wh-J3 for ietf-http-wg-dist@listhub.w3.org; Sun, 20 Jan 2013 01:32:28 +0000
Resent-Date: Sun, 20 Jan 2013 01:32:28 +0000
Resent-Message-Id: <E1Twjls-0002wh-J3@frink.w3.org>
Received: from maggie.w3.org ([128.30.52.39]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1Twjlo-0002vx-F6 for ietf-http-wg@listhub.w3.org; Sun, 20 Jan 2013 01:32:24 +0000
Received: from mail-ie0-f179.google.com ([209.85.223.179]) by maggie.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <jasnell@gmail.com>) id 1Twjln-0000Pg-So for ietf-http-wg@w3.org; Sun, 20 Jan 2013 01:32:24 +0000
Received: by mail-ie0-f179.google.com with SMTP id k14so8038458iea.38 for <ietf-http-wg@w3.org>; Sat, 19 Jan 2013 17:31:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Mh/kDe2ooKC85lNyKmkgAvOEqJ3OKjVjuqVXl+MDEb0=; b=WtTmPNHfX5vrqsU7bf/H/BuQajQheiRaCOso1ebjPay984yRgFMKiGhNWq88+skRB9 Mgcy2LDhUOVGTM1AAPS4mtcDV7Zbf+32Xnt+pDXaJ0BYYyfRVG7uL03qU2kIovl3vnlu 0YENVESgyVzO4cKjzjyjNdiaj9/AqP1r3rVRfnHsaAWvacFICIQSUpRg/SvEVxzvbx88 CkZ6y9nKYF9wMvzcLdriKEO4BQtw3A/hKV6uI6zA+RCwy9R0NynDXY9zbvlewHBW0yTw l4nMHNEbunstlQvsq3b4FZWfXorxw0ebHA9ftA2uHD4EPfvQZF1xrp/1UH+UlinfA73x OG5g==
MIME-Version: 1.0
X-Received: by 10.50.158.170 with SMTP id wv10mr6115065igb.75.1358645517423; Sat, 19 Jan 2013 17:31:57 -0800 (PST)
Received: by 10.64.26.137 with HTTP; Sat, 19 Jan 2013 17:31:57 -0800 (PST)
Received: by 10.64.26.137 with HTTP; Sat, 19 Jan 2013 17:31:57 -0800 (PST)
In-Reply-To: <CAK3OfOgYgemMX9FHrTWnv=+oWaVjtj7R9qyToznb0Y2yjKnCGQ@mail.gmail.com>
References: <CABP7RbcYw4=Lv_JHRAq9HNKQZ9GthE1ZhbXGC4fPna1aD3eZeA@mail.gmail.com> <591317E9-3090-4491-8694-F1E06217D6B4@mnot.net> <CABP7RbfTrN0GLRDrnLWvoyE5TfE+8U=0frpD0kHVcz+dqCkA2Q@mail.gmail.com> <CAK3OfOgYgemMX9FHrTWnv=+oWaVjtj7R9qyToznb0Y2yjKnCGQ@mail.gmail.com>
Date: Sat, 19 Jan 2013 17:31:57 -0800
Message-ID: <CABP7RbfwsdC1Fkt0P8TB3bMyJhb7ENM0cptJgF-=aV9ZSmS7+A@mail.gmail.com>
From: James M Snell <jasnell@gmail.com>
To: Nico Williams <nico@cryptonector.com>
Cc: Mark Nottingham <mnot@mnot.net>, ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary="14dae9340f217115b804d3ae4f1a"
Received-SPF: pass client-ip=209.85.223.179; envelope-from=jasnell@gmail.com; helo=mail-ie0-f179.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.710, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001
X-W3C-Scan-Sig: maggie.w3.org 1Twjln-0000Pg-So 939ed96ec9581207a04f058fd47b69e9
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Set-Cookie and Cookie Optimized Binary Encoding
Archived-At: <http://www.w3.org/mid/CABP7RbfwsdC1Fkt0P8TB3bMyJhb7ENM0cptJgF-=aV9ZSmS7+A@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16030
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <http://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Part of that escape hatch ought to be a bit in the encoded header that
indicates a binary or text value. If it's text, then the 1.1 format is
used. If it's binary, the optimized format is used and we get a closest we
can get compromise on the translation from one to the other.
On Jan 19, 2013 5:28 PM, "Nico Williams" <nico@cryptonector.com> wrote:

> On Sat, Jan 19, 2013 at 6:11 PM, James M Snell <jasnell@gmail.com> wrote:
> > Yes, indeed. I'm wondering if there's a reasonable balance we can support
> > here... That is, provide for backwards compatibility for most but not all
> > 1.1 features and optimize for the most commonly used bits. Restricting
> set
> > cookie syntax could be one of those compromises.
>
> We should try to optimize bridging between HTTP/1.* and HTTP/2.0, but
> we should not penalize a pure HTTP/2.0 future in the process.  The
> obvious thing to do is to provide an escape hatch for contents we
> don't optimize and not try to optimize absolutely everything.
>
> Nico
> --
>

v2.23.0 | Report a Bug | By Email