Re: [quicwg/base-drafts] What scheme should be used for HTTP/3? (#2384)
Mike Bishop <notifications@github.com> Thu, 31 January 2019 06:23 UTC
Return-Path: <noreply@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 157361288BD for <quic-issues@ietfa.amsl.com>; Wed, 30 Jan 2019 22:23:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.007
X-Spam-Level:
X-Spam-Status: No, score=-11.007 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_IMAGE_ONLY_20=1.546, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham 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 6jQ3kM7C9oFZ for <quic-issues@ietfa.amsl.com>; Wed, 30 Jan 2019 22:23:39 -0800 (PST)
Received: from out-2.smtp.github.com (out-2.smtp.github.com [192.30.252.193]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 61766130EB0 for <quic-issues@ietf.org>; Wed, 30 Jan 2019 22:23:38 -0800 (PST)
Date: Wed, 30 Jan 2019 22:23:37 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1548915817; bh=10aQjJwRvPckjAWa/PKw+ZW81ex+3hrFarfXO4AqFoI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=zIRlFpl+DLVlHnqVYFshFrTdbv2LZ+LLlmvG1TI067kiBocWV80ce1+f3+5wPeCW2 wKj/nQ3cLPyhlPVbl9xdFKmTjRHqraJvyma4aI+atvdMPtGLd1LlbIqYQl0b+kMVca qhh9qcfo2TxXBv4cVKC6mBo6mRAvBb4CcQkdNKwE=
From: Mike Bishop <notifications@github.com>
Reply-To: quicwg/base-drafts <reply+0166e4ab4b668591940fa3728047f3d0cb54aca0d094349092cf00000001186a566992a169ce18168909@reply.github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Cc: Subscribed <subscribed@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/2384/459230638@github.com>
In-Reply-To: <quicwg/base-drafts/issues/2384@github.com>
References: <quicwg/base-drafts/issues/2384@github.com>
Subject: Re: [quicwg/base-drafts] What scheme should be used for HTTP/3? (#2384)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c5294693b8c4_2f253fa2ca0d45c42947a2"; 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
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/s_F1wfjArae6eF70IqUc5IV0F3U>
X-BeenThere: quic-issues@ietf.org
X-Mailman-Version: 2.1.29
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: Thu, 31 Jan 2019 06:23:43 -0000
Discussed in Tokyo; this is out-of-scope for QUIC and needs to be resolved by the HTTP WG. -- 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/issues/2384#issuecomment-459230638
- [quicwg/base-drafts] What scheme should be used f… Masaori Koshiba
- Re: [quicwg/base-drafts] What scheme should be us… Mike Bishop
- Re: [quicwg/base-drafts] What scheme should be us… Mike Bishop
- Re: [quicwg/base-drafts] What scheme should be us… Mike Bishop