Re: [rfc-i] Meta decorations in generated HTML

John R Levine <johnl@taugh.com> Fri, 27 May 2022 16:59 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 22940C16551C for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Fri, 27 May 2022 09:59:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653670753; bh=lLLCn8TwjjOEzLnguTLq2AOrsXOfkrBDr14foJ1VD+0=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=ysXYZFG8/NJa15DWaEQ3iTXVQX8fftxT2dCD2uJAqSuJbbrWSXF5A6aypgXXUKnHu +ne3N3WSIMuY9+5wuV8IAQU1X8e8YrbqBh1coLBdiBPheBVfMVnl7b9B5DiY9t4GIv 6dDShEDZOASxArUsUrTEiXsts77zO11Y2OU3R+SM=
X-Mailbox-Line: From rfc-interest-bounces@rfc-editor.org Fri May 27 09:59:10 2022
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id D844DC180A90; Fri, 27 May 2022 09:59:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1653670749; bh=lLLCn8TwjjOEzLnguTLq2AOrsXOfkrBDr14foJ1VD+0=; h=Date:From:To:In-Reply-To:References:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=lyjgPULR49RvidmdJNZttbzGrAec9msfEWtH4aKUUKTAvMKRmcSd5+02MtytPiSFS k4dnnPX7y4u1AQMr1CticFNXC7XfY1xdBXqbLLRPPVaDZzsdGch6sZ/ORzL0oMZXrz iZqzS6XhWGyacFJ/C/vy8UmNejhEovLXSBI/diRk=
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 76AFDC180A90 for <rfc-interest@ietfa.amsl.com>; Fri, 27 May 2022 09:59:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level:
X-Spam-Status: No, score=-2.096 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_ZEN_BLOCKED_OPENDNS=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
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=iecc.com header.b=SZuu78Ya; dkim=pass (2048-bit key) header.d=taugh.com header.b=1EO75lTe
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 8oydydnNtbPT for <rfc-interest@ietfa.amsl.com>; Fri, 27 May 2022 09:59:03 -0700 (PDT)
Received: from gal.iecc.com (gal.iecc.com [IPv6:2001:470:1f07:1126:0:43:6f73:7461]) (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 6835AC16551C for <rfc-interest@rfc-editor.org>; Fri, 27 May 2022 09:59:03 -0700 (PDT)
Received: (qmail 99708 invoked from network); 27 May 2022 16:58:59 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=18579.62910353.k2205; bh=K5HMwdnbTC1K8cnRWW4OhelKBNrUZE3e42gCCIWBc8g=; b=SZuu78Ya72DgiJBWn2fXfkgiRyv42j3oeI70z8pg2blQset0v1heDWY5p3QAVux731zmySUfpwcEO5ylDNmPisHD4C1BvUFtD0qhWJVzt51gdipytflo+VkVlS2iJP/efKBhYJO1Izs4blDskLrs6P8OixN72/uKXYN5VCps6GmCFLr75ui7WfF4vljz8ZBF0DDUSEVOqz+Mvb9aHG07nkFmAoP7S0mz7i2peRp8COw2mDBI9jrxMC+/TNMPah6uWmnRXGKVyXH1RVRFEKfP+/0Ht4UngCD0vQelIPYspBANfMnNdOd8kNcOiCffiBQRzWf4oWBvdxEp8OZybLthMw==
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:subject:in-reply-to:references:mime-version:content-type; s=18579.62910353.k2205; bh=K5HMwdnbTC1K8cnRWW4OhelKBNrUZE3e42gCCIWBc8g=; b=1EO75lTeTZZM6jzmSMiEi9X/8Tskircf5sVcym8oUQvdYXa/5rQBTpq4HmqzJ4F0xITnabspgojApTNqjFqcy+9ZWdNFSmmcNpKdiPRRD2aAyAoSQyZIzo5oHXqAFxxiEqTr6d1MvaqnQWVziKkJCuCjaKKX2y3uUyYlQzg14tsnus2kj1tEEnc3yLDqFYOH2B8ImqnAshQCJia5Esk5jsKmuSmXg+vjg/h41F/fdBuZfQZRaRaz4JQjg6Sdpw3E75TkAEedkmloI220TSxSXrrDgjxP8qlRpP7edT3Csr0VxXIBo41QMoiSzP9q7h91jRr3NhcmLVWknfF0Rf040A==
Received: from ary.qy ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.3 ECDHE-RSA AES-256-GCM AEAD) via TCP6; 27 May 2022 16:58:59 -0000
Received: by ary.qy (Postfix, from userid 501) id 139EC41C4B78; Fri, 27 May 2022 12:58:57 -0400 (EDT)
Received: from localhost (localhost [127.0.0.1]) by ary.qy (Postfix) with ESMTP id 589D541C4B5A; Fri, 27 May 2022 12:58:57 -0400 (EDT)
Date: Fri, 27 May 2022 12:58:57 -0400
Message-ID: <88f7f0a7-be8b-cefe-1ee7-2b8a158cc788@taugh.com>
From: John R Levine <johnl@taugh.com>
To: Michael Richardson <mcr+ietf@sandelman.ca>, rfc-interest@rfc-editor.org
X-X-Sender: johnl@ary.qy
In-Reply-To: <29605.1653666740@localhost>
References: <20220525203826.8606A41A4E93@ary.qy> <f0f92d4c-8cc4-c3bb-0f0d-96c3ad422303@gmx.de> <C826D239-7CCB-404E-9591-B33C34ED82C9@tzi.org> <5afe0f29-ab5a-b79e-cad4-7c18cf8fc5d3@gmx.de> <0ab66d2e-aa7d-eb17-83dc-2774e9d021a7@taugh.com> <27659.1653660447@localhost> <d603174c-db26-4fcb-0a60-a1f8b714c951@taugh.com> <29605.1653666740@localhost>
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/elR_iqM2DHid6yMG-Lf5IZuXwyc>
Subject: Re: [rfc-i] Meta decorations in generated HTML
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>

>    > The way to keep AUTH48 pages out of search engines is to tell them not to
>    > index them.

> Yes, that particular mole has been whacked, but I'm just thinking about other
> ways/places that RFCs might show up in non-canonical places.    I might post
> a copy on a web site devoted to that technology for instance, and it would be
> good if it re-inforced rfc-editor.org as the canonical source, rather than
> diluted it.

I suppose we could put "don't index me" tags into the HTML and edit them 
out on the copies on the rfc-editor web site but that seems too fragile.

The normal way you get high in the search rankings is to have high quality 
links pointing at them.  If all of the places in the datatracker and the 
other IETF web sites pointed at the copies RFCs on the rfc-editor web site 
rather than at other places that would help but that also doesn't seem 
likely.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail. https://jl.ly

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