I only have a few comments. The use cases are certainly there, i.e. " encoding of HTTP messages that can be conveyed outside of an HTTP protocol". We have done this for a long time, in many forms but all encoded with protocol buffers <https://en.wikipedia.org/wiki/Protocol_Buffers>. I wonder if an http-wg version of "ASN.1" definition is needed here. We certainly won't switch to bhttp anytime soon, and there will likely be performance gaps too to adopt such a new encoding. When streaming is needed, a new wire protocol will likely be needed in order to tunnel bhttp. On Thu, Feb 3, 2022 at 6:29 PM Mark Nottingham <mnot@mnot.net> wrote: > This message begins Working Group Last Call for > draft-ietf-httpbis-binary-message-01, 'Binary Representation of HTTP > Messages'. > > https://datatracker.ietf.org/doc/draft-ietf-httpbis-binary-message/ > > Please read the document, raise issues if you find any, and indicate > on-list whether you support its publication. > > WGLC will end on 4 March 2022. > > Cheers, > > -- > Mark Nottingham https://www.mnot.net/ > > >Received on Saturday, 5 February 2022 17:10:54 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 5 February 2022 17:10:55 UTC