Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The IETF WPACK WG is chartered now. #571

Merged
merged 1 commit into from
Apr 15, 2020
Merged

The IETF WPACK WG is chartered now. #571

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions explainers/navigation-to-unsigned-bundles.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -152,9 +152,9 @@ We propose to use the [Web Bundle
format](https://wicg.github.io/webpackage/draft-yasskin-wpack-bundled-exchanges.html),
without origin-trusted signatures, to give users a format they can create from
any website they're visiting, share it using existing peer-to-peer sharing apps,
and then have a peer load it in their browser. The IETF has
[approved](https://ietf.org/blog/ietf106-highlights/) but not yet created a
WPACK working group to continue developing this format as of February 2020.
and then have a peer load it in their browser. The IETF's [WPACK
WG](https://datatracker.ietf.org/wg/wpack/about/) is chartered to continue
developing this format.

Here's a [demo video](https://youtu.be/xAujz66la3Y) of this use-case for Web
Bundles (a.k.a. Bundled HTTP Exchanges):
Expand Down