IETF Logo Mail Archive

Re: [rfc-i] Wrong Internet search results for new RFCs

Carsten Bormann <cabo@tzi.org> Tue, 03 May 2022 05:28 UTC

Return-Path: <rfc-interest-bounces@rfc-editor.org>
X-Original-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Delivered-To: ietfarch-rfc-interest-archive@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 643D3C15E6CC for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Mon, 2 May 2022 22:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651555732; bh=VxMsz8GG/5nmwwsfQ3lEfvo4fMKq8ZbqL1o6d26FuYs=; h=From:In-Reply-To:Date:Cc:References:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=k74dq4MCBG5hldajYjS9kexggwFGPLbtBg0cQPYLErAN9nH/JqDTRMmBtuqYRmay8 yQIyqrl1hr2Ky0iJvbQO3aGZdheepGJ4k2nz6qVDPGQdkKr1+jhqkyFG0xeCJ55KEs gvCSUr+3b33TNTFPL+w+eJCd9i0zD+ZeBNP2OF5g=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Mon May 2 22:28:52 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1E3CCC157B37; Mon, 2 May 2022 22:28:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651555732; bh=VxMsz8GG/5nmwwsfQ3lEfvo4fMKq8ZbqL1o6d26FuYs=; h=From:In-Reply-To:Date:Cc:References:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=k74dq4MCBG5hldajYjS9kexggwFGPLbtBg0cQPYLErAN9nH/JqDTRMmBtuqYRmay8 yQIyqrl1hr2Ky0iJvbQO3aGZdheepGJ4k2nz6qVDPGQdkKr1+jhqkyFG0xeCJ55KEs gvCSUr+3b33TNTFPL+w+eJCd9i0zD+ZeBNP2OF5g=
X-Original-To: rfc-interest@ietfa.amsl.com
Delivered-To: rfc-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F168DC14F738 for <rfc-interest@ietfa.amsl.com>; Mon, 2 May 2022 22:28:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 ODRtRV6VmIHs for <rfc-interest@ietfa.amsl.com>; Mon, 2 May 2022 22:28:47 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [IPv6:2001:638:708:32::15]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 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 214BAC14F734 for <rfc-interest@rfc-editor.org>; Mon, 2 May 2022 22:28:45 -0700 (PDT)
Received: from smtpclient.apple (p5089ad4f.dip0.t-ipconnect.de [80.137.173.79]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by gabriel-smtp.zfn.uni-bremen.de (Postfix) with ESMTPSA id 4KspQy04tKzDCbN; Tue, 3 May 2022 07:28:41 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.80.82.1.1\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <5528eb31-2cbd-460b-720c-a69ebe4e7482@gmx.de>
Date: Tue, 03 May 2022 07:28:41 +0200
Cc: rfc-interest@rfc-editor.org
Message-Id: <C68D2369-4592-4F3A-8C37-FBB1A88D2E9D@tzi.org>
References: <YnCECATOh9mI1HY4@faui48e.informatik.uni-erlangen.de> <20220503021720.69EDC3F4BACA@ary.qy> <YnCkoCzNTr3aquH/@faui48e.informatik.uni-erlangen.de> <5528eb31-2cbd-460b-720c-a69ebe4e7482@gmx.de>
To: Julian Reschke <julian.reschke@gmx.de>
X-Mailer: Apple Mail (2.3696.80.82.1.1)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/mZowrB8KTJm25Hj4IUhJwyUriB4>
Subject: Re: [rfc-i] Wrong Internet search results for new RFCs
X-BeenThere: rfc-interest@rfc-editor.org
X-Mailman-Version: 2.1.34
Precedence: list
List-Id: "A list for discussion of the RFC series and RFC Editor functions." <rfc-interest.rfc-editor.org>
List-Unsubscribe: <https://mailman.rfc-editor.org/mailman/options/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/rfc-interest/>
List-Post: <mailto:rfc-interest@rfc-editor.org>
List-Help: <mailto:rfc-interest-request@rfc-editor.org?subject=help>
List-Subscribe: <https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest>, <mailto:rfc-interest-request@rfc-editor.org?subject=subscribe>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

>>>> 
>>>> https://www.rfc-editor.org/rfc/authors/rfc9148.html
>>>> 
> 
> FWIW, this shows that it is a bad idea to name a publicly readable
> resource RFCNNNN until the moment it get's published (so I believe the
> RFC Editor should modify their naming convention).

+1

➔

>> https://www.rfc-editor.org/rfc/authors/rfc9148-to-be.html

And, after publication, this needs to have a permanent redirect to

>> https://www.rfc-editor.org/rfc/rfc9148.html

(Similar for the other presentation forms.)

Grüße, Carsten

_______________________________________________
rfc-interest mailing list
rfc-interest@rfc-editor.org
https://mailman.rfc-editor.org/mailman/listinfo/rfc-interest

v2.23.0 | Report a Bug | By Email