Re: [hybi] Call for interest: multiplexing dedicated for WebSocket

Takeshi Yoshino <tyoshino@google.com> Sun, 19 May 2013 04:31 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 B3E4721F8756 for <hybi@ietfa.amsl.com>; Sat, 18 May 2013 21:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.5
X-Spam-Level:
X-Spam-Status: No, score=-102.5 tagged_above=-999 required=5 tests=[AWL=0.476, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 pvAsGQ9o8+uR for <hybi@ietfa.amsl.com>; Sat, 18 May 2013 21:30:57 -0700 (PDT)
Received: from mail-ee0-f53.google.com (mail-ee0-f53.google.com [74.125.83.53]) by ietfa.amsl.com (Postfix) with ESMTP id 5B27921F869A for <hybi@ietf.org>; Sat, 18 May 2013 21:30:57 -0700 (PDT)
Received: by mail-ee0-f53.google.com with SMTP id c1so3027526eek.40 for <hybi@ietf.org>; Sat, 18 May 2013 21:30:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=+KX3y/jZxTVxUSYjrlxC6iqPjZlGP6O5736IXb+pBXY=; b=Pq6PgyonT1Wf5WPQWfthdOKb42En7R7Cd/o0ul01b4oK2bknyrPR4eLdwAYDL2Ookh Z0AW4ZdsoivPtmqSogAV+vRY6VIEdxTKVajp4NMbNhs2IsQI1lDUfQGN52YV7wRDO6YS j79D1Xq60b4h4MxTrKTipUM7Qar8x3YJ2QGKc/IYeTURbpEkpNJlIWCvKiijqWQ3hBPl DejzsMwKC6K0/UZQGx1wHbk9KAbMNxzrolyI9dGY9age3f3fpKDglGWin9k3ZsIG4OI9 8Gg1Zt+uiMDn3ZRLQSw/OHProFE/WTFSGk5NU/aK2yLwqjljajDUDRgomO7kyuyGqg12 +znw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:in-reply-to:references:from:date:message-id :subject:to:content-type:x-gm-message-state; bh=+KX3y/jZxTVxUSYjrlxC6iqPjZlGP6O5736IXb+pBXY=; b=J8YT7StLnn7QZUNUGzQxuzujYa1QD5ykvVrw9OnEk4pXEqkqB3Vn3bgEbnGk5PKUHr 8z/KAUsq+VEHBgySn2ynCqerPkPtHBoKzvpzocvw8wVj6cB51RA0UgUK+sT2fBcnuzo0 zMeS0t8NYWlcgp6xlSPpWtZy4k12u3qmhWeen13Jmp/ukIgOhECGlIbd6l9CkWieXhFC zUKURF9CbdWci7KE5N9BQMjfwxNf8IRZDkPK6uSucDnLi3B3u8KefjdxKNnuSf7GICh/ jyiq8rLaP4DWMMF5YYa858g8yUODb7Hg8NzbZLKAZU7pQ+KBejZVgpawsKz11ugriEqw yaOw==
X-Received: by 10.14.172.195 with SMTP id t43mr7786808eel.34.1368937856258; Sat, 18 May 2013 21:30:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.85.152 with HTTP; Sat, 18 May 2013 21:30:36 -0700 (PDT)
In-Reply-To: <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com>
References: <CAH9hSJZxr+aG7GZa4f-dUOTGj4bnJ+3XxivUX4jei5CMyqN4LQ@mail.gmail.com> <CAH9hSJZUG1f+3Uk=t2=A5i4O9=wPvAisspM=pgmGEH9emTL9-Q@mail.gmail.com>
From: Takeshi Yoshino <tyoshino@google.com>
Date: Sun, 19 May 2013 13:30:36 +0900
Message-ID: <CAH9hSJZai_UuxW4O6mZcEJT2DJoURtLo16XNci1qkYVWv4HVdg@mail.gmail.com>
To: "hybi@ietf.org" <hybi@ietf.org>
Content-Type: multipart/alternative; boundary=047d7b621ee6a48a1904dd0aae14
X-Gm-Message-State: ALoCoQkNxL5651Vr9ZYZgSZzawezjrf2pTitLh5Q0EEZdmKoD9eS5COmMnko5IafzPYepZjhEIOoNN+jFBnhsnbMSXkQQFEQfaSkf9pR7eOyVl4R82nYDanlOv3VEwASrLX4r/hNd3ZpNlA+fYkYv6VIpWB9kPrptewzIhGEt37AvNfGEo/QtvWV9CZI8oubngGR45caflx2
Subject: Re: [hybi] Call for interest: multiplexing dedicated for WebSocket
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, 19 May 2013 04:31:02 -0000

I got one comment about this.

He/she suggested that we finish the WebSocket dedicated multiplexing
quickly even by simplifying the spec much e.g. cutting some functionality
in it that would take much time to get consensus, and when HTTP/2.0 is
matured, switch to that.