From nobody Fri Mar 8 12:49:41 2019 Return-Path: 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 49EA112D110 for ; Fri, 8 Mar 2019 12:49:34 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.999 X-Spam-Level: X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=isoc.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 T0uUcxwoDeTu for ; Fri, 8 Mar 2019 12:49:31 -0800 (PST) Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-co1nam05on0630.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe50::630]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E38B9130DCD for ; Fri, 8 Mar 2019 12:49:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=isoc.org; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=XRaRKKs9NvS8zmf/Gj/EgL4vgXKyp16nuJa3TuO3kyY=; b=W5kr2WxNvgAGqxtZOsD+5s//cdhgpxlOH3k31FGMENJ8FQvok5ZcSuxAc+aKkOj3nVx+4JMOU+Hs0ljGJCTFjfK7D97yJr4Nh2b7ovCciVCQOE9x7F5zxPZU5hwOS2rGBUWsOaJCuxd9tZJgTni2JE1YaZJl2P9D+108i8+vj+o= Received: from BN8PR06MB5570.namprd06.prod.outlook.com (20.178.210.219) by BN8PR06MB5892.namprd06.prod.outlook.com (20.179.139.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.1686.19; Fri, 8 Mar 2019 20:49:27 +0000 Received: from BN8PR06MB5570.namprd06.prod.outlook.com ([fe80::3483:c592:8ecf:98ad]) by BN8PR06MB5570.namprd06.prod.outlook.com ([fe80::3483:c592:8ecf:98ad%4]) with mapi id 15.20.1665.020; Fri, 8 Mar 2019 20:49:27 +0000 From: Dan York To: "wpack@ietf.org" Thread-Topic: FYI - Web Packaging at IETF 104 - in DISPATCH - Fwd: [dispatch] Re-dispatching Web Packaging Thread-Index: AQHUxVQnqlGwVIUlgUqruTOg8Nxt8Q== Date: Fri, 8 Mar 2019 20:49:27 +0000 Message-ID: References: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: spf=none (sender IP is ) smtp.mailfrom=york@isoc.org; x-originating-ip: [2601:198:4101:7bd5:512f:478e:ba0:c348] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: 2732ddbd-89b3-40f7-ecb6-08d6a4078e42 x-microsoft-antispam: BCL:0; PCL:0; RULEID:(2390118)(7020095)(4652040)(8989299)(4534185)(4627221)(201703031133081)(201702281549075)(8990200)(5600127)(711020)(4605104)(2017052603328)(7153060)(7193020); SRVR:BN8PR06MB5892; x-ms-traffictypediagnostic: BN8PR06MB5892: x-ms-exchange-purlcount: 9 x-microsoft-exchange-diagnostics: =?us-ascii?Q?1; BN8PR06MB5892; 23:Qt48Ar5VtiO6htU6ZEk39HbJt29Qky704moNqQZ2I?= =?us-ascii?Q?aESzM7gSnj9iXlgnvjtgqwTwFMqZwXondHp0shTHV1bXw34sy02c9/poRMiK?= =?us-ascii?Q?UKBufQ7yVuy6Gu2aguX1N8QrgeEFBXDSNNcDTVlHTfUwao7ebRUwMCrQpk9D?= =?us-ascii?Q?im5iF4N5MrhG9SeT/DzA4Q/DvCqFpL2L+tOqOM2gqI/fDQM+5OfFUTz1yFSJ?= =?us-ascii?Q?EkxmDnsTEqnWHQovl0ASKZH94ICmFFb5c5N9NElJj1YUlL+K1IyMUvHICZbw?= =?us-ascii?Q?B/kBUFImY4BTMAPW4B6Nqiy0lASS39d/rQ+wm5I0E2TC0B3ARAHzSgOsYH1c?= =?us-ascii?Q?agwMAEMuqtI4Rz3zfz3Rfr4JtAcXsr9xQEZ58UhSWKyBDh8rtPAgPPcP5mK+?= =?us-ascii?Q?zZMmNbBNQdWBRG/HxUTBn4mbox4w07qXPdc53LTm9IH0l97v8QcLB4w3zYwH?= =?us-ascii?Q?oSg+N3JgeZ3qF61bZHVJw9S6EJBuLzrAfirkO4LmpTIUFeh+6uUI1aiuHdD1?= =?us-ascii?Q?ApHPq3IaZIJtRrysqCBCnKlHggcru+tJdzfo/t9vdS/ZdOg9LcV9czUn3CTk?= =?us-ascii?Q?AJP9GnCAXpL5yG74q8nmUtpUO/gC/WkYOvuRRh8/nBg5vmaAYstwiA38aBjt?= =?us-ascii?Q?sxhy8MWVhXUK/2+YjSLY934ed4Hlx03qXBbzpQbMrYSy4vQ7/zX8NBk0VAHR?= =?us-ascii?Q?yijrW02Fodl7bq8tyTScogumTxQHKcx3LgTPJgLU/lbJOi5BDlsqDAXD1QlH?= =?us-ascii?Q?T2MafmWby5ktKy6O8ieb2qCIo+vSaIaWhKayFucPrjjzJ833q0H9Z23KTa2A?= =?us-ascii?Q?vzBLq5bGEnHSa/ocAaX6OEojgD6DaxqgPfwtAqbNfwI4/SbmpKPo7s5/cHBC?= =?us-ascii?Q?5lMAsOVoJuhNn/YzhDiroYD0D/WXxUjmxicg34SncES0PeHs8aqLr6clvU8N?= =?us-ascii?Q?O6WqUraZyFwI06AP7kR7u0ojf7cbv6IT3J+WerHif6CoIsl/fYVz8m9e6LDK?= =?us-ascii?Q?QC1Imaf+BH0SXEC9zt73KNP+yOe50zO7qnC7egOnUKTVOJExxSpjswdugg0S?= =?us-ascii?Q?TFckoVeODycsuRxStrjfHhKDUMf6IwbsmaD7KFivsZA0rT2tW24IfJEKznTR?= =?us-ascii?Q?dlilJwBN4WkfVfMoq5pukPw1b1QzGb6zjqwiVSq2KyHTWwvtbEDQc8LzJ9lt?= =?us-ascii?Q?zvmK7ebhrRbA4UTHTDUpY42r/XEY8mWxhTHlqafS9V56LD6wRajPxiPykmI9?= =?us-ascii?Q?gIldnd6CSL4I8CjwTqqk4HmOT1+KDQ6NrEInTL4DqFyObZxWjkOw7vg6YAQm?= =?us-ascii?Q?F9eKGseuslUhRpifPc9w2nycxPWQQZgrUrk+zwKeaWdyA234b3gjnJU2ZLtY?= =?us-ascii?Q?0NPAw=3D=3D?= x-microsoft-antispam-prvs: x-forefront-prvs: 0970508454 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(366004)(346002)(136003)(39850400004)(396003)(376002)(189003)(199004)(186003)(7736002)(76176011)(2501003)(102836004)(14444005)(6116002)(53936002)(14454004)(256004)(86362001)(6506007)(83716004)(71190400001)(71200400001)(99286004)(606006)(6916009)(5660300002)(53376002)(66574012)(6512007)(106356001)(5640700003)(561944003)(105586002)(2906002)(2351001)(33656002)(97736004)(36756003)(68736007)(46003)(25786009)(6436002)(6486002)(82746002)(486006)(21615005)(8676002)(316002)(81166006)(1730700003)(81156014)(446003)(2616005)(6306002)(476003)(54896002)(8936002)(966005)(478600001)(236005); DIR:OUT; SFP:1101; SCL:1; SRVR:BN8PR06MB5892; H:BN8PR06MB5570.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; received-spf: None (protection.outlook.com: isoc.org does not designate permitted sender hosts) x-ms-exchange-senderadcheck: 1 x-microsoft-antispam-message-info: cPJDl9vVUlvNP+ZuZ/BfoeZaP+3cvKNi10NHjEMPygpERNUyzYF0uHdKJ7zPuGolcNe/St2CF1aJ+da7mUA8IRS0LFq3pe73cEzF70rpMJ/IUozzsL0Kb6shVjGy+UA0uT1sq0JGokZUo3+NfKb0kYMAMRMawzwG99PCKM26kg8EWe/N1+nrptDfJfTFX5P0gVOgHaX3YIUcR5WP3f3QoXq+dFb1SGQsBBT9m5A/AjahG8F34ViaP3C4rrwQAInIDAQkhe/YXREmzo5DSrw1O3kdO0omu5FVYfQK9ft1DfUbyKUWW7hvT9NXaYfAEyuVmv/22Toa2WOBpa9IPQ15dsVAvKwGpTPEKw7FQ4n5NgMuH2MQWYdguR8K3PBB7U132/SL6ZLChBoAv7QJvnLdKYOn1AJqQslF1BwZpU9sREo= Content-Type: multipart/alternative; boundary="_000_AE1539AFA1D14F53A31470F1F271FAE4isocorg_" MIME-Version: 1.0 X-OriginatorOrg: isoc.org X-MS-Exchange-CrossTenant-Network-Message-Id: 2732ddbd-89b3-40f7-ecb6-08d6a4078e42 X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Mar 2019 20:49:27.6129 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 89f84dfb-7285-4810-bc4d-8b9b5794554f X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN8PR06MB5892 Archived-At: Subject: [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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Mar 2019 20:49:39 -0000 --_000_AE1539AFA1D14F53A31470F1F271FAE4isocorg_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable 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 Skype: danyork = http://twitter.com/danyork http://www.internetsociety.org/ Begin forwarded message: From: Jeffrey Yasskin > 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/, at IETF99= , with the discussion at https://mailarchive.ietf.org/arch/msg/dispatch/lZo= hQ8ypodcpB2f_jhxoBRMYl0o. On your advice, we split the proposal into two pi= eces, "signed exchanges", and "bundles". We also created the https://mailar= chive.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 tha= t specifies the format: https://wicg.github.io/webpackage/draft-yasskin-htt= p-origin-signed-responses.html, and a WICG draft that specifies ho= w it integrates with Fetch: https://wicg.github.io/webpackage/loading.html.= We've implemented that specification in Chromium, run an origin trial in C= hrome, and will be shipping the current version in Chrome 73: https://group= s.google.com/a/chromium.org/d/topic/blink-dev/gPH_BcOBEtc/discussion. Despite shipping the current version, we expect standards bodies to make mo= re changes, and we've built in a way to migrate users to new versions of th= e 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/w3= ctag/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 a= t 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 --_000_AE1539AFA1D14F53A31470F1F271FAE4isocorg_ Content-Type: text/html; charset="us-ascii" Content-ID: <4B4F105F9EFAB547921E874F414C616E@namprd06.prod.outlook.com> Content-Transfer-Encoding: quoted-printable 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 curr= ent draft agenda points to this email message.)

--
Dan York
Director of Web Strategy, Internet Society
york@isoc.org   &= #43;1-802-735-1624 
Jabber: york@jabber.isoc= .org  Skype: danyork   http://twitter.com/danyork

http://www.internets= ociety.org/

Begin forwarded message:

From: Jeffrey Yasskin <jyasskin=3D40google.com@d= marc.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 discuss= ion of Web Packaging at IETF104. We think it'll be ready for a BOF at IETF1= 05, 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://maila= rchive.ietf.org/arch/msg/dispatch/lZohQ8ypodcpB2f_jhxoBRMYl0o. On your advice, we split the proposal into two pieces, "signed exchan= ges", and "bundles". We also created the https://mailarchiv= e.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 a= n IETF draft that specifies the format: https://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-respons= es.html, and a WICG draft that specifies how it integrates with Fetch: https://wicg= .github.io/webpackage/loading.html. We've implemented that specificatio= n 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/disc= ussion.

Despite shipping the current version, we expect standards b= odies to make more changes, and we've built in a way to migrate users to ne= w 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.<= /div>

The W3C TAG recently discussed the state of things at = https://github.co= m/w3ctag/meetings/blob/gh-pages/2019/02-tokyo/02-06-minutes.md#signed-excha= nges-and-bundling.

Mark Nottingham and a representative of the TAG are organiz= ing an "ESCAPE" conference at a TBD date to help publishers organ= ize their feedback on the proposals. This has been pushed back a couple tim= es, 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 di= scuss in a BOF at IETF105, with the goal of handing control of the specific= ations 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 wi= th the proposals.

Thanks,
Jeffrey
_______________________________________________
dispatch mailing list
dispatch@ietf.org
https://www.ietf.org/mailman/listinfo/dispatch

--_000_AE1539AFA1D14F53A31470F1F271FAE4isocorg_-- From nobody Mon Mar 11 15:16:07 2019 Return-Path: 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 ; 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 ; 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 ; Mon, 11 Mar 2019 15:15:50 -0700 (PDT) Received: by mail-lf1-x142.google.com with SMTP id u9so475056lfe.11 for ; 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: In-Reply-To: From: Jeffrey Yasskin Date: Mon, 11 Mar 2019 15:15:36 -0700 Message-ID: To: Dan York Cc: "wpack@ietf.org" Content-Type: multipart/alternative; boundary="0000000000002d2e9d0583d8ea9d" Archived-At: 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 11 Mar 2019 22:16:01 -0000 --0000000000002d2e9d0583d8ea9d Content-Type: text/plain; charset="UTF-8" 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 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 Skype: danyork > http://twitter.com/danyork > > http://www.internetsociety.org/ > > Begin forwarded message: > > *From: *Jeffrey Yasskin > *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/ > , 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 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 > --0000000000002d2e9d0583d8ea9d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've also reserved up to 2 hours in t= he Wednesday afternoon side-meeting session at 3pm:=C2=A0https://trac.ietf.org/trac/ietf/meeting/wiki/104sidemeetings#Room= :AthensBarcelonaWednesday. We can go into more detail there, see what u= se cases folks are interested in or worried about, start drafting the chart= er, etc.

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

Jeff= rey

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 a= genda points to this email message.)

--
Dan York
Director of Web Strategy,=C2=A0Internet Society
york@isoc.org=C2=A0= =C2=A0 +1-802-735-1624=C2=A0
Jabber: york@jabb= er.isoc..org =C2=A0Skype:=C2=A0danyork =C2=A0=C2=A0http://twitter.com/danyork

http://www.in= ternetsociety.org/

Begin forwarded message:

Subject: [dispatch] Re-dispatching Web Packaging<= /b>
Date: February 15, 2019 at 12:30:05 PM EST

Hello Dispatch,

TL;DR: I'd like to request another=C2=A0discussion 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,=C2=A0https://github.com/WICG/webpackage/, at = IETF99, with the discussion at=C2=A0https://m= ailarchive.ietf.org/arch/msg/dispatch/lZohQ8ypodcpB2f_jhxoBRMYl0o. On your advice, we split the proposal into two pieces, "signed exchan= ges", and "bundles". We also created the=C2=A0https://mai= larchive.ietf.org/arch/browse/wpack/=C2=A0mailing list, although it has= n't seen as much activity as the github issue tracker.

The signed exchanges specification is mostly complete, in an IETF draf= t that specifies the format:=C2=A0ht= tps://wicg.github.io/webpackage/draft-yasskin-http-origin-signed-responses.= html, and a WICG draft that specifies how it integrates with Fetch:=C2=A0https= ://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/disc= ussion.

Despite shipping the current version, we expect standards bodies to ma= ke more changes, and we've built in a way to migrate users to new versi= ons of the specification.

The Bundles specification is very roughly sketched, but we expect to f= lesh that out and start implementing it in the next few months.


Mark Nottingham and a representative of the TAG are organizing an &quo= t;ESCAPE" conference at a TBD date to help publishers organize their f= eedback 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 i= n 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 DISPAT= CH to see if anyone's sense of the right plan has changed now that we have a little more experience wi= th 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
--0000000000002d2e9d0583d8ea9d-- From nobody Sun Mar 24 01:17:14 2019 Return-Path: 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 0480E1310BC for ; Sun, 24 Mar 2019 01:17:06 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.241 X-Spam-Level: X-Spam-Status: No, score=-17.241 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, HTML_OBFUSCATE_05_10=0.26, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-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 dICsYmaYnSkE for ; Sun, 24 Mar 2019 01:17:03 -0700 (PDT) Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 DC94C130E7C for ; Sun, 24 Mar 2019 01:17:02 -0700 (PDT) Received: by mail-lf1-x12e.google.com with SMTP id 10so3972235lfr.8 for ; Sun, 24 Mar 2019 01:17:02 -0700 (PDT) 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=kkhTtbKIcD7zURs1YsJI1PybB/Wui7z4DooafZV8bNE=; b=DhwZAQKpNq43sLqlVlHtcTYkMubpm4Sjn5s7wMu+UXjp/7NCN0F/qeVcrxeaYpcNST 5ejLSowJs3W/g4sXuMqJl1EspF2L2ZD0BkX1f/PeVH+GNehS+fJJ/SLZNXi2WiK11mub CSEaO07mL3aV3zibVUsDnSEzPJsHfZPGXj8bISSa0MDNFXqVntZwVSOoU1h4yUWymEQA 486vW1bXZIo5BQB8x8eHGTW7Fg9WGLsusIN6JPN+DlSQKdhWbo5EwiluGHBKCd3Vibuq 0XOTg6qtG4Liav2QsRDB9ygReFac8Ih+XZGKgmtmZs2pqDzq69MsJD+nq5+uwZav9bkw Kgag== 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=kkhTtbKIcD7zURs1YsJI1PybB/Wui7z4DooafZV8bNE=; b=PxIsftCUfu1N1b9K+MCUw0eryzyzTVExSQhJ9HeA94FfmUpeX7Hj57ROgUb8GF8wW7 hVTpuSTuRGOGKT1zAx5cRXq4ZK7Z3yPmzSJOXRSCFFflju/f7LoCWSmCmTZSRQ2DNBJ4 teZ1q300eQglc35tf3BodzXT+lvqlEW31v6YGL8TmXpBzwxqj2fxLxsU00q6Ky7GH7Sk dy8+LBnHlm6yaF2rVQCwOjHc5WN8BzQ01lF+NiIU5LkS8cEvzwD5lzchxOI9UGETGKka J/RM9UdDdtZoTaa8RRT/mNVbLoyy1cOsiY4SHVfssyQT2F819RocmxCn+FnsZYgRoitx nvSA== X-Gm-Message-State: APjAAAX6DCQJhLTwNkjwOhUII4GiIuo51cFEeH32BtHKovAB0+MAXNJA jspq9YPnIFBpsDM/t7hUBGsc0llnMlm63TuKgCqNqSsRye90/vL/ X-Google-Smtp-Source: APXvYqxDQuOdzOG7lBHD2tiZnRlv9AR26gL/lxwTDuEfsqHeMh6pNHV6gl0sTq89D0IlRbX7PqemzUFx4ObftF2h6ig= X-Received: by 2002:ac2:51aa:: with SMTP id f10mr9231540lfk.82.1553415420526; Sun, 24 Mar 2019 01:17:00 -0700 (PDT) MIME-Version: 1.0 From: Jeffrey Yasskin Date: Sun, 24 Mar 2019 09:16:48 +0100 Message-ID: To: wpack@ietf.org Content-Type: multipart/alternative; boundary="00000000000054b9000584d2b681" Archived-At: Subject: [Wpack] Agenda for Wednesday meeting X-BeenThere: wpack@ietf.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Web Packaging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 24 Mar 2019 08:17:13 -0000 --00000000000054b9000584d2b681 Content-Type: text/plain; charset="UTF-8" I've listed a couple things to talk about in https://github.com/WICG/webpackage/wiki/IETF-104-Agenda along with the other Web Packaging things (DISPATCH and HTTPBIS) that are happening this week. Please add things you want to talk about to the agenda, along with about how long you think they might take. Everyone should have edit rights. Jeffrey --00000000000054b9000584d2b681 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I've listed a couple things to talk about in=C2=A0https://git= hub.com/WICG/webpackage/wiki/IETF-104-Agenda=C2=A0along with the other = Web Packaging things (DISPATCH and HTTPBIS) that are happening this week.
Please add things you want to talk about to the agenda, a= long with about how long you think they might take. Everyone should have ed= it rights.

Jeffrey
--00000000000054b9000584d2b681--