IETF Logo Mail Archive

Re: The use of binary data in any part of HTTP 2.0 is not good

William Chan (陈智昌) <willchan@chromium.org> Sun, 20 January 2013 22:38 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 53B8F21F8801 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Jan 2013 14:38:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.078
X-Spam-Level:
X-Spam-Status: No, score=-7.078 tagged_above=-999 required=5 tests=[FM_FORGED_GMAIL=0.622, MIME_8BIT_HEADER=0.3, 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 IyjV9o1r61iI for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Jan 2013 14:38:22 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 8C96021F87FF for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 20 Jan 2013 14:38:21 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Tx3W5-0000af-A4 for ietf-http-wg-dist@listhub.w3.org; Sun, 20 Jan 2013 22:37:29 +0000
Resent-Date: Sun, 20 Jan 2013 22:37:29 +0000
Resent-Message-Id: <E1Tx3W5-0000af-A4@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <willchan@google.com>) id 1Tx3Vz-0000Zz-H1 for ietf-http-wg@listhub.w3.org; Sun, 20 Jan 2013 22:37:23 +0000
Received: from mail-qc0-f181.google.com ([209.85.216.181]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <willchan@google.com>) id 1Tx3Vy-0007UG-UR for ietf-http-wg@w3.org; Sun, 20 Jan 2013 22:37:23 +0000
Received: by mail-qc0-f181.google.com with SMTP id x40so3426332qcp.40 for <ietf-http-wg@w3.org>; Sun, 20 Jan 2013 14:36:57 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8m9BT05HVtCU4MAzb5697m5HARbatXl8nlX50sP8vaM=; b=JX+5xFHkOUXIufOVOjzLYYcJPsC4Vopbo96qaletLGEIpy37QjLMQ1MVngI0YSZeCR oZXWG9daEv0iNY23baZgZ55OGBgA0jztzLJBW8+rcWIoRKf1v/KzhqGoq9lkyo7kUIoH 1ieugEH7o6Yko7z4pLgXKltd9Hq17RLa+AILkVjVLfU18Tk3nqtyCv45kMttISb5WrZH X3L4hcmyUzsPhdRucdpSe7iayU9LrfinLxYee5jymy0o7inEjdo9L9xwaYqzOW+WWNzi IEZPkBtpjwSFgFnctJVsJTImh7QwNluYa3guNdbed+Yy/TGOXDpFfYb+PlNlJ7Luo4i3 5tuA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=8m9BT05HVtCU4MAzb5697m5HARbatXl8nlX50sP8vaM=; b=fHGBP36bf/4X+QEPk24pzoyZkESMt0uKFIPwDmgUhins4D97qEyJT4jOm1pVoYMWqE lWKHgaiwWjxm9TpyLWPaPpOh9YggEpKfFVaI7ea91kh6UahPUNP0C1CBcBWW1jl310R+ o3MoYDpBQw8FITHB83B4BXGbFBy770Gfzx230=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :x-gm-message-state; bh=8m9BT05HVtCU4MAzb5697m5HARbatXl8nlX50sP8vaM=; b=bRoDVXmfAn7ANrq8eC8fD5e+u+wWNWAmdIELZWSSOV6N3UrAag2MmgXQkUbgB9Xpai 1cHSlGlPxqnKlavRPK0676Lcp4iFrBDeQ7/ka88ctH00muN5SrEtrjdEgt+5xhF35aXl IcFf2ESvuMGHrg3Zl6SF0bNp+JOJuza8EcFnjnq2dY67hBZZmFOwWd2rGxFUh/mK9Wvf cL6a0SkOUmuh6IGvaYhv62WvY46CwrzXZiTc4jvs/T1CKEMECVaiBYzhPiwYM0gmtoGQ mOnHv/4XG9dABewy3ETseX5swWGu2zrUbniSQDdCjXmLkgUw1ozJ+qbS0G+sznp0YogS PS0w==
MIME-Version: 1.0
X-Received: by 10.229.179.23 with SMTP id bo23mr496270qcb.104.1358721416879; Sun, 20 Jan 2013 14:36:56 -0800 (PST)
Sender: willchan@google.com
Received: by 10.229.57.163 with HTTP; Sun, 20 Jan 2013 14:36:56 -0800 (PST)
In-Reply-To: <CAAZO4q4vEiYhH5FaX2XCxXox9jkf4dLTy8coQZiE+CYHA-QzBg@mail.gmail.com>
References: <CAAZO4q4vEiYhH5FaX2XCxXox9jkf4dLTy8coQZiE+CYHA-QzBg@mail.gmail.com>
Date: Sun, 20 Jan 2013 14:36:56 -0800
X-Google-Sender-Auth: Yq4VzpXYuajdUFRPfjOM3lrOZSo
Message-ID: <CAA4WUYhkVBRAyY1O32aOiWB8=46SBidFOjKH+e7PGbB7mKzmiQ@mail.gmail.com>
From: "William Chan (陈智昌)" <willchan@chromium.org>
To: Pablo <paa.listas@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="ISO-8859-1"
X-Gm-Message-State: ALoCoQny2Ouw+rjQ4RvKjYfy4cOmpfvJJKAO10xH1FphyVs71aZh+X9UtJdd7P0NLX47hgxpGwmCFCXn73j/cOlsfIwbkXfDMg1EL2SiIQb0jBlpWlf+J6BxZxZdGMdQERx+V6LRNXRKBWYUw9tpagUhqyxtGvS9902s/TBRTceheE60MedwZJ4MILWn0fOPgQToCyExPg2f
Received-SPF: pass client-ip=209.85.216.181; envelope-from=willchan@google.com; helo=mail-qc0-f181.google.com
X-W3C-Hub-Spam-Status: No, score=-4.5
X-W3C-Hub-Spam-Report: AWL=-1.822, BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001
X-W3C-Scan-Sig: lisa.w3.org 1Tx3Vy-0007UG-UR 484cb5d7f5e5bed8df8213a712c186a5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: The use of binary data in any part of HTTP 2.0 is not good
Archived-At: <http://www.w3.org/mid/CAA4WUYhkVBRAyY1O32aOiWB8=46SBidFOjKH+e7PGbB7mKzmiQ@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16046
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>

There are many advantages to using binary data. If you would like a
textual representation of a protocol, I advise using a utility to
generate one for you.

On Sun, Jan 20, 2013 at 2:20 PM, Pablo <paa.listas@gmail.com> wrote:
> Hello,
>
>    I have readed this document
> http://dev.chromium.org/spdy/spdy-protocol/spdy-protocol-draft1 today [1].
>
> I just wanted to say that I think that the use of any binary data (framing,
> header compression, etc.) in any place of the "header" part of HTTP protocol
> is not good; so, please only use plaintext for HTTP 2.0 because, otherwise,
> that will make very difficult to "see" the headers's protocol :)
>
> Thats all,
> Thanks for reading this few lines, sorry for my basic English, and I hope
> that you can re-think all this of using binary data in any part of HTTP X.X
> (ej: session layer).
>
>
> [1] I started knowing about HTTP 2.0 here:
> http://webscannotes.com/2012/10/09/http-2-0-officially-in-the-works/
>

v2.23.0 | Report a Bug | By Email