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

Pablo <paa.listas@gmail.com> Sun, 20 January 2013 22:22 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 B7C0C21F87FB for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Jan 2013 14:22:23 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.999
X-Spam-Level:
X-Spam-Status: No, score=-7.999 tagged_above=-999 required=5 tests=[HTML_MESSAGE=0.001, 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 o9OSLbtGYXzQ for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 20 Jan 2013 14:22:23 -0800 (PST)
Received: from frink.w3.org (frink.w3.org [128.30.52.56]) by ietfa.amsl.com (Postfix) with ESMTP id 042D521F87FA for <httpbisa-archive-bis2Juki@lists.ietf.org>; Sun, 20 Jan 2013 14:22:19 -0800 (PST)
Received: from lists by frink.w3.org with local (Exim 4.72) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1Tx3G5-00032w-OC for ietf-http-wg-dist@listhub.w3.org; Sun, 20 Jan 2013 22:20:57 +0000
Resent-Date: Sun, 20 Jan 2013 22:20:57 +0000
Resent-Message-Id: <E1Tx3G5-00032w-OC@frink.w3.org>
Received: from lisa.w3.org ([128.30.52.41]) by frink.w3.org with esmtp (Exim 4.72) (envelope-from <paa.listas@gmail.com>) id 1Tx3G0-00032B-VQ for ietf-http-wg@listhub.w3.org; Sun, 20 Jan 2013 22:20:52 +0000
Received: from mail-ob0-f177.google.com ([209.85.214.177]) by lisa.w3.org with esmtps (TLS1.0:RSA_ARCFOUR_SHA1:16) (Exim 4.72) (envelope-from <paa.listas@gmail.com>) id 1Tx3G0-00073d-70 for ietf-http-wg@w3.org; Sun, 20 Jan 2013 22:20:52 +0000
Received: by mail-ob0-f177.google.com with SMTP id wc20so4528380obb.22 for <ietf-http-wg@w3.org>; Sun, 20 Jan 2013 14:20:26 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=STBWKg139AJVThomMcMfdLdkRnd9i+TaOh+dKjxTS38=; b=vVFI63eMn73xk0XpX+ZEEXo8DE6zHqMbJKILK20EVw4bWk3vyTp9k7dMtuJkYEfpwD UzdqTP2lfprDPWGDVRNZj95MFm0E7Rndp3APDLvFn+BL2VspuqyB5Wx35zT9pKP1oc1p 7sqW7M56fZf3DpW5mh7/eVjwQ7hLiOieFI2QTrA3VLXAQLmX8jfiMSxpszjyH5Ijizvv WN4P0V+GgHOUT4Z+JesWA8lDq1b3zX6bo9ds+g68XpsgG1on+Ntp7NY5VVA/BP6j0wUS aQ2z+mQFtuJmGiaUgnw5YU1YUj5v1VxjAHJJqsUeYuH0lI6q36kcD717Jk08+wzWoKbw OjDA==
MIME-Version: 1.0
X-Received: by 10.182.182.101 with SMTP id ed5mr12529018obc.23.1358720426076; Sun, 20 Jan 2013 14:20:26 -0800 (PST)
Received: by 10.182.17.4 with HTTP; Sun, 20 Jan 2013 14:20:25 -0800 (PST)
Date: Sun, 20 Jan 2013 19:20:25 -0300
Message-ID: <CAAZO4q4vEiYhH5FaX2XCxXox9jkf4dLTy8coQZiE+CYHA-QzBg@mail.gmail.com>
From: Pablo <paa.listas@gmail.com>
To: ietf-http-wg@w3.org
Content-Type: multipart/alternative; boundary="14dae9399b1958685a04d3bfc0f4"
Received-SPF: pass client-ip=209.85.214.177; envelope-from=paa.listas@gmail.com; helo=mail-ob0-f177.google.com
X-W3C-Hub-Spam-Status: No, score=-1.8
X-W3C-Hub-Spam-Report: AWL=0.936, BAYES_00=-1.9, 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 1Tx3G0-00073d-70 eb6dae0547b75c669df8de38918a8d17
X-Original-To: ietf-http-wg@w3.org
Subject: The use of binary data in any part of HTTP 2.0 is not good
Archived-At: <http://www.w3.org/mid/CAAZO4q4vEiYhH5FaX2XCxXox9jkf4dLTy8coQZiE+CYHA-QzBg@mail.gmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/16044
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>

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/