Re: [Wpack] wpack: status
Hayato Ito <hayato@google.com> Tue, 29 November 2022 05:55 UTC
Return-Path: <hayato@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 AD471C14CF1B for <wpack@ietfa.amsl.com>; Mon, 28 Nov 2022 21:55:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -22.597
X-Spam-Level:
X-Spam-Status: No, score=-22.597 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, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C15UqN1xyPXF for <wpack@ietfa.amsl.com>; Mon, 28 Nov 2022 21:55:46 -0800 (PST)
Received: from mail-yw1-x112c.google.com (mail-yw1-x112c.google.com [IPv6:2607:f8b0:4864:20::112c]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1A44DC14CF12 for <wpack@ietf.org>; Mon, 28 Nov 2022 21:55:45 -0800 (PST)
Received: by mail-yw1-x112c.google.com with SMTP id 00721157ae682-3b48b139b46so128427597b3.12 for <wpack@ietf.org>; Mon, 28 Nov 2022 21:55:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=vta4f6SHg6N5SjRGczBSy6b6LpntmJeXIdJRz/9G1Xg=; b=nfLFAJt68W6UMvobu5apRc0TEiGTDqhk/lZINNFPaxYVWFpD/Q7qo2nz8hiaakN4HT wyVGTIOxaNLXkLXrR+yO8NAj4aC1Tpwio1gdnxa5D0pE7FR1B1u3kCQ73QCyNsUT8LVO I1TpxIvv8QTyeg7duRucAD44lFQwyAM220/ZYaKZhs2LPEp4NwgDady7g1SgsZ8Gnd2S AHo4oFlCJgzH7s8r1DROW5p4xfE3IKoxMdW8axTtO7qCOCVcOiZdViKB5wXgdA1zB7x+ DePn2y1zQt2rnz6QtTiU3LG6uR2+JR7T2cJp1o+OfRlhVgCIrEOmO6w7INPS7nYfq0QZ S4wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=vta4f6SHg6N5SjRGczBSy6b6LpntmJeXIdJRz/9G1Xg=; b=s8A0L/87JDdtYibaIcWbA4wvHY6hcq1ESiyf9JwMUSRSd8Kt+R4ZkgNLzEOpmh6TMV akqbR78v8JrFdWA4EWn9tG1fDhFnV2wmAoprglQ1cLuyVEhnJaA5eCyk1q1+H5lHv0l2 4hOJPX3eWRuckfblnDXqVF3x/XvIE6Wyd6g4IQWFQ0PJpJm9126AXowuDwtPDGYVteE0 QPPrEV+acuUCE8K98Npv841DteCadblMDfn09/L6lbhh5KulsZMXTw/i3GMPpCHzInkn yd6E4vjyE54ZtXl+wwJNv5QKTd3v5HCTOjorhExdTPZYZpkKWOlHYng2LksoTcRYqUzk xE4A==
X-Gm-Message-State: ANoB5pnapgTZZvxSbEZVA5gUGtoDmntY+LlYcteM7CPWeGVgsz0ZUy3K yrpWFuPbDpteQPhzETVWvb6uU0b1IsrNNEeLaif6IQ==
X-Google-Smtp-Source: AA0mqf5gH40LSDuFR69b116iPEZFSic7sIybSvWCWlht+N0QL9Z7vBdczury5QVdwZOM/188W3UkgM5u2qTfwsSAK4s=
X-Received: by 2002:a81:f80c:0:b0:3b8:45f4:7364 with SMTP id z12-20020a81f80c000000b003b845f47364mr20385290ywm.6.1669701344980; Mon, 28 Nov 2022 21:55:44 -0800 (PST)
MIME-Version: 1.0
References: <05FF4089-61DA-4B7E-AB8A-30B04E814F08@sn3rd.com> <e1459bc9-814d-4e97-9a89-8ae723b4e3a8@app.fastmail.com> <92C52288-2FD2-4BC1-8955-7BA2EA75330B@mnot.net> <CAG3f7MhVCNEFD+=Xr3=3B+VrzFSVGeY31vUfkm-6hHT=xJfEJA@mail.gmail.com>
In-Reply-To: <CAG3f7MhVCNEFD+=Xr3=3B+VrzFSVGeY31vUfkm-6hHT=xJfEJA@mail.gmail.com>
From: Hayato Ito <hayato@google.com>
Date: Tue, 29 Nov 2022 14:55:33 +0900
Message-ID: <CAFpjS_38M=dWTmKXDAmWM1e__0SC1sw7ZbWsoFtZy+8LM+=WFg@mail.gmail.com>
To: Shivan Kaul Sahib <shivankaulsahib@gmail.com>
Cc: Mark Nottingham <mnot=40mnot.net@dmarc.ietf.org>, Martin Thomson <mt@lowentropy.net>, Sean Turner <sean@sn3rd.com>, WPACK List <wpack@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008cc5b205ee95a35a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/FbjvALSuQuOyJgzJkxb4JCpwknM>
Subject: Re: [Wpack] wpack: status
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.39
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: Tue, 29 Nov 2022 05:55:49 -0000
Hi folks, I'm Hayato, working on Web Bundles in Google. I've recently taken over the spec leadership from Jeffrey Yasskin. As Sean mentioned, we are still motivated to publish the I-D, and are willing to make changes based on IETF input. In particular, I appreciate IETF's input on this open issue: https://github.com/wpack-wg/bundled-responses/issues/18, which I want to resolve. > If the WG closes, there would also not be the IETF change control expected of a Standards Track document, though it would still have value documenting an Internet exchange format. In that event, it would be better suited to go through the Independent Submissions Editor with labeling that reflects its provenance as a Google format. Let me take this back as Google's homework. I'm not sure what track is suitable yet. Thanks! On Tue, Nov 29, 2022 at 1:46 PM Shivan Kaul Sahib <shivankaulsahib@gmail.com> wrote: > +1 as well, though I’m not sure what the value of going through ISE would > be either. > > On Mon, Nov 28, 2022 at 5:16 PM Mark Nottingham <mnot= > 40mnot.net@dmarc.ietf.org> wrote: > >> +1 to that way forward. >> >> > On 29 Nov 2022, at 11:38 am, Martin Thomson <mt@lowentropy.net> wrote: >> > >> > On Tue, Nov 29, 2022, at 03:40, Sean Turner wrote: >> >> For draft-ietf-wpack-bundled-responses, the authors have indicated >> that >> >> they are still motivated to publish the I-D, and are willing to make >> >> changes based on IETF input. But, they need input. The issues we see >> >> are that, without the security and privacy documents, the solution is >> >> not likely to make it through the IESG. >> > >> > If there is not a working group working on this document, we shouldn't >> push it. We've had a few years for that input to be solicited and acted >> upon; doing a last minute cram probably isn't going to produce the sort of >> results we'd be proud of. >> > >> > If the authors are committed to publication (perhaps because this is >> what Chrome is shipping), then might I recommend asking our Independent >> Submissions Editor to help publish a document for that. That might require >> some work, but it avoids the really difficult stuff >> > >> > _______________________________________________ >> > 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 > -- Hayato
- [Wpack] wpack: status Sean Turner
- Re: [Wpack] wpack: status Martin Thomson
- Re: [Wpack] wpack: status Mark Nottingham
- Re: [Wpack] wpack: status Shivan Kaul Sahib
- Re: [Wpack] wpack: status Hayato Ito
- Re: [Wpack] wpack: status Sean Turner
- Re: [Wpack] wpack: status Francesca Palombini