The meat of the story is: "We embarked on a multi-month long effort, and today we finally feel confident that we found a solution: As recommended by the W3C TA

The meat of the story is: "We embarked on a multi-month long effort, and today we finally feel confident that we found a solution: As recommended by the W3C TAG [1], we intend to implement a new version of AMP Cache serving based on the emerging Web Packaging standard [2]." I'm just reading through this so I'm gleaning as I go, but it looks like the W3C TAG came out with a recommendation for 'Distributed and Syndicated Content' [1] that specifically addresses AMP by name, and recommends strategies to do this kind of content syndication in a way that preserves the original provenance of the data. The Web Packaging Format [2] aims to, apparently [3], solve packing together resources, but, rather, HTTP request-response pairs, maybe HPACKed?, and signed and hashed for integrity, in a flat hierarchy, in a CBOR envelope, that nonetheless has MIME-like properties? I'm still digesting what's all involved. [1] https://www.w3.org/2001/tag/doc/distributed-content/ https://www.w3.org/2001/tag/doc/distributed-content/ [2] https://github.com/WICG/webpackage https://github.com/WICG/webpackage [3] https://github.com/WICG/webpackage/blob/master/explainer.md https://github.com/WICG/webpackage/blob/master/explainer.md