Re: Header Compression
Ted Hardie <ted.ietf@gmail.com> Thu, 20 June 2013 22:59 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 84BFF21F9A73 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 20 Jun 2013 15:59:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.265
X-Spam-Level:
X-Spam-Status: No, score=-9.265 tagged_above=-999 required=5 tests=[AWL=1.333, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-8]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id TFlsnM9UPo0l for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 20 Jun 2013 15:59:25 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id AE18621E80A9 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 20 Jun 2013 15:59:21 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1UpnoH-00013A-Ig for ietf-http-wg-dist@listhub.w3.org; Thu, 20 Jun 2013 22:58:33 +0000
Resent-Date: Thu, 20 Jun 2013 22:58:33 +0000
Resent-Message-Id: <E1UpnoH-00013A-Ig@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <ted.ietf@gmail.com>) id 1Upno3-00012L-Vw for ietf-http-wg@listhub.w3.org; Thu, 20 Jun 2013 22:58:20 +0000
Received: from mail-wi0-f178.google.com ([209.85.212.178]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <ted.ietf@gmail.com>) id 1Upno2-00011F-Sk for ietf-http-wg@w3.org; Thu, 20 Jun 2013 22:58:19 +0000
Received: by mail-wi0-f178.google.com with SMTP id k10so65755wiv.17 for <ietf-http-wg@w3.org>; Thu, 20 Jun 2013 15:57:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=O4g5RLQnm1mu5mEogbTSjspOkMcD1LQTZJl/U1LxIYA=; b=YnkYmrJxAxhcn6rjGIcub5HTNp14kSKYxqRxyz7PENBNlyjQHQo7kXm2H4KxqcQw7s jkSbgXA6HMajG2m1s8yrVF7zUaT2OIKdbOZqQefUjoj+bbEqJSn1Izr2FiHeqOol1iLo 9FgQQiXkX/E/tPslY531Xk9Vq4DJNyS9/ofrHMovTRTvsuw5vN9f1sK8NWQtt8P8ep7J kGebkxyyrFfeykMTlXgZ/tbmky/eNBrGnysgHeLINj4w+0QWMvn7CACP+B+AxZMSH3G4 xZJ1kkOSNQ3gNgq0qgRP/laKmi4oydc79+sSsPsp97ZSRtYB63nqWBJNCXMFGta76PxO XuCg==
MIME-Version: 1.0
X-Received: by 10.194.85.233 with SMTP id k9mr7008109wjz.36.1371769072756; Thu, 20 Jun 2013 15:57:52 -0700 (PDT)
Received: by 10.227.164.137 with HTTP; Thu, 20 Jun 2013 15:57:52 -0700 (PDT)
In-Reply-To: <6C71876BDCCD01488E70A2399529D5E525EC01A3@ADELE.crf.canon.fr>
References: <6C71876BDCCD01488E70A2399529D5E516531910@ADELE.crf.canon.fr> <CAJ_4DfTQ=X1RE+4aO58_1h7_sCvhNW19ZTFAC7htA4Tb_5gj8w@mail.gmail.com> <6C71876BDCCD01488E70A2399529D5E516532B26@ADELE.crf.canon.fr> <CABkgnnURGjmOTNM=mNKOAdmU0F87Rbs_2jDcGQ3_tAVzofwKrg@mail.gmail.com> <6C71876BDCCD01488E70A2399529D5E5165335A6@ADELE.crf.canon.fr> <CA+9kkMAgPWFUVHgZrLuf+1-qtV17hY93-mRwh9-UH04Yw4MhfQ@mail.gmail.com> <6C71876BDCCD01488E70A2399529D5E525EC01A3@ADELE.crf.canon.fr>
Date: Thu, 20 Jun 2013 15:57:52 -0700
Message-ID: <CA+9kkMAP1=WUhO71+uienmwK+WWwa0Y+e5uLtsSagnDT1igtCg@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
To: RUELLAN Herve <Herve.Ruellan@crf.canon.fr>
Cc: Martin Thomson <martin.thomson@gmail.com>, Ryan Hamilton <rch@google.com>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="089e0102e3e04badfc04df9de014"
Received-SPF: pass client-ip=209.85.212.178; envelope-from=ted.ietf@gmail.com; helo=mail-wi0-f178.google.com
X-W3C-Hub-Spam-Status: No, score=-3.5
X-W3C-Hub-Spam-Report: AWL=-2.711, 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: lisa.w3.org 1Upno2-00011F-Sk c6c0cc82a2e72f84c33e86e28c43e878
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Header Compression
Archived-At: <http://www.w3.org/mid/CA+9kkMAP1=WUhO71+uienmwK+WWwa0Y+e5uLtsSagnDT1igtCg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/18328
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>
On Mon, Jun 17, 2013 at 9:43 AM, RUELLAN Herve <Herve.Ruellan@crf.canon.fr>wrote: > > Second, it is a design choice not to have deletion: the mean of removing a > header is to replace it with a new one. Another possibility is to use the > automatic dropping of headers to remove the headers that were the oldest to > be added to the table (see penultimate paragraph of section 3.1 Header > Table). > > Sorry for the delay in responding. Just to make sure I understand: I have a header "Example: ". It's in position 3 in the index. I want to remove "Example: ". To do so, I update position 3 with a new header, say, "Fleen: ". The Fleen header can be a no-op, a duplicate of another header, or something I care about now and did not before. Is that about right? If so, I don't think the draft is clear on this point. I think making an explicit statement that there is no "delete" operation but that a similar aim can be accomplished by updating an index position with a new header, including a no-op header, would be useful. regards, Ted Hardie > Hervé. > ------------------------------ > *From:* Ted Hardie [ted.ietf@gmail.com] > *Sent:* Tuesday, June 11, 2013 18:33 > *To:* RUELLAN Herve > *Cc:* Martin Thomson; Ryan Hamilton; ietf-http-wg@w3.org > *Subject:* Re: Header Compression > > On Tue, Jun 11, 2013 at 7:05 AM, RUELLAN Herve < > Herve.Ruellan@crf.canon.fr> wrote: > >> I just did it : >> http://www.ietf.org/id/draft-ruellan-http-header-compression-00.txt >> >> Hervé. >> >> > Hi Herve, > > A couple of quick comments. First, for the TODO in your security > considerations section, I think you should probably expand on the text in > the overview, which describes the attack on Deflate and unpack why the > current scheme is resistant to similar attacks. Second, the document > describes substitution and insertion, but does not describe deletion. If > a party wishes to remove a header (note: not change to a null value) is > this possible and, if so, what's the process? > > regards, > > Ted Hardie > > > >> > -----Original Message----- >> > From: Martin Thomson [mailto:martin.thomson@gmail.com] >> > Sent: jeudi 6 juin 2013 18:46 >> > To: RUELLAN Herve >> > Cc: Ryan Hamilton; ietf-http-wg@w3.org >> > Subject: Re: Header Compression >> > >> > On 6 June 2013 04:43, RUELLAN Herve <Herve.Ruellan@crf.canon.fr> >> wrote: >> > > Yes there are now both HTML and txt version available: >> > > http://http2.github.io/compression-spec/compression-spec.html >> > > http://http2.github.io/compression-spec/compression-spec.txt >> > >> > Could you please visit https://datatracker.ietf.org/idst/upload.cgi >> > and go through the motions for us. It's a procedural matter that >> shouldn't >> > take more than a couple of minutes. >> > >
- Re: Header Compression Martin Thomson
- Header Compression RUELLAN Herve
- Re: Header Compression James M Snell
- Re: Header Compression Martin Thomson
- Re: Header Compression Ryan Hamilton
- Re: Header Compression Mark Nottingham
- Re: Header Compression Yoav Nir
- RE: Header Compression RUELLAN Herve
- Re: Header Compression Tatsuhiro Tsujikawa
- Re: Header Compression James M Snell
- RE: Header Compression RUELLAN Herve
- Re: Header Compression Ted Hardie
- RE: Header Compression RUELLAN Herve
- RE: Header Compression RUELLAN Herve
- Re: Header Compression Ted Hardie
- Re: Header Compression Roberto Peon