[dispatch] Re-dispatching Web Packaging
Jeffrey Yasskin <jyasskin@google.com> Fri, 15 February 2019 17:30 UTC
Return-Path: <jyasskin@google.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1])
by ietfa.amsl.com (Postfix) with ESMTP id 39CE2130FD6
for <dispatch@ietfa.amsl.com>; Fri, 15 Feb 2019 09:30:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level:
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5
tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1,
DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5,
HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5,
USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key)
header.d=google.com
Received: from mail.ietf.org ([4.31.198.44])
by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id 3O9F1sUSbpwu for <dispatch@ietfa.amsl.com>;
Fri, 15 Feb 2019 09:30:21 -0800 (PST)
Received: from mail-wm1-x331.google.com (mail-wm1-x331.google.com
[IPv6:2a00:1450:4864:20::331])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by ietfa.amsl.com (Postfix) with ESMTPS id 93708128BCC
for <dispatch@ietf.org>; Fri, 15 Feb 2019 09:30:21 -0800 (PST)
Received: by mail-wm1-x331.google.com with SMTP id x10so10278900wmg.2
for <dispatch@ietf.org>; Fri, 15 Feb 2019 09:30:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025;
h=mime-version:from:date:message-id:subject:to;
bh=3eZ2ka/khRLBnkMoOOUvVfaOs0DWQi4ZgKtI9NOh/fs=;
b=OoF5NiEVQkUvQZjyuom1Rh9tVxy3CpEfzZXSLv4JldPEDYh9i2kvWQJIS01DEMs1X5
zUr/Iz8uPwq3Qy9U7lf/eW4kaO7rvsFfV/Ab3/m+Xps96DVjobuE5ijIgg/TA0Okhjq5
ty30+PH8dSK5Ypux35CzddlCSZV5oMpfCIRD3faAgPi1xlPjrYXhE7g5DnLNzdeD+TUL
itOxckNIftuRHpZc15GQtR46LkEY5KbPiMUppqfIifFjnLUNfKvqyoxsyzb9mmpF5g2V
3T/g0ovWQ8GxG/LptS6cEIaOf1XoHeoDtfmYw/1RGacvdBTm+6ZXh4Pq6GCDapUslwU8
PMNg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
bh=3eZ2ka/khRLBnkMoOOUvVfaOs0DWQi4ZgKtI9NOh/fs=;
b=Lswnmd40Abqu9rRw5myXLpswFiASOiPay8qP6gwOT8K9V7hegcgEfQFoTS32VY+3Wg
eWcB6qb038gQvS+DlL0sJf+1d676nTh0qEORBAXlvPRHMMBhV5jUlxg48fM9h+XCrjIb
TSE/M7azOJeImM075MYKoAAlZ+a/ugiA02UAxpBe0jTrZ6VhBWdr36tURNLmBKyh6wtV
aPPCGa00gfoMSFd0mehS74DWXuHUSVyc0C5SN9RJyOrZJYhadCFuCPifzKCvQXljsb9a
VnB7QnDxT2/uj8kx/X9dhz4FaX/0mPuT72jGrjYCasirDgL47wJopsxQSHv31WRqocoS
agaQ==
X-Gm-Message-State: AHQUAua+cd7NMHA+huI0Qw/o9iMJPNWI1LDDWqQdmzE465noARDL91fZ
b2aVkhxKMe8+GjQUCznDypRD9f7RAUwAXkNm8tmfhtOuhamwsw==
X-Google-Smtp-Source: AHgI3IbNmyNUQLhkj/c6jJ5eaN44numJWFjZH26zpIgjCWmYB2sMhi53Hz0Lc/rtXjPK+K4FhHbcWFeAVxOsVxOFGyY=
X-Received: by 2002:a7b:cf1a:: with SMTP id l26mr7206728wmg.76.1550251819061;
Fri, 15 Feb 2019 09:30:19 -0800 (PST)
MIME-Version: 1.0
From: Jeffrey Yasskin <jyasskin@google.com>
Date: Fri, 15 Feb 2019 07:30:05 -1000
Message-ID: <CANh-dXkL1gHVcHko9Z8aSEG+dmJp3KBJnCzsY0hJ1CGG=vPF7w@mail.gmail.com>
To: dispatch@ietf.org
Content-Type: multipart/alternative; boundary="000000000000fd3b790581f2208e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/e6ZSh7ocW6n2afnbwGzBlX1WT8Y>
Subject: [dispatch] Re-dispatching Web Packaging
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>,
<mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>,
<mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 15 Feb 2019 17:30:24 -0000
Hello Dispatch, TL;DR: I'd like to request another discussion of Web Packaging at IETF104. We think it'll be ready for a BOF at IETF105, but mnot suggested we take it back here for a second look. We dispatched Web Packaging, https://github.com/WICG/webpackage/, at IETF99, with the discussion at https://mailarchive.ietf.org/arch/msg/dispatch/lZohQ8ypodcpB2f_jhxoBRMYl0o. On your advice, we split the proposal into two pieces, "signed exchanges", and "bundles". We also created the https://mailarchive.ietf.org/arch/browse/wpack/ mailing list, although it hasn't seen as much activity as the github issue tracker. The signed exchanges specification is mostly complete, in an IETF draft that specifies the format: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.html, and a WICG draft that specifies how it integrates with Fetch: https://wicg.github.io/webpackage/loading.html. We've implemented that specification in Chromium, run an origin trial in Chrome, and will be shipping the current version in Chrome 73: https://groups.google.com/a/chromium.org/d/topic/blink-dev/gPH_BcOBEtc/discussion . Despite shipping the current version, we expect standards bodies to make more changes, and we've built in a way to migrate users to new versions of the specification. The Bundles specification is very roughly sketched, but we expect to flesh that out and start implementing it in the next few months. The W3C TAG recently discussed the state of things at https://github.com/w3ctag/meetings/blob/gh-pages/2019/02-tokyo/02-06-minutes.md#signed-exchanges-and-bundling . Mark Nottingham and a representative of the TAG are organizing an "ESCAPE" conference at a TBD date to help publishers organize their feedback on the proposals. This has been pushed back a couple times, but it sounds like it's more solidly planned for either May or July before IETF105. We think we'll be able to write a WG charter that we can discuss in a BOF at IETF105, with the goal of handing control of the specifications to a more formal group. However, mnot suggested that we come back to DISPATCH to see if anyone's sense of the right plan has changed now that we have a little more experience with the proposals. Thanks, Jeffrey
- [dispatch] Re-dispatching Web Packaging Jeffrey Yasskin
- Re: [dispatch] Re-dispatching Web Packaging Mark Nottingham