Re: [quicwg/base-drafts] What scheme should be used for HTTP/3? (#2384)

Mike Bishop <> Tue, 29 January 2019 05:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 7AFD4130EE8 for <>; Mon, 28 Jan 2019 21:45:42 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -11.149
X-Spam-Status: No, score=-11.149 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_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id mNvlZD0AUtE3 for <>; Mon, 28 Jan 2019 21:45:40 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id C0C72130EA4 for <>; Mon, 28 Jan 2019 21:45:40 -0800 (PST)
Date: Mon, 28 Jan 2019 21:45:39 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1548740739; bh=Ex8hmpCqI7JUGy9LZ+Ez8FLblzhaD9IirVPwmib4tSI=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=nqQq7F/mzhK3qEqbqgl2TyadsuX2bRE/45SXrANOu1Q1Im0r8MsvGqxMGAfsP+spo n/jhu3C29Ct6jWlYMtVLzly2Lh8Bbi52HS13AyBTeHyAOZZ+vX/VrGSQ23Wtm2EdVV lZvVTrBGn1cODyd/IoLNWUxu9cKNbk4mUg6z+Zz4=
From: Mike Bishop <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/2384/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] What scheme should be used for HTTP/3? (#2384)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5c4fe883da2ce_5e343fb92a6d45c012064f"; 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
Archived-At: <>
X-Mailman-Version: 2.1.29
List-Id: Notification list for GitHub issues related to the QUIC WG <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 29 Jan 2019 05:45:43 -0000

This is another variant of #253, actually.  In the current draft, H3 can *only* be used as the target from an Alt-Svc entry.  So the scheme is the scheme of whatever the origin is which gave you an H3 alternate.  That's probably https://, but it could also be http:// (see RFC 8164).

You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub: