Re: [Wpack] Call for adoption of draft-yasskin-wpack-bundled-exchanges

Larry Masinter <LMM@acm.org> Sat, 20 March 2021 04:41 UTC

Return-Path: <masinter@gmail.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B6AD3A19EC for <wpack@ietfa.amsl.com>; 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 <wpack@ietfa.amsl.com>; 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 <wpack@ietf.org>; Fri, 19 Mar 2021 21:41:00 -0700 (PDT)
Received: by mail-pj1-x1029.google.com with SMTP id f2-20020a17090a4a82b02900c67bf8dc69so7673077pjh.1 for <wpack@ietf.org>; 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 <masinter@gmail.com>
From: Larry Masinter <LMM@acm.org>
X-Google-Original-From: "Larry Masinter" <lmm@acm.org>
To: 'Sean Turner' <sean@sn3rd.com>, 'Mark Nottingham' <mnot@mnot.net>
Cc: 'WPACK List' <wpack@ietf.org>
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: <https://mailarchive.ietf.org/arch/msg/wpack/5DaXAQVp7psQbOh35688yuwe5ec>
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 <wpack.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpack>, <mailto:wpack-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wpack/>
List-Post: <mailto:wpack@ietf.org>
List-Help: <mailto:wpack-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpack>, <mailto:wpack-request@ietf.org?subject=subscribe>
X-List-Received-Date: 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: 
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 <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’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 <mnot@mnot.net> 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 <sean@sn3rd.com> 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