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

[Daniel Ehrenberg <[e-mail]>]

I'd have an easier time supporting the adoption of the use cases
document if it did not prioritize use cases which depend on signed
bundles. Maybe we should split the use cases document, and produce one
which focuses only on unsigned bundle use cases and requirements. This
could clarify the more limited issues in terms of privacy and security
for the unsigned case. In addition to expressing the importance of
subresource loading, I'd add further use cases which are not currently
reflected (around tooling and serving conventions, which may have the
biggest developer experience impact, even if it's not something that
clients will receive directly).

I will be happy to draft these proposals for changes, though it will
probably take me a few months to find the time to do so properly. I'd
like to learn more about how to write the kinds of use case documents
that IETF tends to produce. Could anyone recommend any examples to
reference?

Thanks,
Dan

On 2021-03-22 22:57, Jeffrey Yasskin wrote:
> My understanding of the charter discussion was that we expected to
> need separate documents on privacy and security because
> signing-as-other-origins has such a big effect on the web origin
> model. It could make sense to hold up adoption of the signing document
> on those drafts being started.
> 
> However, bundling without signing has a more localized effect, which
> should fit in the single document's privacy and security
> considerations section. We should continue to improve that section in
> the same way we plan to improve the rest of the draft.
> 
> A use cases document [1] is ready for adoption. It has, historically,
> not attracted much discussion from the people who asked me to write
> it, but if having it adopted by the WG would attract more interest,
> I'm all for it. I see Daniel also has some concrete changes to
> propose, I think especially around promoting
> https://wicg.github.io/webpackage/draft-yasskin-wpack-use-cases.html#name-subresource-bundling
> to "essential". I think it's easier to tell whether the WG supports
> that sort of change after we adopt the document.
> 
> Jeffrey
> 
> On Fri, Mar 19, 2021 at 7:51 PM Sean Turner <[e-mail]> wrote:
> 
>> Mark,
>>
>> You make a good point about the need for the additional I-Ds,
>> because the charter’s milestones actually call out 3 other I-Ds
>> that address the signing mechanism as well as privacy and security.
>> To be blunt, these other I-Ds have not yet been submitted. There was
>> some security-related text in the bundle document that was removed
>> and Martin Thomson had a content-based origin I-D. I am cautiously
>> optimistic that getting the bundling I-D adopted will encourage the
>> other I-Ds to surface because I strongly suspect that progress on
>> the bundling I-D is likely to grind to a halt without those I-Ds. I
>> do not think that the milestones, which are also a good year out of
>> date at this point, should hold us back from adopting the bundling
>> I-D. But, the entire set of I-Ds is required- it is the pact we made
>> the IESG to get to done.
>>
>> spt
>>
>>> On Mar 16, 2021, at 00:59, Mark Nottingham <[e-mail]> wrote:
>>>
>>> Hi Sean,
>>>
>>> I don't have access to minutes of the meeting yet, so this may
>> have already been answered --
>>>
>>> The charter says that a use cases document, a privacy analysis
>> document, and a security analysis document will be adopted at the
>> same time as the bundling document. What's their status?
>>>
>>> Cheers,
>>>
>>>
>>>> On 16 Mar 2021, at 11:53 am, Sean Turner <[e-mail]> 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
>>>> [e-mail]
>>>> https://www.ietf.org/mailman/listinfo/wpack
>>>
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>>
>>
>> _______________________________________________
>> Wpack mailing list
>> [e-mail]
>> https://www.ietf.org/mailman/listinfo/wpack
>  
> 
> Links:
> ------
> [1] https://tools.ietf.org/html/draft-yasskin-wpack-use-cases-01
> _______________________________________________
> Wpack mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/wpack