From nobody Tue Mar 9 07:34:03 2021 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 8739D3A102D for ; Tue, 9 Mar 2021 07:34:02 -0800 (PST) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 dSV0iv0RC0_K for ; Tue, 9 Mar 2021 07:34:01 -0800 (PST) Received: from mail-qv1-xf32.google.com (mail-qv1-xf32.google.com [IPv6:2607:f8b0:4864:20::f32]) (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 3DA5F3A1028 for ; Tue, 9 Mar 2021 07:34:01 -0800 (PST) Received: by mail-qv1-xf32.google.com with SMTP id 2so6589528qvd.0 for ; Tue, 09 Mar 2021 07:34:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=lBOSgtf/sbHXPUSyVHCDG+tijz1sprTtQlznzH4xt3k=; b=fSCQFyKVoOh1Glo0+yCnWSdb3oaq+BbLz+tJJ+UzjNdNeg1C9pKaZBlhSxL3ji4M2V 3zpLuFzu4K959Q5bd3EQG9PF111NV7t7SnyehZHK0LpHy81hHcIplggZfaPbHEnsi2uh 0468zcndL8nKW53ogrviG47yvmWT5xCKpgA3A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=lBOSgtf/sbHXPUSyVHCDG+tijz1sprTtQlznzH4xt3k=; b=XbJa9HsrREy4agjDU74Bog9i7J2h1tQlA6xgSL4vcPzVYyTAhnps75bOkozScsTPZP TMQiQKEXXfAcG/o6OqN7+882jdNZ+oQwl4puMC5LAE79zlJZCoriawjeh/mjMa2b45ps ozs6x20jACFoIwV+XY2VfZKbxWcg8hhyEYxeYuS1UOa1+7NUIEP16C2X80GQ3xs5KxFz UPQ67/K+kETYIjTpRbqBaH2Bbhmb8qS72708nmtfP8yYQl8hhIG55GEu/50/kLxe4rtr oLPmClOF1rfmko1ihDrw9F8AV6eJ/W6XgYHMwSLFjQmqgOnWgRRm3qnlHpUOULFyi7MA GGZA== X-Gm-Message-State: AOAM531xRxi1QZq5ljAss+AMI+kJSBPLCKFSJLyB3qCmcUrK5rT0+NRY fIXjX7JXw9Va2UoFHXnXF9YdE+zVeVsJqQ== X-Google-Smtp-Source: ABdhPJyeoneDAURhwUZtFXnKVDB3aUgQB0LwH1SkCLURZpLlhnE5Gw9As3cRL216yelWnF5TYU8rXA== X-Received: by 2002:a05:6214:f6d:: with SMTP id iy13mr26347382qvb.24.1615304039163; Tue, 09 Mar 2021 07:33:59 -0800 (PST) Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id s19sm10190729qks.130.2021.03.09.07.33.58 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 09 Mar 2021 07:33:58 -0800 (PST) From: Sean Turner Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Message-Id: Date: Tue, 9 Mar 2021 10:33:58 -0500 To: WPACK List X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: [Wpack] wpack@ietf110: agenda materials 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: Tue, 09 Mar 2021 15:34:03 -0000 The slides for Friday=E2=80=99s session have been uploaded and can be = found here: https://datatracker.ietf.org/meeting/110/session/wpack spt (for the chairs)= From nobody Mon Mar 15 17:53:30 2021 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 991363A14CC for ; Mon, 15 Mar 2021 17:53:28 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 MahZzTFk1cUL for ; Mon, 15 Mar 2021 17:53:26 -0700 (PDT) Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 938033A14CB for ; Mon, 15 Mar 2021 17:53:26 -0700 (PDT) Received: by mail-qk1-x735.google.com with SMTP id d20so33706277qkc.2 for ; Mon, 15 Mar 2021 17:53:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=JWuXEfuuhp1ly1s4zMlcielxHNk+Ftwe4uO9gTV6OPc=; b=WZ0++c+2oGj6bG2jGNWtVvdjSNVckYoZe+9Iij5TvSv1e8tUdkfUHta12VDwGq0yc/ lhiDQaP6iIFxcvq47TqONRxTWFpVxTNpM46DAy1Ve2QUbSMdZaLPy+0SoZre8sGiYunB ZwQ8VhqAPZ8JtZlDpqBWJ7wTOUGVNQa1H3/Hg= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=JWuXEfuuhp1ly1s4zMlcielxHNk+Ftwe4uO9gTV6OPc=; b=tBeU7sn4iJiuoM7++N9+c5XxsH7VR7Zx2+hxQUboHSx/H4KJtd8P39ksLZMktRGfDH 13sJXzpmt9up3PEdotOwk1uzqyh4R8T5Rx8pB+wnzxcuVWrJYqNFF7OJSna/D5vk2pjI yCJ4ha4Wdtc706sF66aQ+TddDZ24xw7CA+w2/LW6eod+JVx/aIx3DW2CMET+zSLrrEwW UjAT1XrD3O0zz8cZgCTaSGuJ94MLoexZvk5Zot9IIPff6u7okpijenrIvjK5inrQdBv1 DMBTMe/nJ0c51cwv0xrzNB2coKMxhclrhjiGfK3i37LAo5GjoBAQ3s/J8NwfFHoqvNQy vE7A== X-Gm-Message-State: AOAM530nkF8hMAg02Uz1E1YouenGLgkbJdkWtoicrX7boDffI7pXcRYF 594FwZvNiN32cVC3vQBWQKVJRusW71VPtw== X-Google-Smtp-Source: ABdhPJz6/YIpai5aXp1VXObwk5caFOaXQPzD5FBcfWCXi5GEQbfZiWqpAbA3UuG9I00YD2STOI8wLw== X-Received: by 2002:a37:ac10:: with SMTP id e16mr3855213qkm.314.1615856005016; Mon, 15 Mar 2021 17:53:25 -0700 (PDT) Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id r7sm12016819qtw.17.2021.03.15.17.53.24 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 15 Mar 2021 17:53:24 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Message-Id: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> Date: Mon, 15 Mar 2021 20:53:23 -0400 To: WPACK List X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Tue, 16 Mar 2021 00:53:29 -0000 Based on interest expressed at IETF 110, this email starts the call for = adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found = here: = https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ This adoption call will run until March 30, 2021 at 2359 UTC. Please = indicate whether or not you would like to see this I-D adopted as a WG = item. Note that this is an adoption call for the draft as a starting = point for the bundle format. Thanks, spt (for the chairs)= From nobody Mon Mar 15 17:54:02 2021 Return-Path: X-Original-To: wpack@ietf.org Delivered-To: wpack@ietfa.amsl.com Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id E29523A14DB; Mon, 15 Mar 2021 17:54:00 -0700 (PDT) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit From: IETF Secretariat To: , , X-Test-IDTracker: no X-IETF-IDTracker: 7.27.0 Auto-Submitted: auto-generated Precedence: bulk Message-ID: <161585604090.26433.3832243990277651160@ietfa.amsl.com> Date: Mon, 15 Mar 2021 17:54:00 -0700 Archived-At: Subject: [Wpack] The WPACK WG has placed draft-yasskin-wpack-bundled-exchanges in state "Call For Adoption By WG Issued" X-BeenThere: wpack@ietf.org X-Mailman-Version: 2.1.29 List-Id: Web Packaging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 16 Mar 2021 00:54:01 -0000 The WPACK WG has placed draft-yasskin-wpack-bundled-exchanges in state Call For Adoption By WG Issued (entered by Sean Turner) The document is available at https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ From nobody Mon Mar 15 18:00:14 2021 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 7BE673A14F8 for ; Mon, 15 Mar 2021 18:00:13 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -17.599 X-Spam-Level: X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 c-Fpdty_Khy7 for ; Mon, 15 Mar 2021 18:00:12 -0700 (PDT) Received: from mail-qv1-xf2a.google.com (mail-qv1-xf2a.google.com [IPv6:2607:f8b0:4864:20::f2a]) (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 E187D3A14F5 for ; Mon, 15 Mar 2021 18:00:11 -0700 (PDT) Received: by mail-qv1-xf2a.google.com with SMTP id x27so8760839qvd.2 for ; Mon, 15 Mar 2021 18:00:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lGbzMkQbfbnI25RXPYBxsYOK+8O/x1bCSIW43RCZm50=; b=IzdpePLvl3N+aNasMkszwZrjPhkfT0zoA6bOietpQiGR7phzBPkLWhtqXoqJI+jWCL euxERjBht8k5blDOCEJAKns5fk2W3sk5cUr5YA/Axl7hkmDMZlTuwFyAUHMdGbhXeRwk EGlKVR+cg8hD1bLkQ5nJP/yLugBpwMCDlVqRy7hP8wUQUPR1cEzFK4P9++oOYSTUhO8P OJff3IVhoIHqgYfHYhOy673uutqezmIkA9bch0idhnyPwkvNBL4KTIs+OvyssPXxs0fT CfrrhJr7Tj5ZmT9UyOA00MdVuF34XRCB7R4QJOwwNUq0Spc/0tf3bO2p6jJQBFAL2mx5 Li0Q== 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=lGbzMkQbfbnI25RXPYBxsYOK+8O/x1bCSIW43RCZm50=; b=a1fl4yXPNGG90yvX1VzecNNyLWqS/YnHSbmnXR+y3u26rEy9HA02DWU14bU8Opso2T 5RRsAVYHhAOmjcyXU3/KvzT3ip7o4PMA/MLnZm4O7qzyMQ8INpnK2+VMiRMlVGG3dMFa Kjb/TeXUWtXLXN5Rt8YMqI09CSzEAmJeILD0Fm5pyDvg2qzvzeT+MGGL3aTxj39Mztm9 63qxIEM2krsVc6DoLIgpXTbbdL3fGL52vJISf0y+E7KepooNyOQ63OlIW7PDXszSOY/e ztVXdASM+C3uA7JJccveKh/x8vWaELRVt0/oKYz4c++6ZpSRijuPeIdjVDin+MNn13hJ sLaQ== X-Gm-Message-State: AOAM532RMo4KooQfh0n+OZLncOeXVog2KtlzPrMTNRKw6cCIAT/gvGCy SZzcyBztdl3sMlUOsVdqDKOc33G0u4Wu1A0D9imV+A== X-Google-Smtp-Source: ABdhPJy7tqM2fZu2/DT6beUpezyDDoq0TMwT41NM6U8PDqiJ6G1elalxYiB7S5mCQrW8B3vabi5DAb8nzMcC4h3mnqM= X-Received: by 2002:a05:6214:a62:: with SMTP id ef2mr7754234qvb.44.1615856410303; Mon, 15 Mar 2021 18:00:10 -0700 (PDT) MIME-Version: 1.0 References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> In-Reply-To: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> From: Jeffrey Yasskin Date: Mon, 15 Mar 2021 17:59:58 -0700 Message-ID: To: Sean Turner Cc: WPACK List Content-Type: multipart/alternative; boundary="00000000000058a3f505bd9ce32a" Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Tue, 16 Mar 2021 01:00:14 -0000 --00000000000058a3f505bd9ce32a Content-Type: text/plain; charset="UTF-8" I, predictably, support the WG adopting my draft and continuing to develop it toward consensus. Jeffrey On Mon, Mar 15, 2021, 5:53 PM Sean Turner wrote: > Based on interest expressed at IETF 110, this email starts the call for > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found > here: > > https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ > > This adoption call will run until March 30, 2021 at 2359 UTC. Please > indicate whether or not you would like to see this I-D adopted as a WG > item. Note that this is an adoption call for the draft as a starting point > for the bundle format. > > Thanks, > > spt (for the chairs) > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack > --00000000000058a3f505bd9ce32a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I, predictably, support the WG adopting my draft and= continuing to develop it toward consensus.

Jeffrey

=
On Mon, Mar 15, 2021, 5:53 PM Sean Tu= rner <sean@sn3rd.com> wrote:
Based on interest expressed at IETF 1= 10, this email starts the call for adoption of draft-yasskin-wpack-bundled-= exchanges. The I-D can be found here:

=C2=A0 https://dat= atracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/

This adoption call will run until March 30, 2021 at 2359 UTC. Please indica= te whether or not you would like to see this I-D adopted as a WG item. Note= that this is an adoption call for the draft as a starting point for the bu= ndle format.

Thanks,

spt (for the chairs)
_______________________________________________
Wpack mailing list
Wpac= k@ietf.org
https://www.ietf.org/mailman/listinfo/wpack
--00000000000058a3f505bd9ce32a-- From nobody Mon Mar 15 22:00:03 2021 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 0E1F53A19F7 for ; Mon, 15 Mar 2021 22:00:01 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.82 X-Spam-Level: X-Spam-Status: No, score=-2.82 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=FLNgV6/O; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nDxr6q7p 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 xGPiuUduCJEu for ; Mon, 15 Mar 2021 21:59:59 -0700 (PDT) Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC14A3A19F5 for ; Mon, 15 Mar 2021 21:59:58 -0700 (PDT) Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 14A135C0156; Tue, 16 Mar 2021 00:59:58 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Tue, 16 Mar 2021 00:59:58 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm2; bh=P BcYG0FLyhNzVMIQ7sQXb4xIFBhYCs2UoAsu1T6+K94=; b=FLNgV6/Ol3WzkZ5WG lx2Imvl0Q2fkeE/+4xsvvQaygpeZeuaM0MRZjo4PzZT2l8yRTipIBKy9p2/Z8OqA k/zQ4cKFHOasINAyOXuneO5BZ9Csh/SubdLdcf1qjb8KZPz8nVq+OazuzmeWryjx wKltt2KVMg2cTfDotRwi99Yn0/eLQV3raIPG62kQnZKu0ZzjdMJYplAlCIwGItzy SHG2zLSL9dhJaA6/gtqrW3I5NtMrgZT9gH3svYa5FpCnWpUVLn+EBKY37s466u4W T3T67CUmkZ7+bBP0YjITB5jczdD69Bzea8tsq3Ggwb+Cf5suPEDk8BwDC4VIYP9r FHt4w== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=PBcYG0FLyhNzVMIQ7sQXb4xIFBhYCs2UoAsu1T6+K 94=; b=nDxr6q7p87/nJ3mkBWZuKjXMW4OL4ffTx0mC3gs5ZGr+HRmOTwn1/C+bT vtu/aIOTDN2Gb6xtZ2qfmwQtEdpbHgcAg05OaWTpdWEBuzbGu9Tw0XfkZPsaDl7q YBoxogDOcFGa4H5aY617Y7OcCJ6a4K9I0/IzhrsioifpHALtt+mt/R6FqRBA4Qp+ k3QeKtBNTnsemcH1YBfi8tMQuwrLEjbtZ9LoTfDNuCOVPJzrdmfUbxrrl2Bj7Vx2 H+WefnIkhkXYgWMdbDLo0cEK4FoRxLiFVdXSQsjbUIz1A8dUEsVoC5KTHkk7qQ6I KCDCYVvMjcMyCqH3uwm9WHVpzxT8g== X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudefuddgjeejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucggtffrrghtth gvrhhnpeekuddvleejgeethfevkefhtdevkeelveekfeegleduiefhudegvdeiuefftddt hfenucffohhmrghinhepihgvthhfrdhorhhgpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehm rghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvth X-ME-Proxy: Received: from [192.168.7.30] (119-17-158-251.77119e.mel.static.aussiebb.net [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 83E681080054; Tue, 16 Mar 2021 00:59:56 -0400 (EDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) From: Mark Nottingham In-Reply-To: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> Date: Tue, 16 Mar 2021 15:59:53 +1100 Cc: WPACK List Content-Transfer-Encoding: quoted-printable Message-Id: <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> To: Sean Turner X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Tue, 16 Mar 2021 05:00:01 -0000 Hi Sean, I don't have access to minutes of the meeting yet, so this may have = already been answered -- The charter says that a use cases document, a privacy analysis document, = and a security analysis document will be adopted at the same time as the = bundling document. What's their status? Cheers, > On 16 Mar 2021, at 11:53 am, Sean Turner wrote: >=20 > Based on interest expressed at IETF 110, this email starts the call = for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be = found here: >=20 > = https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ >=20 > This adoption call will run until March 30, 2021 at 2359 UTC. Please = indicate whether or not you would like to see this I-D adopted as a WG = item. Note that this is an adoption call for the draft as a starting = point for the bundle format. >=20 > Thanks, >=20 > spt (for the chairs) > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack -- Mark Nottingham https://www.mnot.net/ From nobody Tue Mar 16 15:17:17 2021 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 93BE93A1171 for ; Tue, 16 Mar 2021 15:17:15 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.098 X-Spam-Level: X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.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 lzVE-rV2AZRQ for ; Tue, 16 Mar 2021 15:17:13 -0700 (PDT) Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (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 52E633A116A for ; Tue, 16 Mar 2021 15:17:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version; bh=WpLr3UdgRz48J/LYI49ZV4K6BoQx5tmoDyc7Zzk5e9I=; b=QAJyFP1PGCl175JqQVRVbXZLM/OPehiO1Zsw0rvSwITeKEMIGFhrT3qkTVxo+bcRi6fnr9yTx63zz3N57Oe8tg+ZRY37Uo6gFl1ckleu/MZgMLmD6u0oyoDUUYK4jTGZXout4IcCnjnM12EzmkTDw1QVUk0QasAsZdPgoXsuenxFq2mIvMewkmEyyvkgt8ipkljcfNwTdY0ag5TIpxNuCT/WfbOPsXKB9xUN07buKjRSacf93zeIR9CmPwugtHW4RoURA6UnSYY/wAQ7qCa1odxrMCywnaUrq+k298KS0LVWPyAWWv59CjQlVYh8ZRmpxk1GykGXOclWIP7s2Qe2cw==; Received: from maestria.local.igalia.com ([192.168.10.14] helo=mail.igalia.com) by fanzine.igalia.com with esmtps (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1lMHzt-0004hL-Fu; Tue, 16 Mar 2021 23:17:05 +0100 Received: from webmail.service.igalia.com ([192.168.21.45]) by mail.igalia.com with esmtps (Cipher TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim) id 1lMHzq-0000VL-U9; Tue, 16 Mar 2021 23:17:05 +0100 Received: from localhost ([127.0.0.1] helo=webmail.igalia.com) by webmail.service.igalia.com with esmtp (Exim 4.94) (envelope-from ) id 1lMHzl-0001qv-FE; Tue, 16 Mar 2021 23:16:57 +0100 MIME-Version: 1.0 Date: Tue, 16 Mar 2021 23:16:57 +0100 From: Daniel Ehrenberg To: Sean Turner Cc: WPACK List In-Reply-To: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <56b1802b7b134974f7cede1a34b61d2d@igalia.com> X-Sender: littledan@igalia.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Tue, 16 Mar 2021 22:17:16 -0000 I support the WG adopting the document, with the understanding that the WG will soon consider making the kinds of significant changes that we discussed in IETF 110 (e.g., #617, #618, #619 in Jeffrey's GitHub repo, and possibly a corresponding name change from "Web Bundles" to "bundled responses"). As for use cases and privacy/security analysis: I have a fairly different set of use cases in mind compared to Jeffrey's use cases document. I've tried to write about these, including implications for privacy, at https://github.com/WICG/resource-bundles (though based on recent feedback, I'm planning on making significant changes). However, as Martin has pointed out, this repository is a bit wordy and not quite to the point of what is relevant for IETF. If someone could suggest some examples to follow on how to write these documents, I can work on them in the coming months. Is it OK for the WG to adopt just the main document for now, with the goal to draft and adopt those other supporting documents in the coming months, well before sending it all off to IESG? Dan On 2021-03-16 01:53, Sean Turner wrote: > Based on interest expressed at IETF 110, this email starts the call > for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be > found here: > > https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ > > This adoption call will run until March 30, 2021 at 2359 UTC. Please > indicate whether or not you would like to see this I-D adopted as a WG > item. Note that this is an adoption call for the draft as a starting > point for the bundle format. > > Thanks, > > spt (for the chairs) > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack From nobody Fri Mar 19 19:51:38 2021 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 F41963A182F for ; Fri, 19 Mar 2021 19:51:36 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 yHySNRobAH45 for ; Fri, 19 Mar 2021 19:51:35 -0700 (PDT) Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 0B1173A182E for ; Fri, 19 Mar 2021 19:51:35 -0700 (PDT) Received: by mail-qk1-x72c.google.com with SMTP id y5so3468502qkl.9 for ; Fri, 19 Mar 2021 19:51:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZXZa6VH40L1cuyecwZIzKvugaLtdQZs+oE1JApnSifg=; b=NcKfGxGeJkSmwUYHUUKG/xWICocskDV5qHbKzJrxM2wVhlWwsnhQD6+5QtWMLucKPR RcotetRG7mL5L4b4ZAqEF8KK7/YEi7zQsC3gZN2iEYoW1atAuJ5jIndGT3de40QOF8zn YtMDPUSNAuK0+TosrlqR+L5wsevdC/3Wz+PiI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=ZXZa6VH40L1cuyecwZIzKvugaLtdQZs+oE1JApnSifg=; b=g78cK97e6jy1HSDMV1q1fv/AXPkSdqR3jRkWrFJQLPhV2dtnFcGK5EPTVQ9Ho0xuqb R0GRN6Oh8fKOJC0Kbeh+TszpslNu1W0nGJBe+Agmj31arPBbifh3jxsv1aNI2aUGN+fH hIa6YBbKV/rBNKK/NSr+YcR5nbfVRxFoEcGcFPQamsjcAmNMhVTlygynQDt6cr286zFv C9tT5+zm/2b1JX3Spswabkjd99CchlPMYJKNQTQbYpbaZeDuXxeOl76XsxeUeZfC4+6L dgD/uZVO7uHMNOZyaFBei/1EyFdwPCqjMyQGrVK+/p6w2h/XLYvwtMLdf+pr1Ir7piad SqFQ== X-Gm-Message-State: AOAM533TvwksehxnWJCyirCnVhBV2Qr024jiR9qkR4LknNoZRa52iaJ+ OnZ/5EUt2U6tySDAax8MSoKRAWRrhKQFhw== X-Google-Smtp-Source: ABdhPJwgYtpr4QWc2UMhm39m9dC6A8IQcWgzn8m4I2yCVsXPbyKjVwy7MsWKaiHxFGASMEBnqvLF6g== X-Received: by 2002:a05:620a:1277:: with SMTP id b23mr1413331qkl.457.1616208692743; Fri, 19 Mar 2021 19:51:32 -0700 (PDT) Received: from [192.168.1.152] (pool-108-31-39-252.washdc.fios.verizon.net. [108.31.39.252]) by smtp.gmail.com with ESMTPSA id z4sm6147006qkb.94.2021.03.19.19.51.32 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Mar 2021 19:51:32 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) From: Sean Turner In-Reply-To: <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> Date: Fri, 19 Mar 2021 22:51:31 -0400 Cc: WPACK List Content-Transfer-Encoding: quoted-printable Message-Id: <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> To: Mark Nottingham X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Sat, 20 Mar 2021 02:51:37 -0000 Mark, You make a good point about the need for the additional I-Ds, because = the charter=E2=80=99s milestones actually call out 3 other I-Ds that = address the signing mechanism as well as privacy and security. To be = blunt, these other I-Ds have not yet been submitted. There was some = security-related text in the bundle document that was removed and Martin = Thomson had a content-based origin I-D. I am cautiously optimistic that = getting the bundling I-D adopted will encourage the other I-Ds to = surface because I strongly suspect that progress on the bundling I-D is = likely to grind to a halt without those I-Ds. I do not think that the = milestones, which are also a good year out of date at this point, should = hold us back from adopting the bundling I-D. But, the entire set of I-Ds = is required- it is the pact we made the IESG to get to done. spt > On Mar 16, 2021, at 00:59, Mark Nottingham wrote: >=20 > Hi Sean, >=20 > I don't have access to minutes of the meeting yet, so this may have = already been answered -- >=20 > The charter says that a use cases document, a privacy analysis = document, and a security analysis document will be adopted at the same = time as the bundling document. What's their status? >=20 > Cheers, >=20 >=20 >> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: >>=20 >> Based on interest expressed at IETF 110, this email starts the call = for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be = found here: >>=20 >> = https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ >>=20 >> This adoption call will run until March 30, 2021 at 2359 UTC. Please = indicate whether or not you would like to see this I-D adopted as a WG = item. Note that this is an adoption call for the draft as a starting = point for the bundle format. >>=20 >> Thanks, >>=20 >> spt (for the chairs) >> _______________________________________________ >> Wpack mailing list >> Wpack@ietf.org >> https://www.ietf.org/mailman/listinfo/wpack >=20 > -- > Mark Nottingham https://www.mnot.net/ >=20 From nobody Fri Mar 19 21:41:04 2021 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 5B6AD3A19EC for ; Fri, 19 Mar 2021 21:41:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.499 X-Spam-Level: X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 eIYXISMv2P0j for ; Fri, 19 Mar 2021 21:41:00 -0700 (PDT) Received: from mail-pj1-x1029.google.com (mail-pj1-x1029.google.com [IPv6:2607:f8b0:4864:20::1029]) (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 BF0763A19EB for ; Fri, 19 Mar 2021 21:41:00 -0700 (PDT) Received: by mail-pj1-x1029.google.com with SMTP id f2-20020a17090a4a82b02900c67bf8dc69so7673077pjh.1 for ; Fri, 19 Mar 2021 21:41:00 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=V6RX+Y1vzqJycEAfaBeSKVkpbxDNu6bo4UYApdWfGfI=; b=EGeAg7tlLJ1ILbc3R4Oq/rqkxx2ZGqKJn3ooCNcW4/Qw7GDP8GKIFapALzAyCoFZVw KZyApzDAWHjTnzjqzfXuAOFmOOZTfpo9Gp2aoMRpNVz5Gx3khaJ3acYc6j91vr0ro7Ds Z0psff8uTuiU4bqxDukhWW5f88iHQuF24kgNItK9NWg3w18qF0hhfYMzC+GYot4QC7pQ qEHFsYD0hJdyPrnWtruW79b/KPddEUPOaAf7Keg+zFZ3S9Gs67h7aafiObEQMvV5/6ym 8mRyYv7SF0djWHwMY7HUJ1F2BxfOS/JwuwPDJxZv7+jcWBNvsnHna2UXyfyaU3VJJRgw i1UA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=V6RX+Y1vzqJycEAfaBeSKVkpbxDNu6bo4UYApdWfGfI=; b=HD5jTfTslhdTUG1dYPnJoXdKoQNHJYLiwUiADVTAJtlEkR/ox5j3ykYA8otAbh3HY0 7rR/tKyXylwFEGdBCscAmhfdB/nBbO6/COm8J3qmgo2yXr6TOtUga1EN6JTivwKYLaDh qeJMx6QiM41POmojafl+7Upg3E/5NEn1qtuxSczw8h9qGi6wkcLNxypSc45nN9YExOiW TRwn9VUMVk5l7ZbRT8HUX6p/e7Tm/BvPFYsLdAb5rSCkqGqSHyoBCDPu5vdsKr24Wc/U 9izYcVmosmegiHbmJpitzN0zC09JMnY5WdfwJZqpUBArxrzFfeQMGYCPY0kjrUZ/QqXm W8jA== X-Gm-Message-State: AOAM532Tylw92V+2vZ1ogkt9HckEFWkkYnxGdVvcARe5NkZ7SdCIngwx rad4MXvxRxE9T4XCOklZmJU= X-Google-Smtp-Source: ABdhPJwHLLHall2Ty7wLc9CUxOZdMw+frMewGuK1FXpCP8YPzpnm5/8JsePtdlP2bs/dDh6qgzHVkA== X-Received: by 2002:a17:90b:1987:: with SMTP id mv7mr1833266pjb.152.1616215258899; Fri, 19 Mar 2021 21:40:58 -0700 (PDT) Received: from TVPC (c-73-158-116-21.hsd1.ca.comcast.net. [73.158.116.21]) by smtp.gmail.com with ESMTPSA id mp21sm7305113pjb.16.2021.03.19.21.40.57 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 19 Mar 2021 21:40:58 -0700 (PDT) Sender: Larry Masinter From: Larry Masinter X-Google-Original-From: "Larry Masinter" To: "'Sean Turner'" , "'Mark Nottingham'" Cc: "'WPACK List'" References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> In-Reply-To: <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> Date: Fri, 19 Mar 2021 21:40:57 -0700 Message-ID: <035001d71d43$390bfbe0$ab23f3a0$@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHCuov1cAgKT1cuIXpcs9J/HHdlsQHKj9G8AYX3fIyqmoj/kA== Content-Language: en-us Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Sat, 20 Mar 2021 04:41:02 -0000 Shouldn't you adopt the use cases first? The scope of activities and the = "Expected Performance" (section 3) are critical. The use cases I had expected that an IETF "Web Packaging" working group = to work on would include would be the ones that led to mime multipart:=20 Multipart/related, multipart/form-data, multipart/alternative, = multipart/byte-ranges Each has its own set of requirements, -- https://LarryMasinter.net https://interlisp.org > -----Original Message----- > From: Wpack On Behalf Of Sean Turner > Sent: Friday, March 19, 2021 7:52 PM > To: Mark Nottingham > Cc: WPACK List > Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled- > exchanges >=20 > Mark, >=20 > You make a good point about the need for the additional I-Ds, because = the > charter=E2=80=99s milestones actually call out 3 other I-Ds that = address the signing > mechanism as well as privacy and security. To be blunt, these other = I-Ds have > not yet been submitted. There was some security-related text in the = bundle > document that was removed and Martin Thomson had a content-based > origin I-D. I am cautiously optimistic that getting the bundling I-D = adopted will > encourage the other I-Ds to surface because I strongly suspect that = progress > on the bundling I-D is likely to grind to a halt without those I-Ds. I = do not think > that the milestones, which are also a good year out of date at this = point, > should hold us back from adopting the bundling I-D. But, the entire = set of I- > Ds is required- it is the pact we made the IESG to get to done. >=20 > spt >=20 > > On Mar 16, 2021, at 00:59, Mark Nottingham wrote: > > > > Hi Sean, > > > > I don't have access to minutes of the meeting yet, so this may have = already > been answered -- > > > > The charter says that a use cases document, a privacy analysis = document, > and a security analysis document will be adopted at the same time as = the > bundling document. What's their status? > > > > Cheers, > > > > > >> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: > >> > >> Based on interest expressed at IETF 110, this email starts the call = for > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be = found > here: > >> > >> https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled- > exchanges/ > >> > >> This adoption call will run until March 30, 2021 at 2359 UTC. = Please indicate > whether or not you would like to see this I-D adopted as a WG item. = Note > that this is an adoption call for the draft as a starting point for = the bundle > format. > >> > >> Thanks, > >> > >> spt (for the chairs) > >> _______________________________________________ > >> Wpack mailing list > >> Wpack@ietf.org > >> https://www.ietf.org/mailman/listinfo/wpack > > > > -- > > Mark Nottingham https://www.mnot.net/ > > >=20 > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack From nobody Sat Mar 20 18:35:36 2021 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 4EE413A117B for ; Sat, 20 Mar 2021 18:35:30 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 JMWDlOUI7h4P for ; Sat, 20 Mar 2021 18:35:25 -0700 (PDT) Received: from mail-qv1-xf2b.google.com (mail-qv1-xf2b.google.com [IPv6:2607:f8b0:4864:20::f2b]) (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 CA39A3A112F for ; Sat, 20 Mar 2021 18:35:25 -0700 (PDT) Received: by mail-qv1-xf2b.google.com with SMTP id by2so6982981qvb.11 for ; Sat, 20 Mar 2021 18:35:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=PbMRKRb2gYcLPFLyWBlJIb6HLdiP94bTtNanODM437c=; b=e+iTf2gbdJOw7DzLXZVlJpfEslFpvyeP7TmTvW1ryHDey7UGFG32ABLZDiK7pHBL60 M3FJbQzYCeeHirKIpFsCcQTB972KnyKR5CyFeyMFf1EJrfbpwCuMKgUgyCIUML8ONhqR 1+3r4fJGY2Ql/1YCKErpFfIBUczrnRGcJJeTM= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=PbMRKRb2gYcLPFLyWBlJIb6HLdiP94bTtNanODM437c=; b=DppSM66oQ3/8u8rQVZhMl5LWzrepoPQSVU1zupEGMeAei6UIPBw4kOnhbQEnB4ySxu BbycFdB7WwX78oDtvc2Ez+WGhoZKWDbwluuqw040fIfVwIrOpvgF9j8IZO3Oi8LAGWj4 vZHbZ/fdl6kRO9M9l4Hi5DkssMGkNQ150daR12/hzVvJt1j4os0Eh7TKSYWPP+jNB43r MEW7plHNkFKN72E5uiolM8JOzUvMKiI8k3DUufIH/k4Rg8sXdw/0W1qdZRHmuyfJvjCW 1MI2T8WSErKzlLZT1RlWo4WnHRUVcWQFUjI0jsEviCW9TREaHQ0vGTl5ovwAvVNiYOHy DjLA== X-Gm-Message-State: AOAM531RVj9r6nbk56Ia+nVrAvmghEX6KrKomTpJHt8Nr2IhA3w5kAPm FVk4yDW+TNsX29v9FM9rB+4dtNE4Tg5Ccw== X-Google-Smtp-Source: ABdhPJxtOxcA5kUpl4fi2JMSy4KGHMlCvDvX5R/lJ4Z1eGD8rlbk9Weuekk1QE726sqkTNmkOe4jvA== X-Received: by 2002:a0c:e84d:: with SMTP id l13mr15576434qvo.28.1616290521869; Sat, 20 Mar 2021 18:35:21 -0700 (PDT) Received: from [192.168.1.152] (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id f8sm7884843qkk.23.2021.03.20.18.35.21 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Mar 2021 18:35:21 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Message-Id: Date: Sat, 20 Mar 2021 21:35:20 -0400 To: WPACK List X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: [Wpack] wpack@ietf110: minutes posted 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, 21 Mar 2021 01:35:34 -0000 Hi! I have posted the minutes from WPACK=E2=80=99s session at IETF110: https://datatracker.ietf.org/meeting/110/materials/minutes-110-wpack-00 Thanks to Chris Lemmons for taking notes. Please send any comments to = wpack-chairs@ietf.org. spt= From nobody Sat Mar 20 19:27:28 2021 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 14C7B3A125F for ; Sat, 20 Mar 2021 19:27:27 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 1XeykP_MUPDw for ; Sat, 20 Mar 2021 19:27:23 -0700 (PDT) Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 F03603A125E for ; Sat, 20 Mar 2021 19:27:22 -0700 (PDT) Received: by mail-qt1-x82e.google.com with SMTP id a11so9889415qto.2 for ; Sat, 20 Mar 2021 19:27:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=from:content-transfer-encoding:mime-version:subject:message-id:date :to; bh=yxWaIKCAEjiQguTxVPbJI3zYn+qHH9sukXB5piskMGw=; b=RGJLSBMDk3gS4UnE9yD0VtFtJlLbD6l4MQ4t6W3ifSG0HHNKafmINEf06mCz/M/yud EG2TSLoEvJgAmqN0zDc8Z5MTeOPgKFTaz5qg/d+zvdO6SDR9Eu383CxcApdbsyXsqJEQ SgNChepobJ1/mY+W8MSy4q9s8wt12YwOOkKNI= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:message-id:date:to; bh=yxWaIKCAEjiQguTxVPbJI3zYn+qHH9sukXB5piskMGw=; b=cW+SVVhCcIxKQhvnr996CZeAOsUiKNHvBH/zxneWc4bDqtxctJqRjNNajCOEBnKXhx HAncQqJR9DQpoIY9pSukrJGQUZjoMv0kGxwe2BSjfaKIACXl53oX8tHq30quGLBccHQu lgNXR3EWQJdk69Bib8b3n1KgRy65ZsDtbyGpSL38PAD1dmMiHEoSSpMADJpffD0jrOHg wDCchLD0azVKObtMZqExm3yRDFM/0k6vQVCKrHS3Dtq7S/Xoi+G4HIkRKjCrZTqNRI+f IHXHYfQRcNGBczU5iPYzjAclwpvuDu1pzVPGXhr2gaaW2EWqWI8+K3SmLhIkjn5TBaMK x3uA== X-Gm-Message-State: AOAM532EYjBINr1+PdafR0kVkHrfrRkeK4/UVIWuSqgJrWLbBD3sBWZJ U+poFQrZzliiDsMsH8ZvLE4fwpHr/x33TA== X-Google-Smtp-Source: ABdhPJx3PAst5omT4QbFCkTRV46A7MAq0kMRc+za9KKl5Rglughmv24hZtiN9nHVz/HbicB6d3/IrQ== X-Received: by 2002:ac8:424e:: with SMTP id r14mr4781155qtm.140.1616293641157; Sat, 20 Mar 2021 19:27:21 -0700 (PDT) Received: from [192.168.1.152] (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id k127sm8175089qkc.88.2021.03.20.19.27.20 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 20 Mar 2021 19:27:20 -0700 (PDT) From: Sean Turner Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) Message-Id: Date: Sat, 20 Mar 2021 22:27:20 -0400 To: WPACK List X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: [Wpack] wpack-wg repo 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, 21 Mar 2021 02:27:27 -0000 Hi! I finally established a GitHub repo for this WG. It can be found here: https://github.com/wpack-wg/ I took the liberty of also updating the about page to include a link to it: https://datatracker.ietf.org/wg/wpack/about/ spt From nobody Mon Mar 22 09:16:04 2021 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 81F8C3A0BE9 for ; Mon, 22 Mar 2021 09:16:02 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.599 X-Spam-Level: X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.251, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 22k78X88oHs8 for ; Mon, 22 Mar 2021 09:15:57 -0700 (PDT) Received: from mail-qk1-x72d.google.com (mail-qk1-x72d.google.com [IPv6:2607:f8b0:4864:20::72d]) (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 43D1E3A0C1E for ; Mon, 22 Mar 2021 09:15:57 -0700 (PDT) Received: by mail-qk1-x72d.google.com with SMTP id x14so11116046qki.10 for ; Mon, 22 Mar 2021 09:15:57 -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=7iZwOaDiHsjE/VQLnReqCSNWn7YDRqk/77U5DJE8UMs=; b=MjtxL2Cy7TJMFAWsLr7OHbLLA0aSQHXhBsuOK8BbPo+KCQGGWWbZAyqpD0e5ZNiYPM IJpusP17eL8LlUqvLL4wj8tBHdHPCFVlFARzj8mcN1UnNyhG9YcXRWOpleAWu0AhJ0in QUXHUBfOoetMK9bWpvFNp2NbozzcNrRBTjWjc= 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=7iZwOaDiHsjE/VQLnReqCSNWn7YDRqk/77U5DJE8UMs=; b=OAz7sv9Gq4pfgjGrWfvRwZ1W4Ll41FAclsoGVi88V+Cs1Zw6gLxuJtTFjKaSHpi0IF gUxCBSr27RZXEszpxPw/JGV4XdY+2xZWX1y1cveyuWNXNbqTk8Pc8xYaGqVwJqnTvETx WzPXZZzUoT+bA1/sInOBU7o+8kRdtJRDvjvYPW+5dwcwEm3uigvdKILUBD56FpAv/5NQ p54k2rRBDGFkulQqwRn67pYlVyy72GlPTlL8Fx6evyquXiWU6tEjXoU/pnFlodeIVY+I fFXBqZE0i2naG2Tn/4DD4qoPoZ+5IZZoIOa604759QE7p6gN83C/IHp5u7FdohSRhmWm AO+A== X-Gm-Message-State: AOAM5328q0demg+XyxJCrFxixeRiUZW7IWjj8R3HdI+3W6VMiNBfmp9t USmEBQ8mWiyA2ewjFTZFYVCRgx/QEPhY7qeecHo6qA== X-Google-Smtp-Source: ABdhPJyj4guKGdU6yxqbzW06vb5ChwoxX3yfTrkla8OJPnTn2kKU38XsDTI1M6YFC1tNUpzp63QcL2vBI5gYP0To6TE= X-Received: by 2002:a37:9b0e:: with SMTP id d14mr754332qke.447.1616429755434; Mon, 22 Mar 2021 09:15:55 -0700 (PDT) MIME-Version: 1.0 References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> <035001d71d43$390bfbe0$ab23f3a0$@acm.org> In-Reply-To: <035001d71d43$390bfbe0$ab23f3a0$@acm.org> From: Jeffrey Yasskin Date: Mon, 22 Mar 2021 09:15:44 -0700 Message-ID: To: Larry Masinter Cc: Sean Turner , Mark Nottingham , WPACK List Content-Type: multipart/alternative; boundary="0000000000006115b305be226106" Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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, 22 Mar 2021 16:16:03 -0000 --0000000000006115b305be226106 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable We have an I-D for use cases, at https://tools.ietf.org/html/draft-yasskin-wpack-use-cases-01. I think it's ready for adoption, at least as a starting point for future work. Jeffrey On Fri, Mar 19, 2021 at 9:41 PM Larry Masinter wrote: > Shouldn't you adopt the use cases first? The scope of activities and the > "Expected Performance" (section 3) are critical. > The use cases I had expected that an IETF "Web Packaging" working group t= o > work on would include would be the ones that led to mime multipart: > Multipart/related, multipart/form-data, multipart/alternative, > multipart/byte-ranges > Each has its own set of requirements, > > -- > https://LarryMasinter.net https://interlisp.org > > > -----Original Message----- > > From: Wpack On Behalf Of Sean Turner > > Sent: Friday, March 19, 2021 7:52 PM > > To: Mark Nottingham > > Cc: WPACK List > > Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled- > > exchanges > > > > Mark, > > > > You make a good point about the need for the additional I-Ds, because t= he > > charter=E2=80=99s milestones actually call out 3 other I-Ds that addres= s the > signing > > mechanism as well as privacy and security. To be blunt, these other I-D= s > have > > not yet been submitted. There was some security-related text in the > bundle > > document that was removed and Martin Thomson had a content-based > > origin I-D. I am cautiously optimistic that getting the bundling I-D > adopted will > > encourage the other I-Ds to surface because I strongly suspect that > progress > > on the bundling I-D is likely to grind to a halt without those I-Ds. I > do not think > > that the milestones, which are also a good year out of date at this > point, > > should hold us back from adopting the bundling I-D. But, the entire set > of I- > > Ds is required- it is the pact we made the IESG to get to done. > > > > spt > > > > > On Mar 16, 2021, at 00:59, Mark Nottingham wrote: > > > > > > Hi Sean, > > > > > > I don't have access to minutes of the meeting yet, so this may have > already > > been answered -- > > > > > > The charter says that a use cases document, a privacy analysis > document, > > and a security analysis document will be adopted at the same time as th= e > > bundling document. What's their status? > > > > > > Cheers, > > > > > > > > >> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: > > >> > > >> Based on interest expressed at IETF 110, this email starts the call > for > > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found > > here: > > >> > > >> https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled- > > exchanges/ > > >> > > >> This adoption call will run until March 30, 2021 at 2359 UTC. Please > indicate > > whether or not you would like to see this I-D adopted as a WG item. Not= e > > that this is an adoption call for the draft as a starting point for the > bundle > > format. > > >> > > >> Thanks, > > >> > > >> spt (for the chairs) > > >> _______________________________________________ > > >> Wpack mailing list > > >> Wpack@ietf.org > > >> https://www.ietf.org/mailman/listinfo/wpack > > > > > > -- > > > Mark Nottingham https://www.mnot.net/ > > > > > > > _______________________________________________ > > Wpack mailing list > > Wpack@ietf.org > > https://www.ietf.org/mailman/listinfo/wpack > > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack > --0000000000006115b305be226106 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
We have an I-D for use cases, at=C2=A0https://tools.ietf.org= /html/draft-yasskin-wpack-use-cases-01. I think it's ready for adop= tion, at least as a starting point for future work.

Jeff= rey

On Fri, Mar 19, 2021 at 9:41 PM Larry Masinter <LMM@acm.org> wrote:
Shouldn't you adopt the use cases first? The= scope of activities and the "Expected Performance" (section 3) a= re critical.
The use cases I had expected that an IETF "Web Packaging" working= group to work on would include would be the ones that led to mime multipar= t:
Multipart/related, multipart/form-data, multipart/alternative, multipart/by= te-ranges
Each has its own set of requirements,

--
= https://LarryMasinter.net https://interlisp.org

> -----Original Message-----
> From: Wpack <wpack-bounces@ietf.org> On Behalf Of Sean Turner
> Sent: Friday, March 19, 2021 7:52 PM
> To: Mark Nottingham <mnot@mnot.net>
> Cc: WPACK List <wpack@ietf.org>
> Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-=
> exchanges
>
> Mark,
>
> You make a good point about the need for the additional I-Ds, because = the
> charter=E2=80=99s milestones actually call out 3 other I-Ds that addre= ss the signing
> mechanism as well as privacy and security. To be blunt, these other I-= Ds have
> not yet been submitted. There was some security-related text in the bu= ndle
> document that was removed and Martin Thomson had a content-based
> origin I-D. I am cautiously optimistic that getting the bundling I-D a= dopted will
> encourage the other I-Ds to surface because I strongly suspect that pr= ogress
> on the bundling I-D is likely to grind to a halt without those I-Ds. I= do not think
> that the milestones, which are also a good year out of date at this po= int,
> should hold us back from adopting the bundling I-D. But, the entire se= t of I-
> Ds is required- it is the pact we made the IESG to get to done.
>
> spt
>
> > On Mar 16, 2021, at 00:59, Mark Nottingham <mnot@mnot.net> wrote:
> >
> > Hi Sean,
> >
> > I don't have access to minutes of the meeting yet, so this ma= y have already
> been answered --
> >
> > The charter says that a use cases document, a privacy analysis do= cument,
> and a security analysis document will be adopted at the same time as t= he
> bundling document. What's their status?
> >
> > Cheers,
> >
> >
> >> On 16 Mar 2021, at 11:53 am, Sean Turner <sean@sn3rd.com> wrote:
> >>
> >> Based on interest expressed at IETF 110, this email starts th= e call for
> adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be foun= d
> here:
> >>
> >> https://datatracker.ietf.= org/doc/draft-yasskin-wpack-bundled-
> exchanges/
> >>
> >> This adoption call will run until March 30, 2021 at 2359 UTC.= Please indicate
> whether or not you would like to see this I-D adopted as a WG item. No= te
> that this is an adoption call for the draft as a starting point for th= e bundle
> format.
> >>
> >> Thanks,
> >>
> >> spt (for the chairs)
> >> _______________________________________________
> >> Wpack mailing list
> >> Wpack@iet= f.org
> >> https://www.ietf.org/mailman/listinfo/wpa= ck
> >
> > --
> > Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/
> >
>
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org=
> https://www.ietf.org/mailman/listinfo/wpack

_______________________________________________
Wpack mailing list
Wpack@ietf.org
https://www.ietf.org/mailman/listinfo/wpack
--0000000000006115b305be226106-- From nobody Mon Mar 22 14:58:19 2021 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 C33313A1370 for ; Mon, 22 Mar 2021 14:58:17 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -7.599 X-Spam-Level: X-Spam-Status: No, score=-7.599 tagged_above=-999 required=5 tests=[DKIMWL_WL_HIGH=-0.251, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, 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 gWhqg9jDIO1v for ; Mon, 22 Mar 2021 14:58:13 -0700 (PDT) Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 E27B13A1371 for ; Mon, 22 Mar 2021 14:58:12 -0700 (PDT) Received: by mail-qv1-xf2f.google.com with SMTP id x16so9484713qvk.3 for ; Mon, 22 Mar 2021 14:58:12 -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=radKoNNT6qyPw8H/t1anzSm/S5RCJ+D43gs2U3Rgm8Q=; b=KXGjT6Fkr93Md+3IaL0OkgTYLjeB0Xy06XZDxalVKTf7Iyc50sEmPG4M62gaI+v2Lr yl2d1K+ziXT7rJbyse+5156d915DjGRnepra1dvL1F0ieeR1IKBG9VKEMPUzwjCkgFaC 8dVtbPi0X5riv/TEX0+og250oQsXiJtbfw16E= 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=radKoNNT6qyPw8H/t1anzSm/S5RCJ+D43gs2U3Rgm8Q=; b=eVq9WYfdDRSx8RK1dt8XMFJCFwPzWBdzzt6bYbfZh4V/Qy5oWos8v3Bo/S3sK+g8Rc fvRWfVwwciE7yDC5TfIJfW8EX87tE8q7lJQ4gDOoWCdvNdN1RljDjPC7/ZEIpYJZv3bq S6uDeverKBKZC4bTXuas/axdBonmS5M11AZPJCbLtBu2FZraq773ekTtzT86coM+eJjG hL4rn53W4JmT4oD4TRyMPRR/Sk1xVQN4LhF4rBKJpiDCiMPjUkpQR3W8OIGTwO0yhDXE 0o+RI8Fc03oS91QdGliH2YUWtzsBn2F5Cw3hkZFInqDrXH1exFk4y5zac/+8pW9yfbIX qSeg== X-Gm-Message-State: AOAM531WB3D/mRtNc8xB/6kGbVNrsCU709zcVveDXlxMGxNAQk/VK5hi 22ugtaqzotQ2MPATWruHLkHQZUZl2W6Pac9tpLTfAIw0HgRvhg== X-Google-Smtp-Source: ABdhPJzYJE4hXkQjAP/k9JV09THYumXR7r8/FC47XXmuOFym3rHgZZn2a85wlmMMdsazjVbpZUstxYn1SA/ZxFL1y7M= X-Received: by 2002:ad4:4732:: with SMTP id l18mr1938368qvz.6.1616450290609; Mon, 22 Mar 2021 14:58:10 -0700 (PDT) MIME-Version: 1.0 References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> In-Reply-To: <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> From: Jeffrey Yasskin Date: Mon, 22 Mar 2021 14:57:59 -0700 Message-ID: To: Sean Turner Cc: Mark Nottingham , WPACK List Content-Type: multipart/alternative; boundary="0000000000005ec83b05be2729bc" Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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, 22 Mar 2021 21:58:18 -0000 --0000000000005ec83b05be2729bc Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable My understanding of the charter discussion was that we expected to need separate documents on privacy and security because signing-as-other-origins has such a big effect on the web origin model. It could make sense to hold up adoption of the signing document on those drafts being started. However, bundling without signing has a more localized effect, which should fit in the single document's privacy and security considerations section. We should continue to improve that section in the same way we plan to improve the rest of the draft. A use cases document is ready for adoption. It has, historically, not attracted much discussion from the people who asked me to write it, but if having it adopted by the WG would attract more interest, I'm all for it. I see Daniel also has some concrete changes to propose, I think especially around promoting https://wicg.github.io/webpackage/draft-yasskin-wpack-use-cases.html#name-s= ubresource-bundling to "essential". I think it's easier to tell whether the WG supports that sort of change after we adopt the document. Jeffrey On Fri, Mar 19, 2021 at 7:51 PM Sean Turner wrote: > Mark, > > You make a good point about the need for the additional I-Ds, because the > charter=E2=80=99s milestones actually call out 3 other I-Ds that address = the > signing mechanism as well as privacy and security. To be blunt, these oth= er > I-Ds have not yet been submitted. There was some security-related text in > the bundle document that was removed and Martin Thomson had a content-bas= ed > origin I-D. I am cautiously optimistic that getting the bundling I-D > adopted will encourage the other I-Ds to surface because I strongly suspe= ct > that progress on the bundling I-D is likely to grind to a halt without > those I-Ds. I do not think that the milestones, which are also a good yea= r > out of date at this point, should hold us back from adopting the bundling > I-D. But, the entire set of I-Ds is required- it is the pact we made the > IESG to get to done. > > spt > > > On Mar 16, 2021, at 00:59, Mark Nottingham wrote: > > > > Hi Sean, > > > > I don't have access to minutes of the meeting yet, so this may have > already been answered -- > > > > The charter says that a use cases document, a privacy analysis document= , > and a security analysis document will be adopted at the same time as the > bundling document. What's their status? > > > > Cheers, > > > > > >> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: > >> > >> Based on interest expressed at IETF 110, this email starts the call fo= r > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found > here: > >> > >> https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges= / > >> > >> This adoption call will run until March 30, 2021 at 2359 UTC. Please > indicate whether or not you would like to see this I-D adopted as a WG > item. Note that this is an adoption call for the draft as a starting poin= t > for the bundle format. > >> > >> Thanks, > >> > >> spt (for the chairs) > >> _______________________________________________ > >> Wpack mailing list > >> Wpack@ietf.org > >> https://www.ietf.org/mailman/listinfo/wpack > > > > -- > > Mark Nottingham https://www.mnot.net/ > > > > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack > --0000000000005ec83b05be2729bc Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
My understanding of the charter discussion was that w= e expected to need separate documents on privacy and security because signi= ng-as-other-origins has such a big effect on the web origin model. It could= make sense to hold up adoption of the signing document on those drafts bei= ng started.

However, bundling without signing has = a more localized effect, which should fit in the single document's priv= acy and security considerations section. We should continue to improve that= section in the same way we plan to improve the rest of the draft.

A use cases document is ready for adoption. It has, = historically, not attracted much discussion from the people who asked me to= write it, but if having it adopted by the WG would attract more interest, = I'm all for it. I see Daniel also has some concrete changes to propose,= I think especially around promoting=C2=A0h= ttps://wicg.github.io/webpackage/draft-yasskin-wpack-use-cases.html#name-su= bresource-bundling to "essential". I think it's easier to= tell=C2=A0whether the WG supports that sort of change after we adopt the d= ocument.

Jeffrey

On Fri, Mar 19, 2021 at 7:51 PM Se= an Turner <sean@sn3rd.com> wrot= e:
Mark,

You make a good point about the need for the additional I-Ds, because the c= harter=E2=80=99s milestones actually call out 3 other I-Ds that address the= signing mechanism as well as privacy and security. To be blunt, these othe= r I-Ds have not yet been submitted. There was some security-related text in= the bundle document that was removed and Martin Thomson had a content-base= d origin I-D. I am cautiously optimistic that getting the bundling I-D adop= ted will encourage the other I-Ds to surface because I strongly suspect tha= t progress on the bundling I-D is likely to grind to a halt without those I= -Ds. I do not think that the milestones, which are also a good year out of = date at this point, should hold us back from adopting the bundling I-D. But= , the entire set of I-Ds is required- it is the pact we made the IESG to ge= t to done.

spt

> On Mar 16, 2021, at 00:59, Mark Nottingham <mnot@mnot.net> wrote:
>
> Hi Sean,
>
> I don't have access to minutes of the meeting yet, so this may hav= e already been answered --
>
> The charter says that a use cases document, a privacy analysis documen= t, and a security analysis document will be adopted at the same time as the= bundling document. What's their status?
>
> Cheers,
>
>
>> On 16 Mar 2021, at 11:53 am, Sean Turner <sean@sn3rd.com> wrote:
>>
>> Based on interest expressed at IETF 110, this email starts the cal= l for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be fou= nd here:
>>
>> https://datatracker.= ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/
>>
>> This adoption call will run until March 30, 2021 at 2359 UTC. Plea= se indicate whether or not you would like to see this I-D adopted as a WG i= tem. Note that this is an adoption call for the draft as a starting point f= or the bundle format.
>>
>> Thanks,
>>
>> spt (for the chairs)
>> _______________________________________________
>> Wpack mailing list
>> Wpack@ietf.org=
>> https://www.ietf.org/mailman/listinfo/wpack<= br> >
> --
> Mark Nottingham=C2=A0 =C2=A0https://www.mnot.net/
>

_______________________________________________
Wpack mailing list
Wpack@ietf.org
https://www.ietf.org/mailman/listinfo/wpack
--0000000000005ec83b05be2729bc-- From nobody Mon Mar 22 15:20:42 2021 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 101CD3A13F6 for ; Mon, 22 Mar 2021 15:20:41 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -0.199 X-Spam-Level: X-Spam-Status: No, score=-0.199 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=igalia.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 A9E-QSmKl0t5 for ; Mon, 22 Mar 2021 15:20:35 -0700 (PDT) Received: from fanzine.igalia.com (fanzine.igalia.com [178.60.130.6]) (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 8F06E3A13F5 for ; Mon, 22 Mar 2021 15:20:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=igalia.com; s=20170329; h=Content-Transfer-Encoding:Content-Type:Message-ID:References:In-Reply-To:Subject:Cc:To:From:Date:MIME-Version; bh=QNitBY4QgiwDTdB0U/9MGsDuGdieU7szo3f/qEBZ+5A=; b=jqDALEEvQ3pKv1YUPVH09Y9koUk+IIRbq/FXEo6y6aRZwSr4jNVO7lir7u69J0QMi4UGhQopP2sI4WxjTlShzAmaLVPvunL3CiCIGsKOKDfUNdOhPqwJ8hw/IH3L3INmQIY45VX8dItQ/STozxmtNfkKAGtUJHi7fcQD72XdZDP1xksprNaiEm1BHVpB4kY1nI5PZpI41kTPxMhsInntz50U4UO9i5l0pqX7FGXo6fkodUgOeUFt/zQW3EMJ0losSMMHIwj2Z/VP0bqEF0wWcvMyjAE7U7zgMtOUpWaRISxKRWoDYzm84AHdTUBc4wvnBK2eMpgA9It8+tepwFYGTA==; Received: from maestria.local.igalia.com ([192.168.10.14] helo=mail.igalia.com) by fanzine.igalia.com with esmtps (Cipher TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim) id 1lOSuU-0000fb-Pn; Mon, 22 Mar 2021 23:20:30 +0100 Received: from webmail.service.igalia.com ([192.168.21.45]) by mail.igalia.com with esmtps (Cipher TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim) id 1lOSuR-00054j-UG; Mon, 22 Mar 2021 23:20:30 +0100 Received: from localhost ([127.0.0.1] helo=webmail.igalia.com) by webmail.service.igalia.com with esmtp (Exim 4.94) (envelope-from ) id 1lOSuM-0002HF-FZ; Mon, 22 Mar 2021 23:20:22 +0100 MIME-Version: 1.0 Date: Mon, 22 Mar 2021 23:20:22 +0100 From: Daniel Ehrenberg To: Jeffrey Yasskin Cc: Sean Turner , Mark Nottingham , WPACK List In-Reply-To: References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <0b73a28b79855d59278448d2debea672@igalia.com> X-Sender: littledan@igalia.com Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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, 22 Mar 2021 22:20:41 -0000 I'd have an easier time supporting the adoption of the use cases document if it did not prioritize use cases which depend on signed bundles. Maybe we should split the use cases document, and produce one which focuses only on unsigned bundle use cases and requirements. This could clarify the more limited issues in terms of privacy and security for the unsigned case. In addition to expressing the importance of subresource loading, I'd add further use cases which are not currently reflected (around tooling and serving conventions, which may have the biggest developer experience impact, even if it's not something that clients will receive directly). I will be happy to draft these proposals for changes, though it will probably take me a few months to find the time to do so properly. I'd like to learn more about how to write the kinds of use case documents that IETF tends to produce. Could anyone recommend any examples to reference? Thanks, Dan On 2021-03-22 22:57, Jeffrey Yasskin wrote: > My understanding of the charter discussion was that we expected to > need separate documents on privacy and security because > signing-as-other-origins has such a big effect on the web origin > model. It could make sense to hold up adoption of the signing document > on those drafts being started. > > However, bundling without signing has a more localized effect, which > should fit in the single document's privacy and security > considerations section. We should continue to improve that section in > the same way we plan to improve the rest of the draft. > > A use cases document [1] is ready for adoption. It has, historically, > not attracted much discussion from the people who asked me to write > it, but if having it adopted by the WG would attract more interest, > I'm all for it. I see Daniel also has some concrete changes to > propose, I think especially around promoting > https://wicg.github.io/webpackage/draft-yasskin-wpack-use-cases.html#name-subresource-bundling > to "essential". I think it's easier to tell whether the WG supports > that sort of change after we adopt the document. > > Jeffrey > > On Fri, Mar 19, 2021 at 7:51 PM Sean Turner wrote: > >> Mark, >> >> You make a good point about the need for the additional I-Ds, >> because the charter’s milestones actually call out 3 other I-Ds >> that address the signing mechanism as well as privacy and security. >> To be blunt, these other I-Ds have not yet been submitted. There was >> some security-related text in the bundle document that was removed >> and Martin Thomson had a content-based origin I-D. I am cautiously >> optimistic that getting the bundling I-D adopted will encourage the >> other I-Ds to surface because I strongly suspect that progress on >> the bundling I-D is likely to grind to a halt without those I-Ds. I >> do not think that the milestones, which are also a good year out of >> date at this point, should hold us back from adopting the bundling >> I-D. But, the entire set of I-Ds is required- it is the pact we made >> the IESG to get to done. >> >> spt >> >>> On Mar 16, 2021, at 00:59, Mark Nottingham wrote: >>> >>> Hi Sean, >>> >>> I don't have access to minutes of the meeting yet, so this may >> have already been answered -- >>> >>> The charter says that a use cases document, a privacy analysis >> document, and a security analysis document will be adopted at the >> same time as the bundling document. What's their status? >>> >>> Cheers, >>> >>> >>>> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: >>>> >>>> Based on interest expressed at IETF 110, this email starts the >> call for adoption of draft-yasskin-wpack-bundled-exchanges. The I-D >> can be found here: >>>> >>>> >> > https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ >>>> >>>> This adoption call will run until March 30, 2021 at 2359 UTC. >> Please indicate whether or not you would like to see this I-D >> adopted as a WG item. Note that this is an adoption call for the >> draft as a starting point for the bundle format. >>>> >>>> Thanks, >>>> >>>> spt (for the chairs) >>>> _______________________________________________ >>>> Wpack mailing list >>>> Wpack@ietf.org >>>> https://www.ietf.org/mailman/listinfo/wpack >>> >>> -- >>> Mark Nottingham https://www.mnot.net/ >>> >> >> _______________________________________________ >> Wpack mailing list >> Wpack@ietf.org >> https://www.ietf.org/mailman/listinfo/wpack > > > Links: > ------ > [1] https://tools.ietf.org/html/draft-yasskin-wpack-use-cases-01 > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack From nobody Tue Mar 23 06:06:58 2021 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 C46753A0B20 for ; Tue, 23 Mar 2021 06:06:56 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.099 X-Spam-Level: X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=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=sn3rd.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 cX9MsUpQ-h8L for ; Tue, 23 Mar 2021 06:06:51 -0700 (PDT) Received: from mail-qk1-x733.google.com (mail-qk1-x733.google.com [IPv6:2607:f8b0:4864:20::733]) (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 C8D0B3A0B1C for ; Tue, 23 Mar 2021 06:06:51 -0700 (PDT) Received: by mail-qk1-x733.google.com with SMTP id i9so14156189qka.2 for ; Tue, 23 Mar 2021 06:06:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sn3rd.com; s=google; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bMfKSc8ddmLOChy71+vM1YvS1aZhlcp1CvCt7xUEeII=; b=fI4JVX2D8EvnYIjat2YMFjH9hrTlCPvTD5ewhwIE2FwGf9ApbMjlOFBG7x7mFr7CIA icxoBis4dvWOAkkX6HFjPTwKq7TsG8yNgeZNeqh87dfPhZgRjqBSS9eYy/5MEGUj4VUd i3CG6mpjVJ+e5kcscIP7uZAJ03oZB2jLqM1vs= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=bMfKSc8ddmLOChy71+vM1YvS1aZhlcp1CvCt7xUEeII=; b=I96OGeJGe/TY2pgEr2stiX0mpI7rpoUPUQcfgDdrHBuSMNk3Yvm33zQK192ba9x6RF tPKF8+O3BmEyArXvXQNxrtTR7Cs2ktEm+O6Ag2gDBNoLPzps0JRkzvMUGheJz3OjwSne SjkqwRxhBtxeN/pF53QTdRt3Tj7mNxyaohkn7FNUzyz8IzbChO+bIGD4it6hPNSCEhRn Gfyhlks1f5a5Tw3WJnWgZKMlPGeoWm6oOPZySLR4Suij8ksdTdtMrylPCB78JabCZ6um EODKWdcMW03ApisEkrQJ7jfSiT1QbtiHQbMYww+PHVnuHDSV/AJS2cdSMRQy551NtRgS hxvA== X-Gm-Message-State: AOAM5325h0k1ilyriYiEqjcFyMAbeNXYBabdy5QQAMVhlOBgV6FZkdyL qb7hQT9taab9wab+YpT+nACNYA== X-Google-Smtp-Source: ABdhPJydzSqwYaev9kR1H8zGwx1h0LZx93FvDGk+lul4UBj2a55rQHtG2OHT764jnUGXlveneaS1bA== X-Received: by 2002:ae9:c007:: with SMTP id u7mr5219037qkk.60.1616504810411; Tue, 23 Mar 2021 06:06:50 -0700 (PDT) Received: from [192.168.1.152] (pool-71-178-177-131.washdc.fios.verizon.net. [71.178.177.131]) by smtp.gmail.com with ESMTPSA id b27sm13103300qkl.102.2021.03.23.06.06.49 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Mar 2021 06:06:49 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.60.0.2.21\)) From: Sean Turner In-Reply-To: <035001d71d43$390bfbe0$ab23f3a0$@acm.org> Date: Tue, 23 Mar 2021 09:06:48 -0400 Cc: Mark Nottingham , WPACK List Content-Transfer-Encoding: quoted-printable Message-Id: <752FE4AC-970C-4362-8289-3F90EC373932@sn3rd.com> References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> <035001d71d43$390bfbe0$ab23f3a0$@acm.org> To: Larry Masinter X-Mailer: Apple Mail (2.3654.60.0.2.21) Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Tue, 23 Mar 2021 13:06:57 -0000 Larry, It is possible that I am way more laissez-faire than most about adopting = I-Ds. I tend to think that clearing the initial hurdle of getting any = I-D into the WG will help other I-Ds get into the WG. Again, the bundle = I-D is just a starting point that is not going to race ahead of the = other I-Ds and will be informed by the use cases I-D regardless of with = the use cases I-D is adopted. And, I am also pretty happy to start a WG = adoption call for that I-D right after this current I-D completes, i.e., = in about a weeks time. spt > On Mar 20, 2021, at 00:40, Larry Masinter wrote: >=20 > Shouldn't you adopt the use cases first? The scope of activities and = the "Expected Performance" (section 3) are critical. > The use cases I had expected that an IETF "Web Packaging" working = group to work on would include would be the ones that led to mime = multipart:=20 > Multipart/related, multipart/form-data, multipart/alternative, = multipart/byte-ranges > Each has its own set of requirements, >=20 > -- > https://LarryMasinter.net https://interlisp.org >=20 >> -----Original Message----- >> From: Wpack On Behalf Of Sean Turner >> Sent: Friday, March 19, 2021 7:52 PM >> To: Mark Nottingham >> Cc: WPACK List >> Subject: Re: [Wpack] Call for adoption of = draft-yasskin-wpack-bundled- >> exchanges >>=20 >> Mark, >>=20 >> You make a good point about the need for the additional I-Ds, because = the >> charter=E2=80=99s milestones actually call out 3 other I-Ds that = address the signing >> mechanism as well as privacy and security. To be blunt, these other = I-Ds have >> not yet been submitted. There was some security-related text in the = bundle >> document that was removed and Martin Thomson had a content-based >> origin I-D. I am cautiously optimistic that getting the bundling I-D = adopted will >> encourage the other I-Ds to surface because I strongly suspect that = progress >> on the bundling I-D is likely to grind to a halt without those I-Ds. = I do not think >> that the milestones, which are also a good year out of date at this = point, >> should hold us back from adopting the bundling I-D. But, the entire = set of I- >> Ds is required- it is the pact we made the IESG to get to done. >>=20 >> spt >>=20 >>> On Mar 16, 2021, at 00:59, Mark Nottingham wrote: >>>=20 >>> Hi Sean, >>>=20 >>> I don't have access to minutes of the meeting yet, so this may have = already >> been answered -- >>>=20 >>> The charter says that a use cases document, a privacy analysis = document, >> and a security analysis document will be adopted at the same time as = the >> bundling document. What's their status? >>>=20 >>> Cheers, >>>=20 >>>=20 >>>> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: >>>>=20 >>>> Based on interest expressed at IETF 110, this email starts the call = for >> adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be = found >> here: >>>>=20 >>>> https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled- >> exchanges/ >>>>=20 >>>> This adoption call will run until March 30, 2021 at 2359 UTC. = Please indicate >> whether or not you would like to see this I-D adopted as a WG item. = Note >> that this is an adoption call for the draft as a starting point for = the bundle >> format. >>>>=20 >>>> Thanks, >>>>=20 >>>> spt (for the chairs) >>>> _______________________________________________ >>>> Wpack mailing list >>>> Wpack@ietf.org >>>> https://www.ietf.org/mailman/listinfo/wpack >>>=20 >>> -- >>> Mark Nottingham https://www.mnot.net/ >>>=20 >>=20 >> _______________________________________________ >> Wpack mailing list >> Wpack@ietf.org >> https://www.ietf.org/mailman/listinfo/wpack >=20 From nobody Tue Mar 23 23:11:09 2021 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 ABCFE3A2430 for ; Tue, 23 Mar 2021 23:11:07 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -1.499 X-Spam-Level: X-Spam-Status: No, score=-1.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.25, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3cg2nsLYvVyR for ; Tue, 23 Mar 2021 23:11:02 -0700 (PDT) Received: from mail-pl1-x631.google.com (mail-pl1-x631.google.com [IPv6:2607:f8b0:4864:20::631]) (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 B7D643A2433 for ; Tue, 23 Mar 2021 23:11:02 -0700 (PDT) Received: by mail-pl1-x631.google.com with SMTP id k4so7363827plk.5 for ; Tue, 23 Mar 2021 23:11:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=1VzAQjcJRI1yIUETzV5fEzlbZrgu+cOxJIRopXzOFSk=; b=NbtpPAtv8iqjgZUOX2Q7djiVlx4oAMmBgkYGmSOLUziDmvH4qqiLEO0fnUR4OgX7z2 /wBXAQ8OE71W6f0Lo+LRtHwRYdv+K/ViWwtN0fyw0xEVcb/FqdBue9mcwqYQOjOabNYB 4VB+Eri7x4lZZ5aaWl2VCs/Gsguwi39ijpHsU1veBJfg1mlWSUPHDc5xcxfDqNxtHB6K RxlbNql51PomYXQnOt6ZNM7wftacXYjJ13ANHuPCtFz6fEn4I3cCl86rh0ECwtEbyAXL AM8dZJ820c2TaTMzIN3o0mwreEU3N/TQkGyIZQz96UQ+OQxvt+1Je3cWWa5SlbX6ra6s YSzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:from:to:cc:references:in-reply-to:subject :date:message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=1VzAQjcJRI1yIUETzV5fEzlbZrgu+cOxJIRopXzOFSk=; b=txog3NF6ovIktohLFbTEosUGUofb33qgsnAwYwXhHBUeD+SHXRLQ+qnClEIRrVo5rI 66QS00QoGp3Ygco4NZTMNHsXbKPZBrs60FJkmxKwdu3UQOme6hEwMnBefWv78B+fuHMI UQY0Zn9j1GoRazSaNMG2+9o1lM4qMXY5t5EpTUxtEXsni9m78IU1/E2O3dM0h7ZvHNzt 5/157asisU19vZetTFqiBVgC6dK02bAcAgaH/UAwRkOhbzmTeVb1a69oBcUWDztA7mXP 9VdRnqaq/9ksCYYrMKHK/FC18QynHZXqebWi3ALsukmjkFiTSQUhXoE5GPvOqAKeCuYN b3gw== X-Gm-Message-State: AOAM531mB407VcYaFk5COeFwFQ/r5IAWP0BmFz/jMTngDcDJh3u1zhR4 Jfyq7g3TVh1JDoySYeBsASQUsQPkPc8= X-Google-Smtp-Source: ABdhPJza9z+NCrnin9Y36v1UQfXgaNnEAPShDnVv/gpsIxt32VCQuhBmsHDxNgsa9VKmTUAg4+LeSw== X-Received: by 2002:a17:90a:d3d8:: with SMTP id d24mr1728698pjw.166.1616566261409; Tue, 23 Mar 2021 23:11:01 -0700 (PDT) Received: from TVPC (c-73-158-116-21.hsd1.ca.comcast.net. [73.158.116.21]) by smtp.gmail.com with ESMTPSA id gt22sm1084711pjb.35.2021.03.23.23.10.59 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 Mar 2021 23:11:00 -0700 (PDT) Sender: Larry Masinter From: Larry Masinter X-Google-Original-From: "Larry Masinter" To: "'Sean Turner'" Cc: "'Mark Nottingham'" , "'WPACK List'" References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <3CF5CFC6-57AA-42AB-A42F-260DF8DA159B@mnot.net> <4896A451-ECFE-482F-B672-E6B257DEE521@sn3rd.com> <035001d71d43$390bfbe0$ab23f3a0$@acm.org> <752FE4AC-970C-4362-8289-3F90EC373932@sn3rd.com> In-Reply-To: <752FE4AC-970C-4362-8289-3F90EC373932@sn3rd.com> Date: Tue, 23 Mar 2021 23:10:59 -0700 Message-ID: <025201d72074$768fa6e0$63aef4a0$@acm.org> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQHCuov1cAgKT1cuIXpcs9J/HHdlsQHKj9G8AYX3fIwCAOPl9gK6SlEmqnsAPDA= Content-Language: en-us Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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: Wed, 24 Mar 2021 06:11:08 -0000 There was just recently a question about sub-resource access. I asked = about using byte-range retrieval. The answer was that cross-resource compression was important. If you = have a bundle with parts A and B such that compression C(A+B) is smaller = than C(A) + C(B) then byte ranges would not help. I don't mean to argue = this now, but just to point out an example where the relative priorities = for different use cases affect an important part of the fundamental part = of the design.=20 Of course you are aware that the details of how well non-HTTP = distribution and privacy considerations interact with the support of = various business models based on tracking end users. I asked about analyzing the use cases for MIME mutipart in the web: Multipart/related (mht -- for email and archive), multipart/form-data (for submitting forms including data) multipart/alternative (for sending data with support for (offline) = content negotiation multipart/byte-ranges (for responding to range requests) How would you do these using bundled-exchanges method? And why is it = better (or worse) than MIME-multipart? At the time, MIME multipart was chosen not because it was optimal for = any of its use cases but because it was adequate and well-understood. As far as laissez-faire goes, the working group charter is a published = plan. It is the agreement about your work, and it has milestones in https://datatracker.ietf.org/wg/wpack/about/ that imply a simultaneous = adoption of four drafts. Why aren=E2=80=99t you following your own published plan? Did = circumstances change?=20 If these were independent documents, then FCFS might be a reasonable = method. But they are not. The use cases and requirements do not depend = on the mechanism, but the converse is not true. -- https://LarryMasinter.net https://interlisp.org > -----Original Message----- > From: Sean Turner > Sent: Tuesday, March 23, 2021 6:07 AM > To: Larry Masinter > Cc: Mark Nottingham ; WPACK List > Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled- > exchanges >=20 > Larry, >=20 > It is possible that I am way more laissez-faire than most about = adopting I-Ds. I > tend to think that clearing the initial hurdle of getting any I-D into = the WG will > help other I-Ds get into the WG. Again, the bundle I-D is just a = starting point > that is not going to race ahead of the other I-Ds and will be informed = by the > use cases I-D regardless of with the use cases I-D is adopted. And, I = am also > pretty happy to start a WG adoption call for that I-D right after this = current I-D > completes, i.e., in about a weeks time. >=20 > spt >=20 > > On Mar 20, 2021, at 00:40, Larry Masinter wrote: > > > > Shouldn't you adopt the use cases first? The scope of activities and = the > "Expected Performance" (section 3) are critical. > > The use cases I had expected that an IETF "Web Packaging" working = group > to work on would include would be the ones that led to mime multipart: > > Multipart/related, multipart/form-data, multipart/alternative, > > multipart/byte-ranges Each has its own set of requirements, > > > > -- > > https://LarryMasinter.net https://interlisp.org > > > >> -----Original Message----- > >> From: Wpack On Behalf Of Sean Turner > >> Sent: Friday, March 19, 2021 7:52 PM > >> To: Mark Nottingham > >> Cc: WPACK List > >> Subject: Re: [Wpack] Call for adoption of > >> draft-yasskin-wpack-bundled- exchanges > >> > >> Mark, > >> > >> You make a good point about the need for the additional I-Ds, = because > >> the charter=E2=80=99s milestones actually call out 3 other I-Ds = that address > >> the signing mechanism as well as privacy and security. To be blunt, > >> these other I-Ds have not yet been submitted. There was some > >> security-related text in the bundle document that was removed and > >> Martin Thomson had a content-based origin I-D. I am cautiously > >> optimistic that getting the bundling I-D adopted will encourage the > >> other I-Ds to surface because I strongly suspect that progress on = the > >> bundling I-D is likely to grind to a halt without those I-Ds. I do > >> not think that the milestones, which are also a good year out of = date > >> at this point, should hold us back from adopting the bundling I-D. = But, the > entire set of I- Ds is required- it is the pact we made the IESG to = get to done. > >> > >> spt > >> > >>> On Mar 16, 2021, at 00:59, Mark Nottingham wrote: > >>> > >>> Hi Sean, > >>> > >>> I don't have access to minutes of the meeting yet, so this may = have > >>> already > >> been answered -- > >>> > >>> The charter says that a use cases document, a privacy analysis > >>> document, > >> and a security analysis document will be adopted at the same time = as > >> the bundling document. What's their status? > >>> > >>> Cheers, > >>> > >>> > >>>> On 16 Mar 2021, at 11:53 am, Sean Turner wrote: > >>>> > >>>> Based on interest expressed at IETF 110, this email starts the = call > >>>> for > >> adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be > >> found > >> here: > >>>> > >>>> https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled- > >> exchanges/ > >>>> > >>>> This adoption call will run until March 30, 2021 at 2359 UTC. > >>>> Please indicate > >> whether or not you would like to see this I-D adopted as a WG item. > >> Note that this is an adoption call for the draft as a starting = point > >> for the bundle format. > >>>> > >>>> Thanks, > >>>> > >>>> spt (for the chairs) > >>>> _______________________________________________ > >>>> Wpack mailing list > >>>> Wpack@ietf.org > >>>> https://www.ietf.org/mailman/listinfo/wpack > >>> > >>> -- > >>> Mark Nottingham https://www.mnot.net/ > >>> > >> > >> _______________________________________________ > >> Wpack mailing list > >> Wpack@ietf.org > >> https://www.ietf.org/mailman/listinfo/wpack > > From nobody Wed Mar 24 22:17:47 2021 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 353613A0F00 for ; Wed, 24 Mar 2021 22:17:46 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -2.1 X-Spam-Level: X-Spam-Status: No, score=-2.1 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=lowentropy.net header.b=hpd69ah6; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=o3QyWNyD 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 wR9d9YlWh7BI for ; Wed, 24 Mar 2021 22:17:41 -0700 (PDT) Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 491E43A0EFF for ; Wed, 24 Mar 2021 22:17:41 -0700 (PDT) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 27A72D45 for ; Thu, 25 Mar 2021 01:17:38 -0400 (EDT) Received: from imap10 ([10.202.2.60]) by compute1.internal (MEProxy); Thu, 25 Mar 2021 01:17:38 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm1; bh=RUlBIU8F22x+lsRsgqqvxKlBSNiTQz7 jdNGIW2M33lw=; b=hpd69ah6f6M2b1HDlxeDaXTgMCeNptUs1BrjmaAA5qGc2sh Nktp9j9hSU8LMMhr3tLCVtT1kA1uRVW5meEjNxhYb8ig4d4wqAJ/KufYQOeIrPAr kYPnoFE6fy5AnkrnrYJwDsRPhxjCffz75pIpkMQSUMFQOcYMe+hXUrH8nguRKMTN IkppFgpVd1z0AaxA7K+B0SpLOJvA8Ju5z1cQ476nkXbjqaKXvspO42tFb7TKoB3z V4DT7UJXbU/noiqzT/vOz8/EHPM+4aP106Nm1lqC0N/V3Q7SWwdO9gfDVIa2cALa 7OaoHRreQN1M/yHw4yf9nShCB4LBd1R2H2O57Xw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=RUlBIU 8F22x+lsRsgqqvxKlBSNiTQz7jdNGIW2M33lw=; b=o3QyWNyDNZC65YukyFkSLE ixBylvt98aW1vQ/Aa4SmFiAOKA3Z3FTn57GvzVuw/MyOzbSobhm9ztjzxpJyHf+l P4oJBu3Xa1AxOY0xwj6osL10v1IyAcAqvtjHi5jYm/pBaAqP1sgI4DSwhk4ELaUE y9mr/w4usgp6l/NTj8ojBslIuAlwK5WZlL2JhZlSswaurEa6tyhqmxyvautbigcy cSTBQbwJBomVtujBXQ1b7HDpUVz69KU1Xqk/Nkt8nfsot4X8Tcd0VRxkIv+Ppzsy 5HBPvo/WZs8lPBMpYbyTW5j/GX3V0QxfcJJS0sGnO/ILb165lnMCKB+p9C0XA5Ew == X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduledrudegledgkedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeelfedugfelgeeigfeuve eludejjeeutdelgedvteehueevhfdvhefggeeuffeivdenucffohhmrghinhepihgvthhf rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth X-ME-Proxy: Received: by mailuser.nyi.internal (Postfix, from userid 501) id C1EA34E0129; Thu, 25 Mar 2021 01:17:36 -0400 (EDT) X-Mailer: MessagingEngine.com Webmail Interface User-Agent: Cyrus-JMAP/3.5.0-alpha0-273-g8500d2492d-fm-20210323.002-g8500d249 Mime-Version: 1.0 Message-Id: <226f0aae-8736-4ddb-88d7-6a44d9731993@www.fastmail.com> In-Reply-To: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> Date: Thu, 25 Mar 2021 16:17:17 +1100 From: "Martin Thomson" To: wpack@ietf.org Content-Type: text/plain Archived-At: Subject: Re: [Wpack] =?utf-8?q?Call_for_adoption_of_draft-yasskin-wpack-bundl?= =?utf-8?q?ed-exchanges?= 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: Thu, 25 Mar 2021 05:17:46 -0000 Let's do it. I would like to see Dan's proposals adopted (mostly), and probably more than that, but as I said at the meeting, I have confidence that Jeffrey will do the right thing. We should continue chatting. On Tue, Mar 16, 2021, at 11:53, Sean Turner wrote: > Based on interest expressed at IETF 110, this email starts the call for > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found > here: > > https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ > > This adoption call will run until March 30, 2021 at 2359 UTC. Please > indicate whether or not you would like to see this I-D adopted as a WG > item. Note that this is an adoption call for the draft as a starting > point for the bundle format. > > Thanks, > > spt (for the chairs) > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack > From nobody Sun Mar 28 21:02:50 2021 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 76DEE3A1188 for ; Sun, 28 Mar 2021 21:02:48 -0700 (PDT) X-Virus-Scanned: amavisd-new at amsl.com X-Spam-Flag: NO X-Spam-Score: -9.249 X-Spam-Level: X-Spam-Status: No, score=-9.249 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.249, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no 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 1isu1dFl2TO4 for ; Sun, 28 Mar 2021 21:02:43 -0700 (PDT) Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 803F53A2F7A for ; Sun, 28 Mar 2021 21:02:43 -0700 (PDT) Received: by mail-wm1-x32f.google.com with SMTP id 12so5844965wmf.5 for ; Sun, 28 Mar 2021 21:02:43 -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=Sov4mVVSdncIe8Ba/hYPMqAwcqmd/2sDz2y+jQ5CZqg=; b=RLlAXjMq9liMoBU8QkxKeY5npdKdzWJMDnqpxEo+Ll0RFUjocw335b12z4HR6XrDb2 dXc/hBqXWU3uiUshYzfypqIQEePIMYhiTD1Shi3uduBjAGraOSNqwoCIA0GdQ6hIQBPW 6nWzxEKn95ZY1cuOW6i1jpEy6/2w4OXdg8eyQ= 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=Sov4mVVSdncIe8Ba/hYPMqAwcqmd/2sDz2y+jQ5CZqg=; b=iABvzf3K+0YhmPtVI+yrJnDAAfgNN7XQg86ikfXh86XyB2ZjA+iCs1ipFX2C3Z4BKJ 9XpdSuIiqt3wsnbmqVW6kpSGmZW5dqd9tN7X7UbG3wYBN4BI/YX/0ijwhSfb/623cy3X OeT5TamiedNBlOfYgvIuLWbBqC9rXOxPu9818tAo+FZfbsq9W1h12noAaHzLW0xaBk3T 736Opto/ooj2rN/XvQLzLJFNi5UnJc0OH+ayRgc7PhB6Mq8YgB90XrDMDZaF/0Qckk8V LLfn8tR0ZdvWCgc3jbD6d1429vahYTnyNzYa6TSceFGhEknlVhtX/pLZdaYq0V64XPDG MkFg== X-Gm-Message-State: AOAM5333fxo7g0FAK5sqdNY1x/Ay/J+68fF9x7/d/CwDwJv7ZpV9Wl2s 07jBTYktpx2YI0BvicRgFfxvnX+0rzfobGBywfvgIw== X-Google-Smtp-Source: ABdhPJz4QU6YyWc+kYjucuhcFw9kcB4DRC4lCa+NX8eAZWxE+YlyALCn7e7+5kLvDj/M2Pwa+vuMAX0HK2rCcUq/KNQ= X-Received: by 2002:a1c:f701:: with SMTP id v1mr22944499wmh.69.1616990560537; Sun, 28 Mar 2021 21:02:40 -0700 (PDT) MIME-Version: 1.0 References: <0C5B1FE3-AB3E-4074-AED9-93DD10B89BFD@sn3rd.com> <226f0aae-8736-4ddb-88d7-6a44d9731993@www.fastmail.com> In-Reply-To: <226f0aae-8736-4ddb-88d7-6a44d9731993@www.fastmail.com> From: Kinuko Yasuda Date: Mon, 29 Mar 2021 13:02:29 +0900 Message-ID: To: Martin Thomson Cc: wpack@ietf.org Content-Type: multipart/alternative; boundary="000000000000f7aba405bea4f396" Archived-At: Subject: Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges 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, 29 Mar 2021 04:02:48 -0000 --000000000000f7aba405bea4f396 Content-Type: text/plain; charset="UTF-8" I support this. I'd be happy to see this format and Dan's proposals will eventually have a good convergence, but I also believe that it's important to have the common base format for further discussion, and Jeffrey has been making a great judgement on addressing various discussion points. On Thu, Mar 25, 2021 at 2:17 PM Martin Thomson wrote: > Let's do it. > > I would like to see Dan's proposals adopted (mostly), and probably more > than that, but as I said at the meeting, I have confidence that Jeffrey > will do the right thing. We should continue chatting. > > On Tue, Mar 16, 2021, at 11:53, Sean Turner wrote: > > Based on interest expressed at IETF 110, this email starts the call for > > adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be found > > here: > > > > > https://datatracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/ > > > > This adoption call will run until March 30, 2021 at 2359 UTC. Please > > indicate whether or not you would like to see this I-D adopted as a WG > > item. Note that this is an adoption call for the draft as a starting > > point for the bundle format. > > > > Thanks, > > > > spt (for the chairs) > > _______________________________________________ > > Wpack mailing list > > Wpack@ietf.org > > https://www.ietf.org/mailman/listinfo/wpack > > > > _______________________________________________ > Wpack mailing list > Wpack@ietf.org > https://www.ietf.org/mailman/listinfo/wpack > --000000000000f7aba405bea4f396 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I suppor= t this.

I'd be happy to see=C2=A0this format and Dan's propos= als will eventually have a good convergence, but I also believe that it'= ;s important to have the common base format for further discussion, and Jef= frey has been making a great=C2=A0judgement on addressing various discussio= n points.

On Thu, Mar 25, 2021 at 2:17 PM Martin Thomson <mt@lowentropy.net> wrote:
Let's do it.

I would like to see Dan's proposals adopted (mostly), and probably more= than that, but as I said at the meeting, I have confidence that Jeffrey wi= ll do the right thing.=C2=A0 We should continue chatting.

On Tue, Mar 16, 2021, at 11:53, Sean Turner wrote:
> Based on interest expressed at IETF 110, this email starts the call fo= r
> adoption of draft-yasskin-wpack-bundled-exchanges. The I-D can be foun= d
> here:
>
>=C2=A0 =C2=A0https://data= tracker.ietf.org/doc/draft-yasskin-wpack-bundled-exchanges/
>
> This adoption call will run until March 30, 2021 at 2359 UTC. Please <= br> > indicate whether or not you would like to see this I-D adopted as a WG=
> item. Note that this is an adoption call for the draft as a starting <= br> > point for the bundle format.
>
> Thanks,
>
> spt (for the chairs)
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org=
> https://www.ietf.org/mailman/listinfo/wpack
>

_______________________________________________
Wpack mailing list
Wpack@ietf.org
https://www.ietf.org/mailman/listinfo/wpack
--000000000000f7aba405bea4f396--