Re: Call for Adoption: Binary Representation of HTTP Messages

Willy Tarreau <w@1wt.eu> Tue, 09 November 2021 13:54 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BE35A3A0CDF for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 9 Nov 2021 05:54:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.67
X-Spam-Level:
X-Spam-Status: No, score=-2.67 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 t3cGjFArNDZX for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Tue, 9 Nov 2021 05:54:16 -0800 (PST)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7F7303A0CDC for <httpbisa-archive-bis2Juki@lists.ietf.org>; Tue, 9 Nov 2021 05:54:15 -0800 (PST)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1mkRXT-0007tC-9y for ietf-http-wg-dist@listhub.w3.org; Tue, 09 Nov 2021 13:51:51 +0000
Resent-Date: Tue, 09 Nov 2021 13:51:51 +0000
Resent-Message-Id: <E1mkRXT-0007tC-9y@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <w@1wt.eu>) id 1mkRXR-0007qZ-HI for ietf-http-wg@listhub.w3.org; Tue, 09 Nov 2021 13:51:49 +0000
Received: from wtarreau.pck.nerim.net ([62.212.114.60] helo=1wt.eu) by mimas.w3.org with esmtp (Exim 4.92) (envelope-from <w@1wt.eu>) id 1mkRXO-0004OT-NS for ietf-http-wg@w3.org; Tue, 09 Nov 2021 13:51:49 +0000
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id 1A9DpPue017836; Tue, 9 Nov 2021 14:51:25 +0100
Date: Tue, 09 Nov 2021 14:51:25 +0100
From: Willy Tarreau <w@1wt.eu>
To: Mark Nottingham <mnot@mnot.net>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, Tommy Pauly <tpauly@apple.com>
Message-ID: <20211109135125.GF16668@1wt.eu>
References: <B688530D-FB61-40CB-89D7-BCF5351817E8@mnot.net>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Disposition: inline
In-Reply-To: <B688530D-FB61-40CB-89D7-BCF5351817E8@mnot.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Received-SPF: pass client-ip=62.212.114.60; envelope-from=w@1wt.eu; helo=1wt.eu
X-W3C-Hub-Spam-Status: No, score=-7.9
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, W3C_AA=-1, W3C_IRA=-1, W3C_IRR=-3, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1mkRXO-0004OT-NS 83fc26eb4e2308b443e9e36552e94f3e
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Call for Adoption: Binary Representation of HTTP Messages
Archived-At: <https://www.w3.org/mid/20211109135125.GF16668@1wt.eu>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/39547
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

On Tue, Nov 09, 2021 at 10:17:03PM +1100, Mark Nottingham wrote:
> Hello everyone,
> 
> This draft was discussed in our last interim, and there seemed to be interest
> in adoption. Additionally, the newly formed OHAI working group has a
> dependency on it:
>   <https://datatracker.ietf.org/doc/draft-thomson-http-binary-message/>
> 
> So, this kicks off a one-week call for adoption for this draft. Please
> respond saying whether you support adoption of this draft as a work item.

For having worked on related concepts on this in the past, I think it
makes a lot of sense to try to standardize a way to reliably serialize
a message.

Thus +1 for adoption!
Willy