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

Mike Bishop <notifications@github.com> Wed, 08 March 2017 18:28 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 5A2C812944E for <quic-issues@ietfa.amsl.com>; Wed, 8 Mar 2017 10:28:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 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_MSPIKE_H2=-0.001, RP_MATCHES_RCVD=-0.001, 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 jM-Kf8Pbq6Zd for <quic-issues@ietfa.amsl.com>; Wed, 8 Mar 2017 10:28:45 -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 7957312943A for <quic-issues@ietf.org>; Wed, 8 Mar 2017 10:28:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com; h=from:reply-to:to:cc:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe; s=s20150108; bh=hSbLWWvXAtiNDzU83HhOd0WjAbo=; b=ncB0bD2zBbZERC6V 9O5ZQnQM7maKfjBYSX9twHWoASOMCcajnZVjUW/izoPT8Sv/dh/A9Kb4ArRZJbBj WvMpl0lV2lG8FPK27lH1iXOc8weJZXyCFUM39EahJqfZ+W3EmU6u3+f/bOWd49kT OTmZErhr4PRa/ZxS2AEu6EVKI30=
Received: by filter0842p1mdw1.sendgrid.net with SMTP id filter0842p1mdw1-3863-58C04D59-49 2017-03-08 18:28:41.918039266 +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 ismtpd0004p1iad1.sendgrid.net (SG) with ESMTP id as750NVWRKmlwp6X4E37FA for <quic-issues@ietf.org>; Wed, 08 Mar 2017 18:28:41.910 +0000 (UTC)
Date: Wed, 08 Mar 2017 10:28:40 -0800
From: Mike Bishop <notifications@github.com>
To: quicwg/base-drafts <base-drafts@noreply.github.com>
Message-ID: <quicwg/base-drafts/issues/371@github.com>
Subject: [quicwg/base-drafts] ALTSVC Frame (#371)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_58c04d58bcbc5_6ae33fef2f30fc381735b8"; 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: l64QuQ2uJCcEyUykJbxN122A6QRmEpucztpreh3Pak0FDi5J2bZQwuUArHGUvQZJOP/c4qd17RJRnV +nnPAWWiZcixxT+siJmxX/At/zhqpU4LZZsWcSUaOv/CeBDzsD35Xm/fENr/rgttWKeOcoDPY50FFN XzzTrBpZl7XW+krrLUajVjHUW193xbLPA+7B6/KFyJHvbRT/+kMk+pN3Fhv4+x0ra2hh6oLAvGZrIv M=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic-issues/67qQF8yA9Xs-NeFHko3yuaYwL6A>
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: Wed, 08 Mar 2017 18:28:47 -0000

As @LPardue has pointed out in the thread for #242, the HTTP/QUIC spec claims to update the IANA registry for "existing" frames.  It really only updates the frames defined in RFC7540; the ALTSVC frame defined in RFC7838 isn't updated.

It would be a simple update, but the question is where it belongs.  Should we:

- Add text in this document to include that frame, because it is "existing"?
- Write a new (very short) document updating RFC7838 with HTTP/QUIC support, following the recommendations in #363?
- Kick it back to the httpbis working group to write exactly the same very short document?

Note that the latter two options probably differ by nothing but the filename of the I-D in question -- the same people will probably end up writing it.

-- 
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/371