Standardization process for TUS

[ioggstream]

Standardization process for TUS

[Acconut]

We have joined the HTTPWG Slack (https://httpwg.slack.com/) to start the discussion for a proposal about resumable uploads. Feel free to join as well, if you want to.

[Acconut]

Thank you for helping to initialize this, @ioggstream! Resumable uploads are being discussed in the HTTP WG since some time now: https://datatracker.ietf.org/doc/draft-ietf-httpbis-resumable-upload/

[kvz]

Hi there, do you have experience with this? We're open to this and are in fact talking about this with a few people. Perhaps we should form a little steering group to make this happen.

[ioggstream]

I have a basic experience in writing internet draft, and I'm currently working on the Digest spec. I landed here while discussing httpwg/http-extensions#1005

I think the first step would be to join the httpwg mailing list and check if somebody is interested in reading/reviewing the spec (I am, for now).

Here's the guide to http contribution
and the mailing list.

[Acconut]

Thanks for the insights, @ioggstream! This is all a bit of new territory for us, so I am going to need some time to understand what's exactly necessary. Expect an update in a few days!

[Acconut]

FYI, moved this issue into the more appropriate repository.

[ioggstream]

Hi @Acconut, we've recently launched a new IETF workgroup for standardizing HTTP API Building Blocks. The mailing list is here https://www.ietf.org/mailman/listinfo/httpapi You're welcome to join and present us TUS :)

[Acconut]

@ioggstream Thank you for invitation and apologies for my late reply! I would love to check it out but could you briefly explain what the working group is about (or provide some links with more details about your efforts)? That would help a lot :)

[ioggstream]

The workgroup charter is here https://datatracker.ietf.org/wg/httpapi/about/

Its output can include the following:
• Specifications for HTTP extensions that relate to HTTP APIs (typically, new HTTP header and/or trailer fields)
• Specifications for new message body formats, or conventions for their use in HTTP APIs (e.g., patterns of JSON objects)
• Best practices and other documentation for HTTP API designers, consumers, implementers, operators, etc.

[ioggstream]

Thanks!