IETF Logo Mail Archive

Re: WGLC comment on draft-ietf-httpbis-encryption-encoding-03, was: Encryption content coding simplification

Julian Reschke <julian.reschke@gmx.de> Thu, 13 October 2016 18:13 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 50C7612943A for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 13 Oct 2016 11:13:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.917
X-Spam-Level:
X-Spam-Status: No, score=-9.917 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-2.996, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 dh8IffvUFxf6 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Thu, 13 Oct 2016 11:13:51 -0700 (PDT)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 83408129619 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Thu, 13 Oct 2016 11:13:51 -0700 (PDT)
Received: from lists by frink.w3.org with local (Exim 4.80) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1bukRz-0007PZ-Ij for ietf-http-wg-dist@listhub.w3.org; Thu, 13 Oct 2016 18:09:51 +0000
Resent-Date: Thu, 13 Oct 2016 18:09:51 +0000
Resent-Message-Id: <E1bukRz-0007PZ-Ij@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bukRu-0007Nt-A0 for ietf-http-wg@listhub.w3.org; Thu, 13 Oct 2016 18:09:46 +0000
Received: from mout.gmx.net ([212.227.15.19]) by lisa.w3.org with esmtps (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from <julian.reschke@gmx.de>) id 1bukRr-00089j-TF for ietf-http-wg@w3.org; Thu, 13 Oct 2016 18:09:45 +0000
Received: from [192.168.178.20] ([93.217.126.239]) by mail.gmx.com (mrgmx001) with ESMTPSA (Nemesis) id 0MHH6Z-1bgmDr0xPv-00E69T; Thu, 13 Oct 2016 20:09:12 +0200
To: Mike Bishop <Michael.Bishop@microsoft.com>, Poul-Henning Kamp <phk@phk.freebsd.dk>
References: <CABkgnnXCMFRthQRCgvSXVjaMwE8BPTdfUYZHCa2tEwhDQ3RUpA@mail.gmail.com> <66482.1470305393@critter.freebsd.dk> <CABkgnnVYh3=pNp4aTVf5OfvskJ8yZvA4j_MDVyQ7GoZgdZO2Kg@mail.gmail.com> <49a8c514-5a39-d4f6-7012-01977cbefb9c@gmx.de> <28071.1476344375@critter.freebsd.dk> <BN6PR03MB27081537BD49FBF383CE66E987DC0@BN6PR03MB2708.namprd03.prod.outlook.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
From: Julian Reschke <julian.reschke@gmx.de>
Message-ID: <bc9e0fcb-03d8-5592-4388-4641d308dba3@gmx.de>
Date: Thu, 13 Oct 2016 20:09:10 +0200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0
MIME-Version: 1.0
In-Reply-To: <BN6PR03MB27081537BD49FBF383CE66E987DC0@BN6PR03MB2708.namprd03.prod.outlook.com>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:mpKefkig6e2+rcTMIe8NbWych+B8W/Tqxfwjk+C0CAih6oFo9Bv SmQ4CaS5xrgQo5P/3S6JvcbJAYS+bcLmNW9wvuNoUk8JUtvPf6OLrWaxtTOZATEuxOoJkhj TFAtsTZc2IXNlUAk5aDntHA8OT7UH/fRFNnU/UM+Z3bfCjjx9NFwIpdIE4O6BJEYQxMDRv+ v2F4iV74pqmJlyREr0jWg==
X-UI-Out-Filterresults: notjunk:1;V01:K0:5l8w0/B1eqs=:iA+q00AnWcqE736d36plNZ wouKf2+SACggkEynshMkqkQ6Hosqgbp9zBfxH2yEROr5nrB0RkUBXb+V5A+SMq1W/pn8wro/m FnaWklAuI+MZFR/hL4YMHHCJmWYpXmSvWn48ZOYC+WDLRAnxgDlzf37GnxhQf9pLR3gG8de6v 9TDaaek+4FnSld36YTuSiISRC1UqW3bb6gUnHUwAcr4nR7JFpTgUTyfITAj9N6pMA4yY5B4OW jMDrNebzX+6kZT4cd5+1k9azmhDkWkJ83E6lNkreplu+SxfHFSIwZZGoUXpPMiAq9oR1r/Nj9 S2Z+MDtFA2a+gvdXf0TPRTN5KfreFHswxESdLWik7+BsGsOPTIwJJ+1C39yIvz/3yX/ObaW3l Aux346BRzsu5OXEJ4FHeNmuMwWNsY2O85MzRj840DQdFAYN6eYRLwEyE0uB7bcZeGcRzs9Kms uFRU2CAmF2Wpk0YZ3kDEHMFU8fGfVKxqNbhTqh23P/mHxh321IydJhkfLmnvxxD9ZVm3v/gnb S8Hi+XsGMSUJ4DNAo18+iPxGcGOsWga3JFEUEFOmskprqF/2lbMBR460v0t6bcYs7A32z3IXl 5UYLuky244ciSDL3jfj7PSgA9Tt86y2RrNzbYiX56Y8xCeGcQuImrvUQMGW2RxRsQaOg5ImG9 RCy2vdwq1HnyYje3RlD7CylZND12WwIjBO8iPrmO/lWMByYo1a06/g0ttWxdnNXz/FcaZXJQd Q5boFeysTBYh8nmk9jeEOxa0x/TnEXSUAXto/Sl+toZUughkHgksMjt+WpiGxCjqHgtg7Almv UQyZr62
Received-SPF: pass client-ip=212.227.15.19; envelope-from=julian.reschke@gmx.de; helo=mout.gmx.net
X-W3C-Hub-Spam-Status: No, score=-8.2
X-W3C-Hub-Spam-Report: AWL=1.410, BAYES_00=-1.9, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: lisa.w3.org 1bukRr-00089j-TF 37a229d8ed5e3dbf693a68c84824870c
X-Original-To: ietf-http-wg@w3.org
Subject: Re: WGLC comment on draft-ietf-httpbis-encryption-encoding-03, was: Encryption content coding simplification
Archived-At: <http://www.w3.org/mid/bc9e0fcb-03d8-5592-4388-4641d308dba3@gmx.de>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/32584
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 2016-10-13 19:46, Mike Bishop wrote:
> Well, I can point at one, though it's not exactly a model of perfect HTTP C-E integration design....  Looking at https://winprotocoldoc.blob.core.windows.net/productionwindowsarchives/MS-PCCRTP/[MS-PCCRTP].pdf, there are additional headers that carry the client's parameters (which the server will need if it chooses that coding) and then carry the server's selections back.
>
> Most notable (and probably the worst choice :-) ) is that rather than defining a new C-E value for v2, the parameters include the client's min/max supported versions, and the server tells the client which version it used in a response header.

...and SDCH will also need a way to send compression related parameters, 
right?

Best regards, Julian

v2.23.0 | Report a Bug | By Email