Re: [Wpack] FYI - Web Packaging at IETF 104 - in DISPATCH - Fwd: [dispatch] Re-dispatching Web Packaging

Jeffrey Yasskin <jyasskin@chromium.org> Mon, 11 March 2019 22:15 UTC

Return-Path: <jyasskin@google.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E28E01311C4 for <wpack@ietfa.amsl.com>; Mon, 11 Mar 2019 15:15:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.499
X-Spam-Level:
X-Spam-Status: No, score=-9.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 6jtNpjGlXSLW for <wpack@ietfa.amsl.com>; Mon, 11 Mar 2019 15:15:51 -0700 (PDT)
Received: from mail-lf1-x142.google.com (mail-lf1-x142.google.com [IPv6:2a00:1450:4864:20::142]) (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 D0A211311E4 for <wpack@ietf.org>; Mon, 11 Mar 2019 15:15:50 -0700 (PDT)
Received: by mail-lf1-x142.google.com with SMTP id u9so475056lfe.11 for <wpack@ietf.org>; Mon, 11 Mar 2019 15:15:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=r+tSfEBAlzoYU1WGsrpYCvLqPVlpuuQSDWGON7Fwx6Y=; b=aTKZjXF0J9aDsbDcZdD7nl/uffOq7klHJH9r0lOcid3xaFMxZ2Xz5UZWuNdp8aUupb 0zI0Kx/CrhGf42JFrWqo3jFctAC3ESJjjjKtO1q38tkjsMMehHTYt+x3/NHD88C1N7g3 x5drhINQiKjSevT+4V0SZxXZchPoddSOlyVys=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=r+tSfEBAlzoYU1WGsrpYCvLqPVlpuuQSDWGON7Fwx6Y=; b=GJBdWnX8WYd7lp4T2pce38z9E58WyZ2tkAO7z63+FDM0TQCtF86tIS+pV41vtcsqY2 QhFeZkPi0t+3vGIDjYai7l6mEOJ0lfOYT5E4GhgCCKPK7+FFw1JM9OjIY44lYjiozELc zPaG6xgZpepQRpsxBWEEV1pJACSHnNr/QMNBjWCnC15zZ8mTiTtMQYSKJb2+5EbvgKD+ 6xSeD5/JthkeIwSL8pIz199FxA2sdNqdKC13+245+8XyRk9vvctDtiugX3sg6Obc5w3v f1vK2yQToj4T3IFfCgOsktUvnjmRnIKQRuNp/y9pKPYP88L6mYfBhMRafpexdD/4eYtS kldA==
X-Gm-Message-State: APjAAAVKTY15j/E3eQfbcIXeHBzbRwL7ju+XQPET9NvSKN5Qm3pKL+sB cCOw/m4TtBlwS8dIxHTWMJLkJWDUMOnevibbDNJGZg==
X-Google-Smtp-Source: APXvYqyVVZFfLSyK6ty5sYSQxCV7TzGqtNy4iiG0rlO5SWpYcZUk/I1GBwNttn6qdJEC0JhMYfUUZFShqi9oi7gt0TQ=
X-Received: by 2002:a19:7613:: with SMTP id c19mr5220945lff.105.1552342548533; Mon, 11 Mar 2019 15:15:48 -0700 (PDT)
MIME-Version: 1.0
References: <CANh-dXkL1gHVcHko9Z8aSEG+dmJp3KBJnCzsY0hJ1CGG=vPF7w@mail.gmail.com> <AE1539AF-A1D1-4F53-A314-70F1F271FAE4@isoc.org>
In-Reply-To: <AE1539AF-A1D1-4F53-A314-70F1F271FAE4@isoc.org>
From: Jeffrey Yasskin <jyasskin@chromium.org>
Date: Mon, 11 Mar 2019 15:15:36 -0700
Message-ID: <CANh-dXkQh5mUXUQZZoyh7zB5ZsZVRUzPR3z9zo+ezmJ=X7Xpug@mail.gmail.com>
To: Dan York <york@isoc.org>
Cc: "wpack@ietf.org" <wpack@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002d2e9d0583d8ea9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/tEVm7wIsp81FYq5LPsCH5V0TvBE>
Subject: Re: [Wpack] FYI - Web Packaging at IETF 104 - in DISPATCH - Fwd: [dispatch] Re-dispatching Web Packaging
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Web Packaging <wpack.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpack>, <mailto:wpack-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wpack/>
List-Post: <mailto:wpack@ietf.org>
List-Help: <mailto:wpack-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpack>, <mailto:wpack-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 11 Mar 2019 22:16:01 -0000

I've also reserved up to 2 hours in the Wednesday afternoon side-meeting
session at 3pm:
https://trac.ietf.org/trac/ietf/meeting/wiki/104sidemeetings#Room:AthensBarcelonaWednesday.
We can go into more detail there, see what use cases folks are interested
in or worried about, start drafting the charter, etc.

Let me know if you want me to be especially prepared to talk about any
particular topics. :)

Jeffrey

On Fri, Mar 8, 2019 at 12:49 PM Dan York <york@isoc.org> wrote:

> FYI, Jeffrey Yasskin has time on the DISPATCH agenda at IETF 104 in
> Prague. The WG meets at 9:00am (CET) on Monday, March 25.
>
> Here is the message he sent to the DISPATCH list. (The current draft
> agenda points to this email message.)
>
> --
> Dan York
> Director of Web Strategy, Internet Society
> york@isoc.org   +1-802-735-1624
> Jabber: york@jabber.isoc..org <york@jabber.isoc.org>  Skype: danyork
> http://twitter.com/danyork
>
> http://www.internetsociety.org/
>
> Begin forwarded message:
>
> *From: *Jeffrey Yasskin <jyasskin=40google.com@dmarc.ietf.org>
> *Subject: **[dispatch] Re-dispatching Web Packaging*
> *Date: *February 15, 2019 at 12:30:05 PM EST
> *To: *dispatch@ietf.org
>
> 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/
> <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
> <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
> <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 mailing list
> dispatch@ietf.org
> https://www.ietf.org/mailman/listinfo/dispatch
>
>
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org
> https://www.ietf.org/mailman/listinfo/wpack
>