[dispatch] Re: INDF - Subscription Account RSS/Atom feeds: request for other people to take care of this problem

Jonas Korene Novak <info@dcrubro.com> Wed, 20 August 2025 09:00 UTC

Return-Path: <info@dcrubro.com>
X-Original-To: dispatch@mail2.ietf.org
Delivered-To: dispatch@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B7F175664929 for <dispatch@mail2.ietf.org>; Wed, 20 Aug 2025 02:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, RCVD_IN_VALIDITY_SAFE_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=dcrubro.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id SWeYMGTrSwXM for <dispatch@mail2.ietf.org>; Wed, 20 Aug 2025 02:00:46 -0700 (PDT)
Received: from mail.dcrubro.com (mail.dcrubro.com [86.61.75.254]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id 42D095664922 for <dispatch@ietf.org>; Wed, 20 Aug 2025 02:00:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dcrubro.com; s=mail; t=1755680444; bh=ng38HV3ykoj+dVHm79r4yzI52agv0nQGvp7lHAIA+2A=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=l8GHwT9aOzcMxv909zzoS69XxXzC/S0qXrg2QW5mgp+XV21UccTNDpBuiGfZDw4Mq yVJqsjRfsAMwFx0hAhioKV52VThJZDxExECt5fjldFx4ip60BhVNQuB33/tfTdm+LE lVUO+hpZCEavb6CH0pt0j/CAyJo2jr1kOHtYvorQ3vJ53vmJGbkBRalcf1ap8DWM+8 Z9vnePGM+x9vP/4hNtyYCcmN9LFRnlYweB5wdkpCz02yxo1ZHo0wh70WqkWWJWTLuX ig5IiGnw+U+1QLVPHOjwPvdNuMrnIb5FnW7bQ9piOlGed/ZlY7oa2Tl30tQacsle6w gcYhO5kleZvpw==
Received: from mail.dcrubro.com (localhost [127.0.0.1]) by mail.dcrubro.com (Postfix) with ESMTPSA id 2DC79B4F; Wed, 20 Aug 2025 09:00:44 +0000 (UTC)
MIME-Version: 1.0
Date: Wed, 20 Aug 2025 11:00:44 +0200
From: Jonas Korene Novak <info@dcrubro.com>
To: Rob Sayre <sayrer@gmail.com>
In-Reply-To: <CAChr6Swzak_K=RtekP4=NRmiF57o6uGmbxh3SUL5joF_N9HmTg@mail.gmail.com>
References: <CAChr6Swzak_K=RtekP4=NRmiF57o6uGmbxh3SUL5joF_N9HmTg@mail.gmail.com>
Message-ID: <d39ef1d9b05b11365435bf4ffb435f9f@dcrubro.com>
X-Sender: info@dcrubro.com
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Content-Transfer-Encoding: 7bit
Message-ID-Hash: TDOAZVJBPEAFF532EZU5BVSL6FTRI5I2
X-Message-ID-Hash: TDOAZVJBPEAFF532EZU5BVSL6FTRI5I2
X-MailFrom: info@dcrubro.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-dispatch.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: DISPATCH WG <dispatch@ietf.org>, Orie <orie@or13.io>
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [dispatch] Re: INDF - Subscription Account RSS/Atom feeds: request for other people to take care of this problem
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/QShR4FhAOc4QWnxjBRiorvDmYcs>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Owner: <mailto:dispatch-owner@ietf.org>
List-Post: <mailto:dispatch@ietf.org>
List-Subscribe: <mailto:dispatch-join@ietf.org>
List-Unsubscribe: <mailto:dispatch-leave@ietf.org>

Hi Rob,

There's a W3C standardized protocol named "WebSub"
(which can be found here: https://www.w3.org/TR/websub/)

Although not an IETF standard, it seems to fit what you're describing 
close enough.

If you're just looking for something that works, I think this covers it,
but if your goal is for it to also be standardized in the IETF and other 
members
agree, I think the next step would be for someone to write up a draft.

Regards,
Jonas

> My request is for the IETF to formulate a standard for feed and
> podcast clients to get /one/ notification of an update for all
> subscription URLs. This work has been done, I think. There are "Well
> Known URIs", "URI templates", and "Webhooks". Think of products like
> Patreon/Memberful/Substack etc.