[Wpack] Follow-up to the IETF 102 side meeting: interested parties?

Kenji Baheux <kenjibaheux@chromium.org> Tue, 14 August 2018 04:15 UTC

Return-Path: <kenjibaheux@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 B38BE130E2D for <wpack@ietfa.amsl.com>; Mon, 13 Aug 2018 21:15:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.509
X-Spam-Level:
X-Spam-Status: No, score=-9.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, 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 oYgKDbjzyf_k for <wpack@ietfa.amsl.com>; Mon, 13 Aug 2018 21:15:33 -0700 (PDT)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 D6188130EF6 for <wpack@ietf.org>; Mon, 13 Aug 2018 21:15:32 -0700 (PDT)
Received: by mail-lf1-x12a.google.com with SMTP id n96-v6so12785643lfi.1 for <wpack@ietf.org>; Mon, 13 Aug 2018 21:15:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:from:date:message-id:subject:to:cc; bh=OYk/yyKtRvNunSkPjvx0vRkL8c5yidKi+KRjFBdw6SQ=; b=n2QDSK/Mcc3r2W8GRXlAUBDeVTZKFtHS4BWiAhMY/SwwHQcGeMEio9gSIWN7TZEK1h cqbxQxl7Kp53e51j8bD7MK7COXOkdvyFRh1b4ImsuW9zDwr4hfr+XC/b8w+sjUX79Eox JxOpqz6xmFvSEzI+CoqeRoc7Fe8WAyIHLwe84=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=OYk/yyKtRvNunSkPjvx0vRkL8c5yidKi+KRjFBdw6SQ=; b=ovL34jDhW4RpO/yVzI8FGDCcN+4DoyIap5eV2xaY0BgzhM0yfvbvxb/B9ysN8CFxCl Cgfdcbzjx0WC8AyDuchHbzPNBkgZPainpqscP0rt5yxhFpt9dRw+N67Aj149cVsahmnF 9s+iPB5MPTwMyset1L5e8OgcVHIb1le+eEOXV7bpXuyMMgSdIeqLTNP0ehGw6qevsUa1 Pb9i8DSMG2KgVc+tC4YHrBgOSeUEKCXe3pQ/1iRPkbfBXiRMawYzBYjbCqDyR70rlRC2 Cw5UITv/0Q1ZxsZXM7FEgUawFTVmhGeByAttkoWA7Nfeh6BkvY57m4noykOSDxFptbTq Ks3Q==
X-Gm-Message-State: AOUpUlHcUbwo74A0Kj/oIOrHJssUqABkSblLoIxFTfOj3h8C/Yt1CS5N Wp3H4BBzzhnLUUq+Ij6vLDYApMGviVhj5zJl0QC/KjS6Vy8=
X-Google-Smtp-Source: AA+uWPw/eV5jJ7ckPPoJTmBILNo6M9VazsrUbgI5QpY3e4niro2k4mGDm+dw/KMzGG1o8S32BMIRk+LkEjCQAgUCgK0=
X-Received: by 2002:a19:c742:: with SMTP id x63-v6mr12843384lff.9.1534220130410; Mon, 13 Aug 2018 21:15:30 -0700 (PDT)
MIME-Version: 1.0
From: Kenji Baheux <kenjibaheux@chromium.org>
Date: Tue, 14 Aug 2018 00:15:18 -0400
Message-ID: <CADWWn7WMD5NdPM0XaAbgcXgVqkTE+C2oJOR1rHeXPKVV6omfpQ@mail.gmail.com>
To: wpack@ietf.org
Cc: Jeffrey Yasskin <jyasskin@chromium.org>
Content-Type: multipart/alternative; boundary="000000000000e20f9905735d75f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/LRgYAc8peI-tPYkfu4rkYWxsbYA>
X-Mailman-Approved-At: Thu, 16 Aug 2018 08:04:01 -0700
Subject: [Wpack] Follow-up to the IETF 102 side meeting: interested parties?
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.27
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, 14 Aug 2018 04:15:35 -0000

Hi,

I heard from Jeffrey Yasskin that a few attendees of the IETF 102 side
meeting for Web Packaging, seemed quite interested in the technology or its
use cases.

I would love to know more about your needs, feedback or questions.

Feel free to reach out directly or via this mailing list.
Thanks!

PS: Chrome has an experimental implementation of signed exchange which can
be enabled via chrome://flags/#enable-signed-http-exchange  (I would be
happy to help anyone get started).