Re: Draft v1 Update for Resumable Uploads
Guoye Zhang <guoye_zhang@apple.com> Thu, 23 June 2022 00:50 UTC
Return-Path: <ietf-http-wg-request+bounce-httpbisa-archive-bis2juki=lists.ie@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 F236EC147930 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 22 Jun 2022 17:50:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.505
X-Spam-Level:
X-Spam-Status: No, score=-3.505 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.745, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.25, HTML_MESSAGE=0.001, MAILING_LIST_MULTI=-1, RCVD_IN_MSPIKE_H2=-0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=apple.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 X0L5EMFZxq37 for <ietfarch-httpbisa-archive-bis2Juki@ietfa.amsl.com>; Wed, 22 Jun 2022 17:50:11 -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 D3160C14F742 for <httpbisa-archive-bis2Juki@lists.ietf.org>; Wed, 22 Jun 2022 17:50:10 -0700 (PDT)
Received: from lists by lyra.w3.org with local (Exim 4.92) (envelope-from <ietf-http-wg-request@listhub.w3.org>) id 1o4Azn-0002hg-3x for ietf-http-wg-dist@listhub.w3.org; Thu, 23 Jun 2022 00:46:55 +0000
Resent-Date: Thu, 23 Jun 2022 00:46:55 +0000
Resent-Message-Id: <E1o4Azn-0002hg-3x@lyra.w3.org>
Received: from mimas.w3.org ([128.30.52.79]) by lyra.w3.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <guoye_zhang@apple.com>) id 1o4Azm-0002gn-3L for ietf-http-wg@listhub.w3.org; Thu, 23 Jun 2022 00:46:54 +0000
Received: from rn-mailsvcp-ppex-lapp34.rno.apple.com ([17.179.253.43] helo=rn-mailsvcp-ppex-lapp34.apple.com) by mimas.w3.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <guoye_zhang@apple.com>) id 1o4Azl-00303p-A7 for ietf-http-wg@w3.org; Thu, 23 Jun 2022 00:46:53 +0000
Received: from pps.filterd (rn-mailsvcp-ppex-lapp34.rno.apple.com [127.0.0.1]) by rn-mailsvcp-ppex-lapp34.rno.apple.com (8.16.1.2/8.16.1.2) with SMTP id 25N0f0C7028876; Wed, 22 Jun 2022 17:46:37 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=6/38m8HExptCJzSJVlwdDUkH53Vlm3Jvq4D0wUF3G4E=; b=d4v8/SshNv8v5NZ6zuCvRJGvXYSGZ2UdVyiBB8zClhoKuB1Cp/hFkf/dZH7/GvWNZSt8 5YixdTqJW+lyDN+ORzEbR9T/CAz3ZZKX/Z+XmJYtXDGw+UplfTyDHUQD36+ebsfspOt/ P6YH40oKSemyPGo2Ld5Cr9aDua1kV2JILK+XS+ah2TidlOO64WB+9glo36xrkhCLcEuB 5XRhBV9RRAE+hxhtf9XSDP8Pe2CsTzYA3MZ6KwR/lE79k4UoDS0wARVi731QfnMq6TWL oJPGhuocyonL/y/btQ0txyXiVU5o87rDZiUYQqZorRwK9/DwW4ODWD20dyROoevcTA+x zw==
Received: from rn-mailsvcp-mta-lapp02.rno.apple.com (rn-mailsvcp-mta-lapp02.rno.apple.com [10.225.203.150]) by rn-mailsvcp-ppex-lapp34.rno.apple.com with ESMTP id 3gsaj1sxm5-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Wed, 22 Jun 2022 17:46:37 -0700
Received: from rn-mailsvcp-mmp-lapp03.rno.apple.com (rn-mailsvcp-mmp-lapp03.rno.apple.com [17.179.253.16]) by rn-mailsvcp-mta-lapp02.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPS id <0RDW00I0ANHI7C80@rn-mailsvcp-mta-lapp02.rno.apple.com>; Wed, 22 Jun 2022 17:46:30 -0700 (PDT)
Received: from process_milters-daemon.rn-mailsvcp-mmp-lapp03.rno.apple.com by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) id <0RDW00E00N6T6000@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Wed, 22 Jun 2022 17:46:30 -0700 (PDT)
X-Va-A:
X-Va-T-CD: 6ce7dffd6ac8afd0af3f738963e57eda
X-Va-E-CD: 7fa589823f194c8498e6df6440bddbf3
X-Va-R-CD: 87a202228b76ae5a02807a21fbbc1b7c
X-Va-CD: 0
X-Va-ID: 86903c46-9d91-44b9-bc18-4625bd24b2dd
X-V-A:
X-V-T-CD: 6ce7dffd6ac8afd0af3f738963e57eda
X-V-E-CD: 7fa589823f194c8498e6df6440bddbf3
X-V-R-CD: 87a202228b76ae5a02807a21fbbc1b7c
X-V-CD: 0
X-V-ID: c7333386-a86d-4b1a-8d4f-02149e47094d
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517,18.0.883 definitions=2022-06-22_09:2022-06-22,2022-06-22 signatures=0
Received: from smtpclient.apple (unknown [17.11.164.4]) by rn-mailsvcp-mmp-lapp03.rno.apple.com (Oracle Communications Messaging Server 8.1.0.18.20220407 64bit (built Apr 7 2022)) with ESMTPSA id <0RDW00SKLNHI0C00@rn-mailsvcp-mmp-lapp03.rno.apple.com>; Wed, 22 Jun 2022 17:46:30 -0700 (PDT)
From: Guoye Zhang <guoye_zhang@apple.com>
Message-id: <A00C7493-2637-4C2A-B880-EC03AD82EDF3@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_32FA45A8-3682-42A4-B865-FEC2D8311CF8"
MIME-version: 1.0 (Mac OS X Mail 16.0 \(3724.0.1.1.31\))
Date: Wed, 22 Jun 2022 17:46:20 -0700
In-reply-to: <181808e7a44.aed3d7b643553.5952608326455145559@zoho.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, ietf-http-wg <ietf-http-wg@w3.org>
To: Eric J Bowman <mellowmutt@zoho.com>
References: <BED5A5BC-3F7F-47E2-815E-DC0483328DFD@apple.com> <Yq67WGkb0LtJIAP9@xps13> <D149DCFE-A5C9-418D-80B4-3B5F138AA497@apple.com> <Yq/mYB6FMLWn/7Oj@xps13> <1A0308B7-266A-4E12-BC6C-6D321BAFC3D3@apple.com> <1817f68e1bc.b0da438140687.4010670760181959722@zoho.com> <E0263B0F-3C3A-46F4-AA1D-7580C5ADE326@apple.com> <d32488ea-05b3-e97f-3118-3845306faa6a@gmx.de> <181808e7a44.aed3d7b643553.5952608326455145559@zoho.com>
X-Mailer: Apple Mail (2.3724.0.1.1.31)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.517,18.0.883 definitions=2022-06-22_09:2022-06-22,2022-06-22 signatures=0
Received-SPF: pass client-ip=17.179.253.43; envelope-from=guoye_zhang@apple.com; helo=rn-mailsvcp-ppex-lapp34.apple.com
X-W3C-Hub-DKIM-Status: validation passed: (address=guoye_zhang@apple.com domain=apple.com), signature is good
X-W3C-Hub-Spam-Status: No, score=-4.7
X-W3C-Hub-Spam-Report: BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.574, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, W3C_AA=-1, W3C_WL=-1
X-W3C-Scan-Sig: mimas.w3.org 1o4Azl-00303p-A7 96203d6a9bdbfc547b903f723af8b3d5
X-Original-To: ietf-http-wg@w3.org
Subject: Re: Draft v1 Update for Resumable Uploads
Archived-At: <https://www.w3.org/mid/A00C7493-2637-4C2A-B880-EC03AD82EDF3@apple.com>
Resent-From: ietf-http-wg@w3.org
X-Mailing-List: <ietf-http-wg@w3.org> archive/latest/40203
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/Mail/>
List-Post: <mailto:ietf-http-wg@w3.org>
List-Unsubscribe: <mailto:ietf-http-wg-request@w3.org?subject=unsubscribe>
> On Jun 20, 2022, at 03:00, Eric J Bowman <mellowmutt@zoho.com> wrote: > > > > > Maybe > > https://www.ietf.org/archive/id/draft-ietf-httpbis-binary-message-05.html could > > be used; that would avoid the multipart parsing challenge. > > > > Ha, like I needed another hobby project from this thread! I get what you're saying, thx Julian. Section 3.8, Padding and Truncation -- message/bhttp as a general-purpose PATCH format for BLOBs. > > -Eric > > I’ll admit that I was confused by this exchange. I know binary message from oblivious HTTP, but I think Julian was suggesting replacing multipart part boundaries with binary message, not using it as the PATCH format. Let me explain what I understood from this discussion, please correct me if I’m wrong: (1) My initial blocker for adopting Content-Range was that we needed a open range: :method: PATCH upload-offset: 42 [Dynamically generated body with unknown length] This is unrepresentable by Content-Range. (2) Eric suggested multipart body with Content-Range, essentially: :method: PATCH content-type: multipart/sometime; boundary=“boundary" --boundary Content-Range: 42-50/* [8 bytes] --boundary Content-Range: 51-60/* [10 bytes] --boundary … (3) I expressed concerns about multipart overhead. (4) Julian suggested using binary message to serialize messages more efficiently, replacing plaintext headers and textual boundaries with the binary serialization format. (5) Eric suggested using binary message itself as the PATCH format to represent arbitrary binary diff. My reply to (4): If we need to invent a new format anyway, I’d avoid multipart since we don’t really need it for appending a continuous blob. My reply to (5): I don’t think this is what binary message is for, but I’m really curious what you were able to achieve with this idea. Having a general-purpose binary patching format would be great. Guoye
- Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Austin William Wright
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Martin J. Dürst
- Re: Draft v1 Update for Resumable Uploads gs-lists-ietf-http-wg
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Lucas Pardue
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Glenn Strauss
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Lucas Pardue
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Glenn Strauss
- Re: Draft v1 Update for Resumable Uploads Glenn Strauss
- Re: Draft v1 Update for Resumable Uploads Glenn Strauss
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Mark Nottingham
- Re: Draft v1 Update for Resumable Uploads Glenn Strauss
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Julian Reschke
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Julian Reschke
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Julian Reschke
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Eric J Bowman
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Greg Wilkins
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Greg Wilkins
- Re: Draft v1 Update for Resumable Uploads Poul-Henning Kamp
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang
- Re: Draft v1 Update for Resumable Uploads Greg Wilkins
- Re: Draft v1 Update for Resumable Uploads Guoye Zhang