Re: [quicwg/base-drafts] http: syntax fixes for quic Alt-Svc parameter (#3059)

Peter Wu <> Mon, 23 September 2019 23:39 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id B7822120047 for <>; Mon, 23 Sep 2019 16:39:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.495
X-Spam-Status: No, score=-6.495 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_IMAGE_ONLY_28=1.404, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RRfi3MaQXehA for <>; Mon, 23 Sep 2019 16:39:18 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id E3C66120045 for <>; Mon, 23 Sep 2019 16:39:17 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 618642603B7 for <>; Mon, 23 Sep 2019 16:39:17 -0700 (PDT)
Date: Mon, 23 Sep 2019 16:39:17 -0700
From: Peter Wu <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/pull/3059/>
In-Reply-To: <quicwg/base-drafts/pull/>
References: <quicwg/base-drafts/pull/>
Subject: Re: [quicwg/base-drafts] http: syntax fixes for quic Alt-Svc parameter (#3059)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5d8957a51a892_45883fde0cecd96478628"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: Lekensteyn
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: Mon, 23 Sep 2019 23:39:20 -0000

I can remove the additional unquoted token change and keep this PR purely as editorial fix. Before the PR, the current text does not have correct ABNF grammar.

I added the unquoted token variant since it is permitted (but not required) by the grammar at
>    parameter     = token "=" ( token / quoted-string )

Since HTTP/3 over QUIC is not the only user of this Alt-Svc header, I can imagine that generic parsers are written such that they already understand the unquoted token value. Thus, adding support for this should not be an additional burden?

I have no strong opinion here. The additional CPU cost of handling both unquoted and quoted forms should be neglible. Disallowing the unquoted form is a restriction of the RFC 7838 grammar.

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