Merge Types
draft-toomim-httpbis-merge-types-00

Document Type Expired Internet-Draft (individual)
Authors Michael Toomim  , Mitar Milutinovic  , Bryn Bellomy 
Last updated 2020-05-21 (latest revision 2019-11-18)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized (tools) htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-toomim-httpbis-merge-types-00.txt

Abstract

Merge Types specify how to merge multiple simultaneous edits to a resource. This happens when two computers edit the same state over a network with latency. A Merge Type specifies how to merge conflicting changes. If the computers implement and agree upon the same Merge Type, then they can guarantee to reach a consistent state, after arbitrary edits, eventually. You can define new Merge Types. This document defines Merge Types, the structure of the Merge Type system, and IANA registration procedures for Merge Types.

Authors

Michael Toomim (toomim@gmail.com)
Mitar Milutinovic (mitar.ietf@tnode.com)
Bryn Bellomy (bryn@signals.io)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)