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

Carsten Bormann <cabo@tzi.org> Tue, 03 May 2022 07:26 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 4821BC15ED66 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 May 2022 00:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651562815; bh=vIJrDq1DrCnY0HxN4Pqn4+xlNPCTRAqd2IPuTqQurQE=; h=From:In-Reply-To:Date:Cc:References:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=MQHQeijway6p/OMEw+DY31Wgeg2+M6wKSjtKK6GwAxgA/uiVbGHUKkp0vhoG46IXz 1UISKq+ZubGlvodH7kExg2EYaGzwbfKNpcNmYt4+oS+ci7GA4hFv/SGnJbiLbsO6Hb YMEYA2+PNZavcOiXfeCMpuqfG84ZehhAQ2Ih6ygk=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Tue May 3 00:26:54 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 60095C157B49; Tue, 3 May 2022 00:26:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651562814; bh=vIJrDq1DrCnY0HxN4Pqn4+xlNPCTRAqd2IPuTqQurQE=; h=From:In-Reply-To:Date:Cc:References:To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=gNMkibBHbM0w3jLKrprUhbxOLqPUFwp0etUj5f5LLWaykFXbefeow5iGHys83Thvc G8U7E4Ynxac+vidslsaPufUa8cbvt1AIbP8mZmcXqSwi/ZSUkHTwTfY2uTXyAEHu8/ HUa8b9m7zlOQljZ90KF5V4LFdJbcooWXB3oDhUKo=
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 6EC1DC157B49 for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 00:26:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level:
X-Spam-Status: No, score=-1.895 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=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 k7IWASa12Kar for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 00:26:49 -0700 (PDT)
Received: from gabriel-smtp.zfn.uni-bremen.de (gabriel-smtp.zfn.uni-bremen.de [134.102.50.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 8BAB6C157B35 for <rfc-interest@rfc-editor.org>; Tue, 3 May 2022 00:26:48 -0700 (PDT)
Received: from [192.168.217.118] (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 4Kss394vqmzDCdy; Tue, 3 May 2022 09:26:45 +0200 (CEST)
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\))
From: Carsten Bormann <cabo@tzi.org>
In-Reply-To: <4c07cb3f-1bba-602d-7d8e-5e798e02d863@huitema.net>
Date: Tue, 03 May 2022 09:26:45 +0200
Cc: Julian Reschke <julian.reschke@gmx.de>, rfc-interest@rfc-editor.org
X-Mao-Original-Outgoing-Id: 673255604.920676-de9caaa63f0ffceb37166e71d2995788
Message-Id: <35A90B8B-3ECD-495D-AAC2-51670E4FAF29@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> <C68D2369-4592-4F3A-8C37-FBB1A88D2E9D@tzi.org> <4c07cb3f-1bba-602d-7d8e-5e798e02d863@huitema.net>
To: Christian Huitema <huitema@huitema.net>
X-Mailer: Apple Mail (2.3608.120.23.2.7)
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/-P61ufFssLmkv0LdMJvwU3AT8k8>
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>

On 2022-05-03, at 08:06, Christian Huitema <huitema@huitema.net> wrote:
> 
> Uh, No. The spiders and indexers are still going to pick "rfc9148" from "https://www.rfc-editor.org/rfc/authors/rfc9148-to-be.html”.

But that’s OK, because there will be a permanent redirect as soon as the real thing is available.

> If you want safety, you need to obfuscate that some more. Maybe you can get away with: 

Safety?
Given that drafts can be sitting in that state for a year or so, it is totally appropriate for people to find them under the new name.

Grüße, Carsten 
(who has three drafts in AUTH48-DONE right now, one approaching 10 weeks there)

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