Re: [quicwg/base-drafts] Add capability for sending HTTP metadata (trailer fields) in mid-stream (#3265)

"Roy T. Fielding" <> Thu, 23 April 2020 15:40 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1ADBA3A0AAD for <>; Thu, 23 Apr 2020 08:40:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.008
X-Spam-Status: No, score=-2.008 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_IMAGE_ONLY_16=1.092, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, SPF_HELO_NONE=0.001, 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 2b3h2WRSIWN7 for <>; Thu, 23 Apr 2020 08:40:04 -0700 (PDT)
Received: from ( []) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 04B4E3A0AAE for <>; Thu, 23 Apr 2020 08:40:03 -0700 (PDT)
Received: from ( []) by (Postfix) with ESMTP id 505296E1F82 for <>; Thu, 23 Apr 2020 08:40:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=pf2014; t=1587656403; bh=/77MgINwRPBFgGy6ryFozUN+zDCRtgVp8qbKeSqu/5A=; h=Date:From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID: List-Archive:List-Post:List-Unsubscribe:From; b=cqUoZXhuUe9/hBXqVsj43cDzCDU9H7L1f3F1P8SOUUEzcI605SSZFbHEEkfd8/Ec4 8f8B9Q2EnaWuXYYQXHWx2PDubt+4F9iAwMvPor8iATzzTSkTMM9If8gQAr9YCqzV1N gZutDR9h4IvFJMc2+UXKZSaRLxKz0ixaJGCZTyMg=
Date: Thu, 23 Apr 2020 08:40:03 -0700
From: "Roy T. Fielding" <>
Reply-To: quicwg/base-drafts <>
To: quicwg/base-drafts <>
Cc: Subscribed <>
Message-ID: <quicwg/base-drafts/issues/3265/>
In-Reply-To: <quicwg/base-drafts/issues/>
References: <quicwg/base-drafts/issues/>
Subject: Re: [quicwg/base-drafts] Add capability for sending HTTP metadata (trailer fields) in mid-stream (#3265)
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="--==_mimepart_5ea1b6d341505_40883fa485acd96016111f"; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: royfielding
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: Thu, 23 Apr 2020 15:40:05 -0000

The discussion in HTTP was entirely positive and there is already a non-IETF spec for it as an extension to h2, but that was in Singapore and nobody has had time to work on it since. The http-core specs already allow for it. h2 is not under revision. The only bits it requires in HTTP/3 is a frame type and some expectation of what to do with it (i.e., it contains fields, treat them as optional trailers, done).

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