- From: Yusuf Motiwala <yusuf@mesibo.com>
- Date: Mon, 29 Dec 2025 11:39:06 +0530
- To: ietf-http-wg@w3.org
- Message-ID: <CALHxHc9QY=wW7K8DkGqVZDV9N6vrbsU-PN5vpbw=NfBEdrD7gw@mail.gmail.com>
Hi all, I am following up on my earlier message regarding draft-motiwala-consolidated-multipart-params-00, sent a few weeks ago. I wanted to check whether the Working Group would like to proceed with a discussion or an adoption call, or if there is a different procedure I should follow at this stage. Any guidance would be appreciated. Thanks, Yusuf On Wed, Dec 3, 2025 at 7:57 PM Yusuf Motiwala <yusuf@mesibo.com> wrote: > Hi all, > > I would like to request Working Group consideration of > draft-motiwala-consolidated-multipart-params-00: > > > https://datatracker.ietf.org/doc/draft-motiwala-consolidated-multipart-params/ > > The draft describes an efficiency pattern for multipart/form-data > uploads where multiple text parameters are combined into a single > application/x-www-form-urlencoded part. This reduces the parameter > overhead by 45–60% in production deployments while remaining fully > compatible with RFC 7578. > > Key properties: > - Uses only existing, standardized media types > - Requires no protocol changes or extensions > - Fully backward compatible (non-aware servers treat it as standard form > data) > - Deployed in production for over two years, with high-volume uploads > > RFC 7578 defines multipart/form-data but does not address efficiency > considerations for parameter-heavy forms. This document fills that gap > by specifying a standards-compliant pattern already permitted by MIME > and HTTP. > > I believe this fits within the HTTPBIS scope, and I am willing to > continue as editor. Feedback and comments are welcome. > > Thanks, > Yusuf Motiwala > >
Received on Monday, 29 December 2025 06:09:23 UTC