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

Michael Richardson <mcr+ietf@sandelman.ca> Tue, 03 May 2022 16:41 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 D5D75C15E402 for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 May 2022 09:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651596119; bh=2yb5SHMdKB9zGv1Nmg4zhNM2YSwVjvQBUXkvFlssxwg=; h=From:To:cc:In-Reply-To:References:Date:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=yjrQqrz6ot5s91e0YnLoDHRAs9q67KCKDwsd2Df204rI0GiZ07AmYInBLykqUIcRS PmNfjXUOD33xHubGu9oRiL9adczubi/3LLsKRzYaFtSywV2igQnqjoBdZBS6QrEkQo I048xvWJBvr9/Yt1OkJwy7vRBge7g5RVbfsdqyrc=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Tue May 3 09:41:59 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BEF7C159A3C; Tue, 3 May 2022 09:41:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651596119; bh=2yb5SHMdKB9zGv1Nmg4zhNM2YSwVjvQBUXkvFlssxwg=; h=From:To:cc:In-Reply-To:References:Date:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=yjrQqrz6ot5s91e0YnLoDHRAs9q67KCKDwsd2Df204rI0GiZ07AmYInBLykqUIcRS PmNfjXUOD33xHubGu9oRiL9adczubi/3LLsKRzYaFtSywV2igQnqjoBdZBS6QrEkQo I048xvWJBvr9/Yt1OkJwy7vRBge7g5RVbfsdqyrc=
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 48908C159524 for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 09:41:58 -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, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-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 aEEIIs20nMX4 for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 09:41:56 -0700 (PDT)
Received: from tuna.sandelman.ca (tuna.sandelman.ca [IPv6:2607:f0b0:f:3:216:3eff:fe7c:d1f3]) (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 CE622C159A3C for <rfc-interest@rfc-editor.org>; Tue, 3 May 2022 09:41:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by tuna.sandelman.ca (Postfix) with ESMTP id 6157738B63; Tue, 3 May 2022 12:54:57 -0400 (EDT)
Received: from tuna.sandelman.ca ([127.0.0.1]) by localhost (localhost [127.0.0.1]) (amavisd-new, port 10024) with LMTP id iKDld1WfUtvo; Tue, 3 May 2022 12:54:56 -0400 (EDT)
Received: from sandelman.ca (unknown [172.30.2.21]) by tuna.sandelman.ca (Postfix) with ESMTP id 8C52D38B5E; Tue, 3 May 2022 12:54:56 -0400 (EDT)
Received: from localhost (localhost [IPv6:::1]) by sandelman.ca (Postfix) with ESMTP id D693E2A7; Tue, 3 May 2022 12:41:51 -0400 (EDT)
From: Michael Richardson <mcr+ietf@sandelman.ca>
To: Robert Sparks <rjsparks@nostrum.com>
cc: RFC Interest <rfc-interest@rfc-editor.org>
In-Reply-To: <2f655efd-603b-ebef-bb01-3859571dbd79@nostrum.com>
References: <20220503021720.69EDC3F4BACA@ary.qy> <2f655efd-603b-ebef-bb01-3859571dbd79@nostrum.com>
X-Mailer: MH-E 8.6+git; nmh 1.7+dev; GNU Emacs 27.1
X-Face: $\n1pF)h^`}$H>Hk{L"x@)JS7<%Az}5RyS@k9X%29-lHB$Ti.V>2bi.~ehC0; <'$9xN5Ub# z!G,p`nR&p7Fz@^UXIn156S8.~^@MJ*mMsD7=QFeq%AL4m<nPbLgmtKK-5dC@#:k
MIME-Version: 1.0
Date: Tue, 03 May 2022 12:41:51 -0400
Message-ID: <20129.1651596111@localhost>
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/d1FL4z6r0bNSCFA_r_UfqXJlZVk>
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: multipart/mixed; boundary="===============7696719651349470533=="
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

It seems to me that the AUTH48 copies are forever going to leak if some
search engines are ignoring the robots.txt

Wouldn't an HTTP AUTH help?  Even if the username/password is ietf/ietf?

--
Michael Richardson <mcr+IETF@sandelman.ca>   . o O ( IPv6 IøT consulting )
           Sandelman Software Works Inc, Ottawa and Worldwide




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