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

Jeffrey Yasskin <jyasskin@chromium.org> Mon, 22 March 2021 16:16 UTC

Return-Path: <jyasskin@google.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81F8C3A0BE9 for <wpack@ietfa.amsl.com>; 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 <wpack@ietfa.amsl.com>; 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 <wpack@ietf.org>; Mon, 22 Mar 2021 09:15:57 -0700 (PDT)
Received: by mail-qk1-x72d.google.com with SMTP id x14so11116046qki.10 for <wpack@ietf.org>; 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 <jyasskin@chromium.org>
Date: Mon, 22 Mar 2021 09:15:44 -0700
Message-ID: <CANh-dX=+waBdCJgzrZNjPpMXF5R-4+KL4K=0j0q4+V4=DE_K1w@mail.gmail.com>
To: Larry Masinter <LMM@acm.org>
Cc: Sean Turner <sean@sn3rd.com>, Mark Nottingham <mnot@mnot.net>, WPACK List <wpack@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006115b305be226106"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/dBNsMKoCd6JwXuLzteALQEwVR0c>
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: Mon, 22 Mar 2021 16:16:03 -0000

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 <LMM@acm.org> 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 <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
>
> _______________________________________________
> Wpack mailing list
> Wpack@ietf.org
> https://www.ietf.org/mailman/listinfo/wpack
>