Re: [hybi] permessage-deflate and missing asymmetric configurations

Tobias Oberstein <tobias.oberstein@tavendo.de> Sun, 13 October 2013 08:18 UTC

Return-Path: <tobias.oberstein@tavendo.de>
X-Original-To: hybi@ietfa.amsl.com
Delivered-To: hybi@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F1EFE21F9A97 for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:18:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[AWL=-0.000, BAYES_00=-2.599, HTML_MESSAGE=0.001]
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 zeSfKOJHXZqI for <hybi@ietfa.amsl.com>; Sun, 13 Oct 2013 01:18:46 -0700 (PDT)
Received: from EXHUB020-1.exch020.serverdata.net (exhub020-1.exch020.serverdata.net [206.225.164.28]) by ietfa.amsl.com (Postfix) with ESMTP id DF1B921F8E3D for <hybi@ietf.org>; Sun, 13 Oct 2013 01:18:42 -0700 (PDT)
Received: from EXVMBX020-12.exch020.serverdata.net ([169.254.3.240]) by EXHUB020-1.exch020.serverdata.net ([206.225.164.28]) with mapi; Sun, 13 Oct 2013 01:18:41 -0700
From: Tobias Oberstein <tobias.oberstein@tavendo.de>
To: Takeshi Yoshino <tyoshino@google.com>, Joakim Erdfelt <joakim@intalio.com>
Date: Sun, 13 Oct 2013 01:18:40 -0700
Thread-Topic: [hybi] permessage-deflate and missing asymmetric configurations
Thread-Index: Ac7FMoDlKEBnqcHQRW6LFMPigXhxzQCuaxMA
Message-ID: <634914A010D0B943A035D226786325D44469B06662@EXVMBX020-12.exch020.serverdata.net>
References: <CAG4zZZAqGcVP=4P9qfo2Gm3fbPHKntwZ5aF=hDePccfKnD4kWQ@mail.gmail.com> <02030518-6F55-4E50-9AB8-06C7540C8AE1@zaphoyd.com> <CAG4zZZCYkuQx40zn-wUBoeSecJ-NTDku-nD5-gkSSy-A1vhxNQ@mail.gmail.com> <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com> <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
In-Reply-To: <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: de-DE, en-US
Content-Type: multipart/alternative; boundary="_000_634914A010D0B943A035D226786325D44469B06662EXVMBX02012ex_"
MIME-Version: 1.0
Cc: "hybi@ietf.org" <hybi@ietf.org>, Peter Thorson <webmaster@zaphoyd.com>
Subject: Re: [hybi] permessage-deflate and missing asymmetric configurations
X-BeenThere: hybi@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Server-Initiated HTTP <hybi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/hybi>, <mailto:hybi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/hybi>
List-Post: <mailto:hybi@ietf.org>
List-Help: <mailto:hybi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/hybi>, <mailto:hybi-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 13 Oct 2013 08:18:52 -0000

my vote: -1 for those new parameters.

IMHO they are not needed: an endpoint can choose to not compress (an individual or all) messages anyway without any negotiation needed - it can also discard context even when context takeover was negotiated and choose less window bits than negotiated.

In essence, the negotiation only needs to establish _upper bounds_ on resource consumption (memory) within endpoints. Hence, context takeover and window bits.

/Tobias

Von: hybi-bounces@ietf.org [mailto:hybi-bounces@ietf.org] Im Auftrag von Takeshi Yoshino
Gesendet: Mittwoch, 9. Oktober 2013 22:59
An: Joakim Erdfelt
Cc: hybi@ietf.org; Peter Thorson
Betreff: Re: [hybi] permessage-deflate and missing asymmetric configurations

If we introduce the feature it'll be like this. We add new parameters, say, server_no_compress and client_no_compress.

- client MAY request server_no_compress
- client MAY send a hint client_no_compress
- server MAY respond with client_no_compress
- server MUST respond with server_no_compress if received it from client

- client MUST NOT include server_no_compress together with other server_ parameters
- server MUST NOT include server_no_compress together with other server_ parameters
- server MUST NOT include client_no_compress together with other client_ parameters