Re: [dispatch] Proposal for Per Resource Events Protocol

Michael Toomim <toomim@gmail.com> Tue, 08 August 2023 21:18 UTC

Return-Path: <toomim@gmail.com>
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 68968C15C509 for <dispatch@ietfa.amsl.com>; Tue, 8 Aug 2023 14:18:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.195
X-Spam-Level:
X-Spam-Status: No, score=-7.195 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, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.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 JzwUPHTvqyNl for <dispatch@ietfa.amsl.com>; Tue, 8 Aug 2023 14:18:12 -0700 (PDT)
Received: from mail-pf1-x430.google.com (mail-pf1-x430.google.com [IPv6:2607:f8b0:4864:20::430]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B2BC151996 for <dispatch@ietf.org>; Tue, 8 Aug 2023 14:18:12 -0700 (PDT)
Received: by mail-pf1-x430.google.com with SMTP id d2e1a72fcca58-686be28e1a8so4385836b3a.0 for <dispatch@ietf.org>; Tue, 08 Aug 2023 14:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1691529491; x=1692134291; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=phdbS2wpGFQJhEywaenRCecxpQscx99CPZ31sSTrgfA=; b=bloCL1HhvFFfEq9IEPJ06elSlzIZ4nQOGel6onm4zvbEQT5Us+Up25nTpfAyHUCLV/ PjIW0Y8toJ3clc1/FAyCR/G0MHxWoL9cS1m9opqjteBD0DKgeGiegexL/ZzFGckLhJ4G viRmeEgLQNI3rLqrIWFCgKTp6IOzq+1CRqwBNS/MIcFlBp3oQ5zw8UBExB04ydSsw6DZ jTIXcTmd3bHFVlZnHhBSBU/Q9/Au99+ZpLWNsKWNBs8q6rDxlRyKZ37K3dfKOSk1pLIV NzUaBwOhB93aOLzkim+QMaYvsJKae/X9R5IswHDfWNf+FjKzH034bAPQIjyNAE0A78CE XT9A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1691529491; x=1692134291; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=phdbS2wpGFQJhEywaenRCecxpQscx99CPZ31sSTrgfA=; b=Etr4vta8QneExNBb/TDRKCYa08S9lE6G28hMIgRFt1cXzTYFazrVOizM7Ct+3vfpJe 0hPeGXji1oVLLXYOfKDWcH4P5ZGJZwjiLsXmnFevtZ2xhsnsRlTlAjDPnJ1zkQCVphDI hTVvUiVdA5sNLd8VV1aZsZ8OaE85ItFdSekehOtShKqJ5xRgvooeyOPJiXeCFnSJKb75 K6B+buVyHmie/96uMM25MgLE9uJHRTRmiIeLES8PzKG9pEt9GWNPQ2iITpaShH9sp/0n 4dhaydwCKxvcQwGsX3mJryDFKsxbudPDPnAgd1qfFx/QOES7eIlqcISlfG+nsISB6zUp 8O8Q==
X-Gm-Message-State: AOJu0YzaKvCM4xfKP2VFy3s6S/5fsW73fmliDrT5GmWkfOcAy2+GJlLS 5YxxBtxJuvbBtoSZd/2AFZpSGbyH7rE=
X-Google-Smtp-Source: AGHT+IFdnMiMTBhmWmps7FDoB3Tc0smBJx8BBrkIjzBVoUYTvrmRpkKnyjaVezPfFoQZZNXaK7Bs0Q==
X-Received: by 2002:a05:6a20:9184:b0:133:712e:f700 with SMTP id v4-20020a056a20918400b00133712ef700mr848287pzd.51.1691529491142; Tue, 08 Aug 2023 14:18:11 -0700 (PDT)
Received: from [192.168.4.22] (184-23-20-243.fiber.dynamic.sonic.net. [184.23.20.243]) by smtp.gmail.com with ESMTPSA id k3-20020a636f03000000b0052c9d1533b6sm7187626pgc.56.2023.08.08.14.18.09 for <dispatch@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 08 Aug 2023 14:18:09 -0700 (PDT)
Content-Type: multipart/alternative; boundary="------------4pLfvknFkqXu2juIV50PVbkt"
Message-ID: <15c147ec-6628-6fc8-f31b-69d7269cb222@gmail.com>
Date: Tue, 08 Aug 2023 14:18:08 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.14.0
Content-Language: en-US
To: dispatch@ietf.org
References: <878ralz3o1.fsf@hobgoblin.ariadne.com>
From: Michael Toomim <toomim@gmail.com>
In-Reply-To: <878ralz3o1.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/tfdjit_EVn4MPy1RQO4ZSSVC-Yc>
Subject: Re: [dispatch] Proposal for Per Resource Events Protocol
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: Tue, 08 Aug 2023 21:18:13 -0000

On 8/8/23 1:21 PM, Dale R. Worley wrote:
> Looking at that web page, ... it doesn't provide a clear summary that the
> naive reader can read to grasp the big picture (and then fill in the
> details reading the rest of the text).  Put something like your "How it
> works" at the top.

I would really like to see some example use-cases for it, along with 
scenarios showing how this meets those use-cases.

It's not clear to me how Per-Resource Events differs from SSE, for example.

And Rahul, I'm actually planning to dispatch a very similar proposal in 
Braid 
<https://datatracker.ietf.org/doc/html/draft-toomim-httpbis-braid-http> 
this November. Depending on the overlap in use-cases you are trying to 
support, we might end up being able to combine our efforts. Braid 
supports per-resource events that describe *mutations to state.* I would 
be curious to learn if you have use-cases for events beyond mutations to 
state.