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

Takeshi Yoshino <tyoshino@google.com> Wed, 09 October 2013 20:59 UTC

Return-Path: <tyoshino@google.com>
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 32EC611E80D9 for <hybi@ietfa.amsl.com>; Wed, 9 Oct 2013 13:59:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.918
X-Spam-Level:
X-Spam-Status: No, score=-1.918 tagged_above=-999 required=5 tests=[AWL=0.059, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, NO_RELAYS=-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 O+6E-0-7BctF for <hybi@ietfa.amsl.com>; Wed, 9 Oct 2013 13:59:46 -0700 (PDT)
Received: from mail-we0-x22d.google.com (mail-we0-x22d.google.com [IPv6:2a00:1450:400c:c03::22d]) by ietfa.amsl.com (Postfix) with ESMTP id 49DB921E8160 for <hybi@ietf.org>; Wed, 9 Oct 2013 13:59:46 -0700 (PDT)
Received: by mail-we0-f173.google.com with SMTP id u57so1492999wes.4 for <hybi@ietf.org>; Wed, 09 Oct 2013 13:59:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=YPLFx7hN+RkwPsDnDOGrOGe4HsbXSoB2UxnI1UHDJ+Y=; b=NzSetcj2apQJYxPigKMttJBq3EzSf23LPLi7Aw76oh0pnErLynvwnFLYVqT+rQzkOK jwnjHs6AYgM/PJfh5EmJrs6ZL8WECT48GMyDS6hQl2CWchifcZJ3ZB5KTQAMAioM+WoB lzHEmHxzYAjijvxMy+Cy3Q2ALDmT8zKsss3TSMYCumyaVn2U+g6iG1+EaTi3P9UhhQ09 kkqm/izCzOiMQf8oykq/mRrVBq1wwUWFq6I99wEm3bqkkdl/eYZq9ikLd55Yqdqn6Wb1 j6QsHujDxZ7LBAGQFHWn+YWTffWeBI+lmhkAV3SOIkIG5wOCs+ROmZa7WoWjoe7mzYg3 d47w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=YPLFx7hN+RkwPsDnDOGrOGe4HsbXSoB2UxnI1UHDJ+Y=; b=Q0AueOcB0TsL4bj8viWZADLGn/3xXdKXp3hc0ofR8ACVKNAwdk8zWz8VCr/cl64+8x 5h3+W0/XzPzVQdDRpdJN8gxOFD7i6CE8mO+dxcELNwfNad5zS4pxqYG+O8NIKhcKQfnh o28A5+YzrkhQuv64ow00PavWf2SgJzHQJ0qBRJvN+ynlilWQXjTrJW26iQGouzPOhzri Bv0QoFXSm4vOd+hWnWr91r2gRWrlnaGMZkm/HQux01RXUz/OxpCCcdGL35uOTQbiHKql tD4BULGwYWfkVnqnkGZR5CDbNhQuQe+VKMV+5f4zVZ9jTQMM8hOBGRhDB8AVCUe27q/y Pziw==
X-Gm-Message-State: ALoCoQkWArkJ2lRMlygelhuWVnZwzoSa+Q7NhqDZuk75C8oTwZcOXG306ummzzlak6HYr2k5Vyh80o3D33Sm6fw1Zi+z/vm68zodIUquXBZq4Lc53BXn7KOFWxnfq30eVX0X0wYlGZB4lC1xqOvgZaa05k5yMBl6m5+TTN/c3DuvJ37cuyP27XtzaXP2GwdtMRGqgKnOWc0g
X-Received: by 10.195.13.45 with SMTP id ev13mr8617724wjd.20.1381352378287; Wed, 09 Oct 2013 13:59:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.15.133 with HTTP; Wed, 9 Oct 2013 13:59:18 -0700 (PDT)
In-Reply-To: <CAH9hSJZugsZjJ7j7EoGseT9QauQ2bApK7OcWAtirCZ6b0SHwvA@mail.gmail.com>
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>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Thu, 10 Oct 2013 05:59:18 +0900
Message-ID: <CAH9hSJZVAjUPu=6b1CsVVnCRchSGY5hN+ongpkrkVUPJVDmFgQ@mail.gmail.com>
To: Joakim Erdfelt <joakim@intalio.com>
Content-Type: multipart/alternative; boundary="047d7bfced1ed16e7004e855291a"
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: Wed, 09 Oct 2013 20:59:47 -0000

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