IETF Logo Mail Archive

Re: [quicwg/base-drafts] Define "httpq" (#348)

Mike Bishop <notifications@github.com> Mon, 27 February 2017 05:57 UTC

Return-Path: <bounces+848413-a050-quic-issues=ietf.org@sgmail.github.com>
X-Original-To: quic-issues@ietfa.amsl.com
Delivered-To: quic-issues@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BCDC3129B24 for <quic-issues@ietfa.amsl.com>; Sun, 26 Feb 2017 21:57:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.383
X-Spam-Level:
X-Spam-Status: No, score=-0.383 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_24=1.618, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QMbg44e47tOo for <quic-issues@ietfa.amsl.com>; Sun, 26 Feb 2017 21:57:36 -0800 (PST)
Received: from o4.sgmail.github.com (o4.sgmail.github.com [192.254.112.99]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DA7FE129B1C for <quic-issues@ietf.org>; Sun, 26 Feb 2017 21:57:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=kTXkTCJLVPkE2Gs9NpYbPMgIaR0=; b=ryEvTbxVY16YIruN xLIIZfPorQO/uya0yN4NGmZnDA4rY+hSyhaM4Npjn8n767ayHqjIb6yETJsB3rz1 af7BY+Z8H57zJzlRjImF11+eKQ9f5tQkNrz6sMfxv+mD49I7WQ+5a66lxj9YTXdZ EU9pjHpp9iZ3SitKiIBg0ZmrPhM=
Received: by filter0232p1las1.sendgrid.net with SMTP id filter0232p1las1-14176-58B3BFD0-15 2017-02-27 05:57:36.40800631 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [192.30.253.16]) by ismtpd0005p1iad1.sendgrid.net (SG) with ESMTP id jv6h71j-Rsayr9m_Se3hCQ for <quic-issues@ietf.org>; Mon, 27 Feb 2017 05:57:36.109 +0000 (UTC)
Date: Sun, 26 Feb 2017 21:57:36 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/pull/348/c282634922@github.com>
In-Reply-To: <quicwg/base-drafts/pull/348@github.com>
References: <quicwg/base-drafts/pull/348@github.com>
Subject: Re: [quicwg/base-drafts] Define "httpq" (#348)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58b3bfd09445_4d163fa4dda85c342862c0"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: MikeBishop
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address: quic-issues@ietf.org
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak3WxGKuK8KBN7cNxMVmeeyYEUE/6EUkHXo6Se BcuY/kGApjCgIAphSqvMWxXQsUzx0FnWBtrTTskrETABpAQdjGW3P8SMMQT/JBXrGKpnPcfTPzrSRH UiMC8DaOSdlUXghauqTl3mP3jdbGPWnUdn+arFMydW+Yg8R2Zg7xbfRkmtTEkTiDCZQL5lIh7KmWkO w=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/NFo6DnUKqo0J8BKXnoX98PwS9_E>
Cc: Subscribed <subscribed@noreply.github.com>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.17
Reply-To: quic@ietf.org
List-Id: Notification list for GitHub issues related to the QUIC WG <quic-issues.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic-issues/>
List-Post: <mailto:quic-issues@ietf.org>
List-Help: <mailto:quic-issues-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic-issues>, <mailto:quic-issues-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 27 Feb 2017 05:57:37 -0000

I don't see any way in which this could be deployed to the WWW in any reasonable timescale -- which is not the same as saying it wouldn't work in a browser.  A browser accessing a dedicated service which runs over QUIC seems very feasible.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/quicwg/base-drafts/pull/348#issuecomment-282634922

v2.46.0 | Report a Bug | By Email | System Status