Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges

I support the WG adopting the document, with the understanding that the
WG will soon consider making the kinds of significant changes that we
discussed in IETF 110 (e.g., #617, #618, #619 in Jeffrey's GitHub repo,
and possibly a corresponding name change from "Web Bundles" to "bundled
responses").

As for use cases and privacy/security analysis: I have a fairly
different set of use cases in mind compared to Jeffrey's use cases
document. I've tried to write about these, including implications for
privacy, at https://github.com/WICG/resource-bundles (though based on
recent feedback, I'm planning on making significant changes). However,
as Martin has pointed out, this repository is a bit wordy and not quite
to the point of what is relevant for IETF. If someone could suggest some
examples to follow on how to write these documents, I can work on them
in the coming months.

Is it OK for the WG to adopt just the main document for now, with the
goal to draft and adopt those other supporting documents in the coming
months, well before sending it all off to IESG?

Dan

On 2021-03-16 01:53, Sean Turner wrote:
> Based on interest expressed at IETF 110, this email starts the call
> for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be
> found here:
> 
>   https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/
> 
> This adoption call will run until March 30, 2021 at 2359 UTC. Please
> indicate whether or not you would like to see this I-D adopted as a WG
> item. Note that this is an adoption call for the draft as a starting
> point for the bundle format.
> 
> Thanks,
> 
> spt (for the chairs)
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org
> https://www.ietf.org/mailman/listinfo/wpack