[Feeds] Re: Should we standardize on a single URL path to RSS feeds?

Mark <mark@openrss.org> Thu, 26 December 2024 13:13 UTC

Return-Path: <mark@openrss.org>
X-Original-To: feeds@ietfa.amsl.com
Delivered-To: feeds@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C1680C14F6FD for <feeds@ietfa.amsl.com>; Thu, 26 Dec 2024 05:13:46 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, 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=openrss.org
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 rbLNXwFoF8sp for <feeds@ietfa.amsl.com>; Thu, 26 Dec 2024 05:13:42 -0800 (PST)
Received: from mail-4018.proton.ch (mail-4018.proton.ch [185.70.40.18]) (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 ietfa.amsl.com (Postfix) with ESMTPS id 0D00DC14F68D for <feeds@ietf.org>; Thu, 26 Dec 2024 05:13:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=openrss.org; s=protonmail2; t=1735218819; x=1735478019; bh=kBviDtmoV1Nls7vfoOmXGkHV03XlgYGu3l9Fa1Qm54E=; h=Date:To:From:Cc:Subject:Message-ID:In-Reply-To:References: Feedback-ID:From:To:Cc:Date:Subject:Reply-To:Feedback-ID: Message-ID:BIMI-Selector:List-Unsubscribe:List-Unsubscribe-Post; b=FkjDvldcn6WfBvWVzmeeqhW3ptPLc4TQBFvpViqB557btZhF1CbcOXl8Fqx6dX53L vi8Tgu1fDS43OH8gbQjaiDQkqP3W2kieiNatf4lSdJSNPj+D1nY8igjcztTVfrfRZt c9ku4DaHOEx8FsWaUF4qnOhVvRZfUhtKrFeOTRfOVTP42DCS9m6o84UdH6gJJwttY+ SioStkP99o7R2lH95pZHbfa47z8raLdbwGd9fp+sgjHIfiLu9PN2ZnuC9mMtugrOqH k3aNdqmX+uc0XCmHsurwpCst+C5qCMjxA/MGAC7RgRIO4Cs3Yrg1DzCyjj64Z8R6LV Z5rPDeQVtc6EQ==
Date: Thu, 26 Dec 2024 13:13:35 +0000
To: "Martin J. Dürst" <duerst@it.aoyama.ac.jp>
From: Mark <mark@openrss.org>
Message-ID: <aSABTXG6vpXoVXPpPIRp_9UIMV4ImJ8yivG9pFdLRyDr9tgcyZsc55i-WP5on0YhDocOWqr0pZlYpIkq9OBoC5aU9n7hR4J-EkcyDNAdgwk=@openrss.org>
In-Reply-To: <f9764a93-9014-4aa4-8420-a739088098a0@it.aoyama.ac.jp>
References: <CAChr6SyzxzXeFkhLUh0UKHmh_8Fky9ZdhJt8st74SJcqtQZaUA@mail.gmail.com> <bd248ea3-d480-495b-9b74-bfb5194553a0@it.aoyama.ac.jp> <2ix0pHQfu_AImelI95ViwjKRYYLDBc5uRAUG5SybgGdNX9DO_LsSLJOvpgdEGGw5ox3t0swhsEm5YRQpPM0znpJ2zHeigbvGzuQDsr0UXho=@openrss.org> <f9764a93-9014-4aa4-8420-a739088098a0@it.aoyama.ac.jp>
Feedback-ID: 62933185:user:proton
X-Pm-Message-ID: 715bed910d4a4d64a2a1140983ead08baa9dd971
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Message-ID-Hash: TFOBFL3W26J74FS3QWHFVF22GVM32NIE
X-Message-ID-Hash: TFOBFL3W26J74FS3QWHFVF22GVM32NIE
X-MailFrom: mark@openrss.org
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
CC: feeds@ietf.org
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Feeds] Re: Should we standardize on a single URL path to RSS feeds?
List-Id: Web Feeds <feeds.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/feeds/FYmuJQEs3r1CIOB9XeJUyrvcj6A>
List-Archive: <https://mailarchive.ietf.org/arch/browse/feeds>
List-Help: <mailto:feeds-request@ietf.org?subject=help>
List-Owner: <mailto:feeds-owner@ietf.org>
List-Post: <mailto:feeds@ietf.org>
List-Subscribe: <mailto:feeds-join@ietf.org>
List-Unsubscribe: <mailto:feeds-leave@ietf.org>

Thanks for the clarification, Martin.

Hmm, "robots.txt" seems fine, despite the bad little bots that ignore it ;) 

Maybe I'm missing it. But I'd love to understand why IETF has concluded that fixed URLs are a bad idea, if possible. If anyone can link me to the rationale, that would be great!

Mark Kennedy
Engineer
openrss.org


On Thursday, December 26th, 2024 at 3:04 AM, Martin J. Dürst <duerst@it.aoyama.ac.jp> wrote:

> Hello Mark,
> 
> There are people on this list with more background knowledge in this
> area, but robots.txt was probably the earliest example of a fixed link.
> Then came favicon.ico. These are historic artefacts that are difficult
> to remove.
> 
> After favicon.ico, people in the IETF, the W3C, and elsewhere started to
> realize that this was a bad idea and created explanatory texts such as
> RFC 3205 (later updated to RFC 9205), and mechanisms such as .wellknown
> (RFC 5785, later updated to RFC 8615).
> 
> .wellkown essentially makes the mistake of defining a fixed link
> (prefix) for one last time, and then stuffs all future fixed links into
> the /.wellknown/ directory, governed by a registry at IANA to avoid
> collisions.
> 
> Regards, Martin.
> 
> On 2024-12-26 16:26, Mark wrote:
> 
> > Hey Martin,
> > 
> > Thanks for the link. I've taken a look at that and it says
> > 
> > "specifications for applications that use HTTP won't contain fixed application URLs or paths; while it is common practice [...], doing so in an IETF specification is inappropriate".
> > 
> > This suggests that my original question around a standard and fixed URL path for RSS feeds would be inappropriate for the IETF. However, it contradicts something like section 2.3 of RFC 9309 (https://www.rfc-editor.org/rfc/rfc9309.html#name-access-method) where a fixed URL path is clearly being used for a "robots.txt" file. Please correct me if I'm misunderstanding, but why is having a fixed URL path for something like "robots.txt" acceptable for the IETF, but not for a fixed URL path for RSS feeds?
> > 
> > Thanks for any clarification.
> > 
> > Mark Kennedy
> > Engineer
> > openrss.org
> > 
> > On Thursday, December 26th, 2024 at 1:36 AM, Martin J. Dürst duerst@it.aoyama.ac.jp wrote:
> > 
> > > Sorry for being so late, but when cleaning up my inbox, I found this and
> > > thought that for some people, a look at RFC 9205 (BCP 56), in particular
> > > Section 4.4
> > > (https://www.rfc-editor.org/rfc/rfc9205#name-specifying-urls) might
> > > provide some additional background.
> > > 
> > > Regards, Martin.
> > > 
> > > On 2024-12-18 06:41, Rob Sayre wrote:
> > > 
> > > > Oh, it's so much worse than you think. :)
> > > > 
> > > > Check this one out:
> > > > 
> > > > https://help.apple.com/itc/podcasts_connect/#/itcb54353390
> > > > 
> > > > Look at "itunes:new-feed-url" there. Apologies in advance, it's like
> > > > nails on a chalkboard.
> > > > 
> > > > thanks,
> > > > Rob
> > > 
> > > --
> > > Feeds mailing list -- feeds@ietf.org
> > > To unsubscribe send an email to feeds-leave@ietf.org