IETF Logo Mail Archive

Re: [dispatch] Proposal for Per Resource Events Protocol

worley@ariadne.com Fri, 11 August 2023 00:42 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 7A71CC17EB4D for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2023 17:42:15 -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 fDl43POk31OT for <dispatch@ietfa.amsl.com>; Thu, 10 Aug 2023 17:42:11 -0700 (PDT)
Received: from resqmta-a1p-077721.sys.comcast.net (resqmta-a1p-077721.sys.comcast.net [96.103.146.58]) (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 9D486C17EB4C for <dispatch@ietf.org>; Thu, 10 Aug 2023 17:42:11 -0700 (PDT)
Received: from resomta-a1p-077246.sys.comcast.net ([96.103.145.237]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resqmta-a1p-077721.sys.comcast.net with ESMTP id UFYxqX6pLwNuzUGCHqPUii; Fri, 11 Aug 2023 00:40:09 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcastmailservice.net; s=20211018a; t=1691714409; bh=23C8mdJT2aZhNm5N0Yw9yoU536zNGak/a+POAM/hpqI=; h=Received:Received:Received:Received:From:To:Subject:Date: Message-ID:Xfinity-Spam-Result; b=iL09+l9qzu63juqCa6OqsWcap2m09kj9YvsqiLK4Yu5XOyW3quloMS2/0oAX0WG1p 8rSh0a/a6cS3aNzIMuf/lL5uaH/ZtyXAH5WX89q1DVa7SJmPlf4o8R4lQHjU3nHLUV 73/hA7Jh8qkX1f2mCrJGbNkc8SUTBw0ZbbFDZxYCgZgKQZhCKV5VwqJnMqN+4/X8Mx olQUNjPVVnYmhDqJT42jNvDWu0yHspTvYM0nXaQzW3Jc8kEaehXUyqAemSnW3kBfvF MV1iFEaAFSIO0BmuTE7le3a1x9Y7KVJR9YaUJ17B+89CnNUJT8oG9GLTMiyiGX1fBJ 0azxNJn2IXMzA==
Received: from hobgoblin.ariadne.com ([IPv6:2601:192:4a00:430::68ab]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-a1p-077246.sys.comcast.net with ESMTPA id UGC7qpmrKoaa6UGCGqML1n; Fri, 11 Aug 2023 00:40:09 +0000
X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedviedrleejgdefhecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecunecujfgurhephffvvefujghssedttddttddttddtnecuhfhrohhmpeifohhrlhgvhiesrghrihgrughnvgdrtghomhculdffrghlvgcutfdrucghohhrlhgvhidmnecuggftrfgrthhtvghrnhepjeetueegteekheevgfdtkeeijeehfeetffefvdehleejkeevueeuheejheeljeffnecukfhppedviedtudemudelvdemgegrtddtmeegfedtmeemieekrggsnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohephhhosghgohgslhhinhdrrghrihgrughnvgdrtghomhdpihhnvghtpedviedtudemudelvdemgegrtddtmeegfedtmeemieekrggspdhmrghilhhfrhhomhepfihorhhlvgihsegrlhhumhdrmhhithdrvgguuhdpnhgspghrtghpthhtohepvddprhgtphhtthhopeguihhsphgrthgthhesihgvthhfrdhorhhgpdhrtghpthhtoheptgigrhgvshesphhrohhtohhnmhgrihhlrdgtohhm
X-Xfinity-VMeta: sc=0.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 37B0dxqA2418645 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Thu, 10 Aug 2023 20:39:59 -0400
Received: (from worley@localhost) by hobgoblin.ariadne.com (8.16.1/8.16.1/Submit) id 37B0dxKX2418642; Thu, 10 Aug 2023 20:39:59 -0400
X-Authentication-Warning: hobgoblin.ariadne.com: worley set sender to worley@alum.mit.edu using -f
From: worley@ariadne.com
To: "dispatch@ietf.org" <dispatch@ietf.org>
In-Reply-To: <x3e2-5CGGB-joUNy5Ujq053jsdnYpxL4xKIndQDQU0nwsRh5gyFoIEyTeKKogm3HwmyGzJKzDHdzUF5wA7QsFGDnQFG99Ay7tCkYp6ZztXc=@protonmail.com> (cxres@protonmail.com)
Sender: worley@ariadne.com
Date: Thu, 10 Aug 2023 20:39:59 -0400
Message-ID: <87wmy2jtsw.fsf@hobgoblin.ariadne.com>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/gD8cNAuyfw7Ebwxq8n3nZwBqDm4>
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: Fri, 11 Aug 2023 00:42:15 -0000

Rahul Gupta <cxres@protonmail.com> writes:
> I am not very aware of SIP. But I have never come across an instance
> of anyone implementing it for notifications of resource updates. 

Now that you make me think of it, using SIP's SUBSCRIBE/NOTIFY mechanism
(RFC 3265) for notifications might be a good solution.  It has been used
extensively for over 20 years.  It has well-developed methods of dealing
with NATs, aggregating notifications, etc.  For short and infrequent
notifications, it uses UDP alone, so it doesn't maintain connections.
And there are a lot of existing implementations.

Of course, it has the problem that it's not built on top of HTTP.

Dale

v2.31.3 | Report a Bug | By Email | System Status