Re: [quicwg/base-drafts] ALTSVC Frame (#371)

Lucas Pardue <> Wed, 08 November 2017 15:45 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 6B268127876 for <>; Wed, 8 Nov 2017 07:45:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.019
X-Spam-Status: No, score=-2.019 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_32=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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 4zgOVJhyyxzp for <>; Wed, 8 Nov 2017 07:45:09 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id D17D3127843 for <>; Wed, 8 Nov 2017 07:45:08 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed;; 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=iCwZ5HieeauMT8zHxQegHVfAStg=; b=rBgsuvWbG6BpQFXn pqJkTt2qH03NeA5trAAMm9VDuHQkPkCmPJHonLngHlztAMLiZj66NccMlaAGI5O5 xLyT6/vSk61x4ThVRCPeCLMEvKz2fwKotTfAf5njbFuJgsYvsOnLuf5Sa+/DBT+h HHR+ZkKKuQVHbyrUDE7fS6/pK+s=
Received: by with SMTP id filter0463p1iad2-13770-5A032683-19 2017-11-08 15:45:07.844038392 +0000 UTC
Received: from ( []) by (SG) with ESMTP id RULH0fPZQ4KB4zMDu0QE4Q for <>; Wed, 08 Nov 2017 15:45:07.759 +0000 (UTC)
Date: Wed, 08 Nov 2017 15:45:08 +0000
From: Lucas Pardue <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/371/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] ALTSVC Frame (#371)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5a032683a3303_44ef3fee95846f3493730"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: LPardue
X-GitHub-Recipient: quic-issues
X-GitHub-Reason: subscribed
X-Auto-Response-Suppress: All
X-SG-EID: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak1WKssv6Bu5U1CDCyfwqcL4BmQIYXaENOS+6H 78ieiodmTziQnat4OkFxTduPdPbdT/XMyN12aU9GNcgfd0YBM/2OqnjNtRpKKrtuurAQJ8yaZs0sf1 3vABLGLzytz1U3OFHYdUPebyU5zo3gQ5XnCOmCfvnOsd/CZoqI9HUDxlIwv7nOEy/52FVIBR4oGFkh 4=
Archived-At: <>
X-Mailman-Version: 2.1.22
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: Wed, 08 Nov 2017 15:45:10 -0000

ALTSVC frame support came up in a recent conversation and it took me a bit of time to remember that this issue (and the @MikeBishop draft) existed. 

Would it make sense to adopt the document as part of the QUIC WG activity? Or perhaps incorporate the text into draft-ietf-quic-http.

I fear there may be some intellectual interop problems when talking about ALTSVC. For example with draft-ietf-quic-http we describe how ALTSVC can be used to discover HTTP/QUIC but only really for H2 connections prior to HTTP/QUIC, you can't use ALTSVC frames inside a HTTP/QUIC connection unless you're aware that the QUIC extension frame exists. 

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