Re: HTTPBIS summary for IETF 119

Rahul Gupta <cxres@protonmail.com> Mon, 18 March 2024 03:49 UTC

Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=ietf.org@listhub.w3.org>
X-Original-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Delivered-To: ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 85868C14F6B2 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 17 Mar 2024 20:49:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.856
X-Spam-Level:
X-Spam-Status: No, score=-2.856 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, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=w3.org header.b="Qhi+bFlI"; dkim=pass (2048-bit key) header.d=w3.org header.b="RFFjL8Ap"; dkim=pass (2048-bit key) header.d=protonmail.com header.b="naLzJfhy"
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 poIe3KN8tl2o for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Sun, 17 Mar 2024 20:49:28 -0700 (PDT)
Received: from lyra.w3.org (lyra.w3.org [128.30.52.18]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 97BEFC14F6AE for <httpbisa-archive-bis2Juki@ietf.org>; Sun, 17 Mar 2024 20:49:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Subject:Content-Type:MIME-Version:References:In-Reply-To:Message-ID: From:To:Date:Cc:Reply-To; bh=I4y8xxQt0Bm0TNNAEJNc132lm1A/HxYtvIuiSxzDFc8=; b= Qhi+bFlITUJd1He0zBtyw+tGox8Bc7dKE0caPWd3Z+p+nloS41qhx79cucLSlp8Zy16vWe9W2Kp9f U4JnINKSKVrTEK2aVkGmLuFnknXax3zOBmTF24aEfvtMzfEp/SBO5Hrwy0JcDpCNMm3yA/UPoJPAM y8gJcB62AMi7+/xJzrYlYMQDxNRSUkuu9HgYmV5kG3G//IWAm+AUB9mpgH4SzsIsNB4Ruo+sgnqUB 6MspHsddZyQh3K5gHLdLU/Bf4jRFS52fdHf4kDAt6WSzk4mvvzeppK3pN6Np3Uab5WEeNSbQ3XP1y Iyxkcmg1vyWrCZpHoBoESfK8R7rZ8annTw==;
Received: from lists by lyra.w3.org with local (Exim 4.94.2) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1rm3zt-00FeXO-IU for ietf-http-wg-dist@listhub.w3.org; Mon, 18 Mar 2024 03:49:13 +0000
Resent-Date: Mon, 18 Mar 2024 03:49:13 +0000
Resent-Message-Id: <E1rm3zt-00FeXO-IU@lyra.w3.org>
Received: from puck.w3.org ([34.196.82.207]) by lyra.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <cxres@protonmail.com>) id 1rm3zp-00FeWN-LZ for ietf-http-wg@listhub.w3.org; Mon, 18 Mar 2024 03:49:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=w3.org; s=s1; h=Content-Type:MIME-Version:References:In-Reply-To:Message-ID:Subject: From:To:Date:Cc:Reply-To; bh=I4y8xxQt0Bm0TNNAEJNc132lm1A/HxYtvIuiSxzDFc8=; t=1710733749; x=1711597749; b=RFFjL8ApbB+Q8CUbrbODrDM67pWqIF7KfHw1C+2VdtnShXo 8dmaZrCYF5teWL/2feHRYpRZadnCABqIdJcEw62vumUXbaMESoeCvF2SOKA4mz5KQ5qH5dOqghRRo Vey1rrf5o34Tbitebea0BII9nnewgLWXxOCfpVKct+zg4/sX/Bc8hq3tgDwUJZF/seg5UA6OQCLcA iy8rTI5mV8Hrnde4ADWt8j2UJCYzoKYR0bQp9vJoWrB3evpe7U1ENPbrMU3TuZRPjqjPkadmvT0jW u511rp7sXYSYsWe6EURmLGUaA51hLbpNo7hhxgs8KcSVEJFRvu2t+Rv4vC6492nw==;
Received-SPF: pass (puck.w3.org: domain of protonmail.com designates 185.70.40.137 as permitted sender) client-ip=185.70.40.137; envelope-from=cxres@protonmail.com; helo=mail-40137.protonmail.ch;
Received: from mail-40137.protonmail.ch ([185.70.40.137]) by puck.w3.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from <cxres@protonmail.com>) id 1rm3zn-00963Y-1F for ietf-http-wg@w3.org; Mon, 18 Mar 2024 03:49:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail3; t=1710733742; x=1710992942; bh=I4y8xxQt0Bm0TNNAEJNc132lm1A/HxYtvIuiSxzDFc8=; h=Date:To:From:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector; b=naLzJfhyAitvvJcxqfp9fypW4mhmivQ4TxuNirGBoEB2bvhvNzhy4o1FKeUyZ/yh4 UpsGZAKVC8/pcjojXz0WuLFcU8S8MD1+SD+H+wfH2DHvrMBZZDt2g8tN2/nvPJRSPz 5t7inF1zrOzuSrils7t3f1f1pbfxuMZ8EJJhQdPjIEgyGWYS7lvvL9JF2VIMSS8jpV NQxf7idmjO0pVBkrnw0UUcNgx+SXdRlsjYAGM5rFGsSENyDkyeb1nvVCW2Ne9RgQ1V kKuVZb/hfeKICHLfeWF2dVTNuW6hmSUiTbYmd/zeXsif2FTDrKtGTb2SSnDklPf71/ o4zhISwlnlLQw==
Date: Mon, 18 Mar 2024 03:48:37 +0000
To: Tommy Pauly <tpauly@apple.com>, Mark Nottingham <mnot@mnot.net>, "ietf-http-wg@w3.org" <ietf-http-wg@w3.org>
From: Rahul Gupta <cxres@protonmail.com>
Message-ID: <wa9o40acbyaNCj5uwgSM47SOmth4s1V3ChAOE2ie9BnWMgTwFUQuN1qMitSIaD9y-AcYW25_uaiUfsETJOp4ZBq70WWoxspP4bWtfuX22CI=@protonmail.com>
In-Reply-To: <04F5BBEE-B5FD-44CE-8990-0FEC156A876F@apple.com>
References: <04F5BBEE-B5FD-44CE-8990-0FEC156A876F@apple.com>
Feedback-ID: 919445:user:proton
MIME-Version: 1.0
Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="pgp-sha256"; boundary="------d3f7be5c572b17b180b8b2ce413dd0f9f3211341ec08209c1939f5f28a2588c6"; charset="utf-8"
X-W3C-Hub-DKIM-Status: validation passed: (address=cxres@protonmail.com domain=protonmail.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-6.1
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, DMARC_PASS=-0.001, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, W3C_AA=-1, W3C_DB=-1, W3C_IRA=-1, W3C_WL=-1
X-W3C-Scan-Sig: puck.w3.org 1rm3zn-00963Y-1F 8aeef5392ad47d0bffabd67a5ff01df4
X-Original-To: ietf-http-wg@w3.org
Subject: Re: HTTPBIS summary for IETF 119
Archived-At: <https://www.w3.org/mid/wa9o40acbyaNCj5uwgSM47SOmth4s1V3ChAOE2ie9BnWMgTwFUQuN1qMitSIaD9y-AcYW25_uaiUfsETJOp4ZBq70WWoxspP4bWtfuX22CI=@protonmail.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/51892
X-Loop: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list
List-Id: <ietf-http-wg.w3.org>
List-Help: <https://www.w3.org/email/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>

Hi Tommy and Mark,

Just a polite reminder that PREP is still an active draft. While I have not been able to do much work on it, I am in the process of publishing an express middleware this week itself and updating the draft with that information (and minor fixes primarily circumventing the lack of nesting in structured fields).

While both open source servers (CSS and NSS) in Solid are looking to implement PREP, implementation is only starting about now, with the first meeting scheduled next week.

I would appreciate it if you could mention this in the Friday session and perhaps gauge/give me guidance of the interest in the group in adopting PREP and what I might do to hasten the process.

Thanks in advance,

BR/Rahul



On Monday, March 18th, 2024 at 5:33 AM, Tommy Pauly <tpauly@apple.com> wrote:

> Hello WIT area,
> 

> Our ADs have asked for reports on current work in the various WIT area working groups.
> 

> The work that will be discussed this week in the HTTP WG (HTTPBIS) includes:
> 

> - Resumable uploads for HTTP
> - Adding “grouping” to HTTP caches
> - HTTP compression dictionaries
> - “Unprompted” HTTP authentication that allows clients to authenticate, without servers revealing that they expect authentication to clients that don’t have credentials
> 

> There’s also discussion this week both in HTTP, QUIC, and a side meeting about a proposal for running HTTP/3 on streams. Today, HTTP/3 runs on QUIC, and HTTP/2 runs on TLS+TCP, but this is a proposal to run HTTP/3 over TLS+TCP as well. If you’re interested in this discussion, please join the meetings!
> 

> You can find the full agenda here: https://datatracker.ietf.org/doc/agenda-119-httpbis/
> 

> Thanks,
> Tommy & Mark, HTTPBIS WG chairs