- From: Mark Nottingham <mnot@mnot.net>
- Date: Wed, 12 Oct 2022 16:11:16 +1100
- To: HTTP Working Group <ietf-http-wg@w3.org>
- Message-Id: <803DDC53-2F03-48C8-94B0-13FCF7F0D05D@mnot.net>
FYI. I have a rough (but workable) implementation here: https://github.com/mnot/http_sfv/tree/binary-functional <https://github.com/mnot/http_sfv/tree/binary-functional> Cheers, > Begin forwarded message: > > From: internet-drafts@ietf.org > Subject: New Version Notification for draft-nottingham-binary-structured-headers-03.txt > Date: 12 October 2022 at 4:08:21 pm AEDT > To: "Mark Nottingham" <mnot@mnot.net> > > > A new version of I-D, draft-nottingham-binary-structured-headers-03.txt > has been successfully submitted by Mark Nottingham and posted to the > IETF repository. > > Name: draft-nottingham-binary-structured-headers > Revision: 03 > Title: Binary Structured HTTP Field Values > Document date: 2022-10-11 > Group: Individual Submission > Pages: 11 > URL: https://www.ietf.org/archive/id/draft-nottingham-binary-structured-headers-03.txt > Status: https://datatracker.ietf.org/doc/draft-nottingham-binary-structured-headers/ > Html: https://www.ietf.org/archive/id/draft-nottingham-binary-structured-headers-03.html > Htmlized: https://datatracker.ietf.org/doc/html/draft-nottingham-binary-structured-headers > Diff: https://www.ietf.org/rfcdiff?url2=draft-nottingham-binary-structured-headers-03 > > Abstract: > This specification defines a binary serialisation of Structured Field > Values for HTTP, along with a negotiation mechanism for its use in > HTTP/2. > > > > > The IETF Secretariat > > -- Mark Nottingham https://www.mnot.net/
Received on Wednesday, 12 October 2022 05:11:37 UTC