IETF Logo Mail Archive

Re: [dispatch] A State Synchronization Working Group

worley@ariadne.com Fri, 27 October 2023 00:56 UTC

Return-Path: <worley@alum.mit.edu>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 39728C1524B3 for <dispatch@ietfa.amsl.com>; Thu, 26 Oct 2023 17:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.992
X-Spam-Level:
X-Spam-Status: No, score=-0.992 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_SOFTFAIL=0.665, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=comcastmailservice.net
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 LHHe4Rxteum8 for <dispatch@ietfa.amsl.com>; Thu, 26 Oct 2023 17:56:32 -0700 (PDT)
Received: from resqmta-a1p-077723.sys.comcast.net (resqmta-a1p-077723.sys.comcast.net [96.103.146.57]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34828C187714 for <dispatch@ietf.org>; Thu, 26 Oct 2023 17:56:31 -0700 (PDT)
Received: from resomta-a1p-076781.sys.comcast.net ([96.103.145.226]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-a1p-077723.sys.comcast.net with ESMTP id wB05qpi5V8LvVwB7OqqAgp; Fri, 27 Oct 2023 00:54:30 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1698368070; bh=uK3cSgNjcHzjWdxIQksVdRtZl+t9l15jyXwkYN0kuLI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=fdSP5YvZjUG2t6t+vjMbNPtdRqhTgO7CC3puKopCVfvBVCj3tlX+vrx1CQJxyMJIR jngptAaE8F/WU+zivlEZuaojqbYEgLmMT8HmYzCekufUSoIJlqxFe0fq61i8eBUQCk CBWPKXiYfDi4/IE4Rj83WHY5QZkUqYPf3AmqvnOkkEI6A0FFc5EIlMZ8AEoMOudcVZ dIDLhmJVvI1JotwhrXJkyFIPNBQJm4HV75ltm/ROHm1W0iw69crgHGZBN7MvGPLQpD pga7vNHBx9nfkWWj9RHL12vPvg2qk2XjoejnHWXXK/KFI9yHmbmbD1aRnn8kuU2V1k Tl7gYiTHI8j5A==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::9df6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-a1p-076781.sys.comcast.net with ESMTPA id wB7MqSTFArrF0wB7NqLN9H; Fri, 27 Oct 2023 00:54:29 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedvkedrleefgdegudcutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefhvfevufgjshestddttddttddttdenucfhrhhomhepfihorhhlvgihsegrrhhirggunhgvrdgtohhmucdlffgrlhgvucftrdcuhghorhhlvgihmdenucggtffrrghtthgvrhhnpeejteeugeetkeehvefgtdekieejheeftefffedvheeljeekveeuueehjeehleejffenucfkphepvdeitddumeduledvmeegrgdttdemgeeftdemmeelughfieenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhephhgvlhhopehhohgsghhosghlihhnrdgrrhhirggunhgvrdgtohhmpdhinhgvthepvdeitddumeduledvmeegrgdttdemgeeftdemmeelughfiedpmhgrihhlfhhrohhmpeifohhrlhgvhiesrghluhhmrdhmihhtrdgvughupdhnsggprhgtphhtthhopedvpdhrtghpthhtohepthhoohhmihhmsehgmhgrihhlrdgtohhmpdhrtghpthhtohepughishhprghttghhsehivghtfhdrohhrgh
X-Xfinity-VMeta: sc=-100.00;st=legit
Received: from hobgoblin.ariadne.com (localhost [127.0.0.1]) by hobgoblin.ariadne.com (8.16.1/8.16.1) with ESMTPS id 39R0sR2Y1996999 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 26 Oct 2023 20:54:27 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 39R0sRA31996996; Thu, 26 Oct 2023 20:54:27 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: Michael Toomim <toomim@gmail.com>
Cc: dispatch@ietf.org
In-Reply-To: <a301786e-c59d-f395-f752-bd2c94521e67@gmail.com> (toomim@gmail.com)
Sender: worley@ariadne.com
Date: Thu, 26 Oct 2023 20:54:27 -0400
Message-ID: <87a5s4hol8.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/_gCQOdgluEaCiXWiZhQuRht_V4M>
Subject: Re: [dispatch] A State Synchronization Working Group
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 27 Oct 2023 00:56:36 -0000

Michael Toomim <toomim@gmail.com> writes:
> I would like to dispatch the idea of forming a general State 
> Synchronization Working Group, to coordinate duplicate efforts in 
> defining various state synchronization protocols across existing IETF 
> working groups.  ...

> ... We design these as separate protocols because the *general*
> version of the State Synchronization Problem has seemed too
> challenging to tackle.  ...

OK ...  The concept seems quite reasonable but the devil is in the
details, and it seems to me that a lot of devils could be lurking in the
details.

I can conceive that a State Synchronization Working Group could define
an abstract sync protocol, which each networking protocol would then
implement in a straightforward way suitable for its structure.

But this would have some prerequisites.  The basic one is to believe
that this is work for the IETF rather than the IRTF:  Write a convincing
exposition that, relative to a sufficiently general model of "state",
people have produced a sufficiently efficient (and comprehensible)
general synchronization protocol.

In particular, the long list of research results you give *decreases* my
confidence in the current state of the art -- problems that generate a
lot of papers are generally ones that don't yet have a "known solution".

What I want to see is a (short) list of documents, which you think if I
read them, I will be convinced that creating a standardized sync
protocol is an attainable engineering task.  E.g. one response would be
"Please read the Braid draft, draft-toomim-httpbis-braid-http, it covers
everything you could possibly want to know!"

Dale

v2.23.0 | Report a Bug | By Email