Resent-Date: Tue, 16 Jul 2024 01:26:45 +0000
Resent-Message-Id: <E1sTWxp-00Fd04-2k@mab.w3.org>
Received-SPF: pass (pan.w3.org: domain of gmail.com designates 2607:f8b0:4864:20::52b as permitted sender) client-ip=2607:f8b0:4864:20::52b; envelope-from=toomim@gmail.com; helo=mail-pg1-x52b.google.com;
Content-Type: multipart/alternative;
 boundary="------------Sc6x8fLQlCDlRopyPwY6gWPc"
Message-ID: <ff54cd4f-c30e-4447-8744-3297e53b74be@gmail.com>
Date: Mon, 15 Jul 2024 18:26:36 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
References: <172046173132.445281.15041630415895010148@dt-datatracker-5f88556585-j5r2h>
Content-Language: en-US
To: HTTP Working Group <ietf-http-wg@w3.org>,
 Braid <braid-http@googlegroups.com>
From: Michael Toomim <toomim@gmail.com>
In-Reply-To: <172046173132.445281.15041630415895010148@dt-datatracker-5f88556585-j5r2h>
Subject: Fwd: New Version Notification for  draft-toomim-httpbis-versions-00.txt
Archived-At: <https://www.w3.org/mid/ff54cd4f-c30e-4447-8744-3297e53b74be@gmail.com>
Resent-From: ietf-http-wg@w3.org
Resent-Sender: ietf-http-wg-request@w3.org
Precedence: list

This is a multi-part message in MIME format.
--------------Sc6x8fLQlCDlRopyPwY6gWPc
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit

Hi everyone in HTTP!

Last fall we solicited feedback on the Braid State Synchronization 
proposal [draft 
<https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-braid-http-04>, 
slides 
<https://datatracker.ietf.org/meeting/118/materials/slides-118-httpbis-braid-http-add-synchronization-to-http-00>], 
which I'd summarize as:

    "We're enthusiastic about the general work, but the proposal is too
    high-level. Break the spec up into multiple independent specs, and
    work bottom-up. Focus on concrete 'bits-on-the-wire'."

So I'm breaking the spec up, and have drafted up the first chunk for 
you. I would very much like your review on:

    *Versioning of HTTP Resources*
    draft-toomim-httpbis-versions
    https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions-00

Versioning is necessary for state synchronization—and occurs in a range 
of HTTP systems:

  * Caching
  * Archiving
  * Version Control
  * Collaborative Editing

Today, HTTP has resource versions in the Last-Modified and ETag headers, 
and sometimes embeds versions in URLs, like with WebDAV. Each of these 
options serves some needs, but also has specific limitations. An 
improved general approach is proposed, which provides new features, that 
could enable cool new applications, such as incrementally-updated RSS 
feeds, and could simplify existing specifications, such as resumeable 
uploads, and history compression in OT/CRDT algorithms.

I would love to know if people find this work interesting. I think we 
could improve performance, interoperability, and be one step closer to 
having Google Docs power within HTTP URLs.

Michael

-------- Forwarded Message --------
Subject: 	New Version Notification for draft-toomim-httpbis-versions-00.txt
Date: 	Mon, 08 Jul 2024 11:02:11 -0700
From: 	internet-drafts@ietf.org
To: 	Michael Toomim <toomim@gmail.com>



A new version of Internet-Draft draft-toomim-httpbis-versions-00.txt has 
been
successfully submitted by Michael Toomim and posted to the
IETF repository.

Name: draft-toomim-httpbis-versions
Revision: 00
Title: HTTP Resource Versioning
Date: 2024-07-08
Group: Individual Submission
Pages: 19
URL: https://www.ietf.org/archive/id/draft-toomim-httpbis-versions-00.txt
Status: https://datatracker.ietf.org/doc/draft-toomim-httpbis-versions/
HTMLized: 
https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions


Abstract:

HTTP resources change over time. Each change to a resource creates a
new "version" of its state. HTTP systems often need a way to
identify, read, write, navigate, and/or merge these versions, in
order to implement cache consistency, create history archives, settle
race conditions, request incremental updates to resources, interpret
incremental updates to versions, or implement distributed
collaborative editing algorithms.

This document analyzes existing methods of versioning in HTTP,
highlights limitations, and sketches a more general versioning
approach that can enable new use-cases for HTTP.



The IETF Secretariat


--------------Sc6x8fLQlCDlRopyPwY6gWPc
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

<!DOCTYPE html>
<html>
  <head>

    <meta http-equiv="content-type" content="text/html; charset=UTF-8">
  </head>
  <body>
    <p>Hi everyone in HTTP!<br>
    </p>
    <p>Last fall we solicited feedback on the Braid State
      Synchronization proposal [<a
href="https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-braid-http-04">draft</a>,
      <a
href="https://datatracker.ietf.org/meeting/118/materials/slides-118-httpbis-braid-http-add-synchronization-to-http-00">slides</a>],
      which I'd summarize as:</p>
    <blockquote>
      <p>"We're enthusiastic about the general work, but the proposal is
        too high-level. Break the spec up into multiple independent
        specs, and work bottom-up. Focus on concrete
        'bits-on-the-wire'."<br>
      </p>
    </blockquote>
    <div class="moz-forward-container">So I'm breaking the spec up, and
      have drafted up the first chunk for you. I would very much like
      your review on:<br>
    </div>
    <blockquote>
      <div class="moz-forward-container"><b>Versioning of HTTP Resources</b><br>
        draft-toomim-httpbis-versions<br>
        <a class="moz-txt-link-freetext"
href="https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions-00">https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions-00</a><br>
      </div>
    </blockquote>
    <div class="moz-forward-container">Versioning is necessary for state
      synchronization—and occurs in a range of HTTP systems:</div>
    <div class="moz-forward-container">
      <ul>
        <li>Caching</li>
        <li>Archiving<br>
        </li>
        <li>Version Control<br>
        </li>
        <li>Collaborative Editing<br>
        </li>
      </ul>
    </div>
    <div class="moz-forward-container">Today, HTTP has resource versions
      in the Last-Modified and ETag headers, and sometimes embeds
      versions in URLs, like with WebDAV. Each of these options serves
      some needs, but also has specific limitations. An improved general
      approach is proposed, which provides new features, that could
      enable cool new applications, such as incrementally-updated RSS
      feeds, and could simplify existing specifications, such as
      resumeable uploads, and history compression in OT/CRDT algorithms.</div>
    <div class="moz-forward-container"><br>
    </div>
    <div class="moz-forward-container">I would love to know if people
      find this work interesting. I think we could improve performance,
      interoperability, and be one step closer to having Google Docs
      power within HTTP URLs.<br>
    </div>
    <div class="moz-forward-container"><br>
    </div>
    Michael
    <div class="moz-forward-container"><br>
      -------- Forwarded Message --------
      <table class="moz-email-headers-table" cellspacing="0"
        cellpadding="0" border="0">
        <tbody>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Subject:
            </th>
            <td>New Version Notification for
              draft-toomim-httpbis-versions-00.txt</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date: </th>
            <td>Mon, 08 Jul 2024 11:02:11 -0700</td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">From: </th>
            <td><a class="moz-txt-link-abbreviated" href="mailto:internet-drafts@ietf.org">internet-drafts@ietf.org</a></td>
          </tr>
          <tr>
            <th valign="BASELINE" nowrap="nowrap" align="RIGHT">To: </th>
            <td>Michael Toomim <a class="moz-txt-link-rfc2396E" href="mailto:toomim@gmail.com">&lt;toomim@gmail.com&gt;</a></td>
          </tr>
        </tbody>
      </table>
      <br>
      <br>
      A new version of Internet-Draft
      draft-toomim-httpbis-versions-00.txt has been<br>
      successfully submitted by Michael Toomim and posted to the<br>
      IETF repository.<br>
      <br>
      Name: draft-toomim-httpbis-versions<br>
      Revision: 00<br>
      Title: HTTP Resource Versioning<br>
      Date: 2024-07-08<br>
      Group: Individual Submission<br>
      Pages: 19<br>
      URL:
      <a class="moz-txt-link-freetext" href="https://www.ietf.org/archive/id/draft-toomim-httpbis-versions-00.txt">https://www.ietf.org/archive/id/draft-toomim-httpbis-versions-00.txt</a><br>
      Status:
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/draft-toomim-httpbis-versions/">https://datatracker.ietf.org/doc/draft-toomim-httpbis-versions/</a><br>
      HTMLized:
      <a class="moz-txt-link-freetext" href="https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions">https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-versions</a><br>
      <br>
      <br>
      Abstract:<br>
      <br>
      HTTP resources change over time. Each change to a resource creates
      a<br>
      new "version" of its state. HTTP systems often need a way to<br>
      identify, read, write, navigate, and/or merge these versions, in<br>
      order to implement cache consistency, create history archives,
      settle<br>
      race conditions, request incremental updates to resources,
      interpret<br>
      incremental updates to versions, or implement distributed<br>
      collaborative editing algorithms.<br>
      <br>
      This document analyzes existing methods of versioning in HTTP,<br>
      highlights limitations, and sketches a more general versioning<br>
      approach that can enable new use-cases for HTTP.<br>
      <br>
      <br>
      <br>
      The IETF Secretariat<br>
      <br>
      <br>
    </div>
  </body>
</html>

--------------Sc6x8fLQlCDlRopyPwY6gWPc--