IETF Logo Mail Archive

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

"Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org> Tue, 03 May 2022 16:49 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 4D125C15E6DE for <ietfarch-rfc-interest-archive@ietfa.amsl.com>; Tue, 3 May 2022 09:49:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651596569; bh=ln7L4To6g3lcR/wnXhyAOCChXxW1l43yXZl2KNoLm/E=; h=To:CC:Date:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe: From; b=D8pK9Xc6dXRre0u5sGQina+XTyyqHmM5hoWWK+5cb8P7PdDNXT4vay249uJrfX3Mf MKhaIYde2AfmOY8f0ZB4M2EVkH9Dx1xzrQCY55NPtevl0VntfeCJ7AhH0vGAqySrHD FANoLhV3ErbOTXTpk1YekPmOsB4c8S2n1OZO68JA=
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 1ECD3C159A20; Tue, 3 May 2022 09:49:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1651596569; bh=ln7L4To6g3lcR/wnXhyAOCChXxW1l43yXZl2KNoLm/E=; h=From:To:CC:Date:References:In-Reply-To:Subject:List-Id: List-Unsubscribe:List-Archive:List-Post:List-Help:List-Subscribe; b=ott3zltZnXsMwiSw0fJ4m68xsGpPsZUgU+OboVqOcmQyUFof7j+hxCjOzRoQgMB4d FG4ahlyOTF8MpCqZ6dSmvXXTD3P8PbnFNF//JtKbnWJYBylgTuECyB9FmMw2QtnF0n wlYOenHCJKfzWcF0riixvi9G5Q83/qYHqBg3qQV4=
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 83FC5C159A20 for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 09:49:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.671
X-Spam-Level:
X-Spam-Status: No, score=-2.671 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.575, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 uKPyPErfueIx for <rfc-interest@ietfa.amsl.com>; Tue, 3 May 2022 09:49:24 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5EB77C1594B5 for <rfc-interest@rfc-editor.org>; Tue, 3 May 2022 09:48:32 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.17.1.5/8.17.1.5) with ESMTP id 243EnNib016407; Tue, 3 May 2022 17:48:27 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=HWIavhGCs6iOW1Bm4gWgIQWVOvJENvcDmb/oeJagNFE=; b=G0qHa7bqVo/8juonmMWFC4i60Pf6Bza1wCYruRIVAZXWjM68D8iVmNqdF9BTp2ZXWf+V Z8yNCyQFWSZ+apXRYdLE8Nan9vZzvd/lLSBSmd7Lzm1Wvrk+T3WS408NdeR55n56ChfR 1nlfrTcslo3N8XVKoShRKaIDk/Cau/Z4TYVSyTVU+mwDfYQqwlyDcVaiGHOdvYQg0hYW K5diRUnkObOFXW4OfGLoi65e3hfPxqgwgZ+m/xDyYYv+1wnPjkR9BKR0y8Bt5dcccjN0 7fgwYMFLthTTteqsJWO+eXtwMZZLFBOzX0axmrt84VjBlfAVuY4jVKsSAnv00jhxlQtO CQ==
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18] (may be forged)) by mx0a-00190b01.pphosted.com (PPS) with ESMTPS id 3frvcc9s45-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 03 May 2022 17:48:27 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.1.2/8.16.1.2) with SMTP id 243GY3mi009489; Tue, 3 May 2022 12:48:25 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.30]) by prod-mail-ppoint1.akamai.com with ESMTP id 3fs0eydjm1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 03 May 2022 12:48:25 -0400
Received: from USMA1EX-DAG1MB4.msg.corp.akamai.com (172.27.123.104) by usma1ex-dag4mb1.msg.corp.akamai.com (172.27.91.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.2.986.22; Tue, 3 May 2022 12:48:25 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1497.32; Tue, 3 May 2022 12:48:25 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1497.033; Tue, 3 May 2022 12:48:24 -0400
To: Michael Richardson <mcr+ietf@sandelman.ca>, Robert Sparks <rjsparks@nostrum.com>
CC: RFC Interest <rfc-interest@rfc-editor.org>
Thread-Topic: [rfc-i] Wrong Internet search results for new RFCs
Thread-Index: AQHYXoxpltwVG5RjaEOdr5KD5l4ywa0MrcgAgADK9wCAACaWgP//vsaA
Date: Tue, 03 May 2022 16:48:23 +0000
Message-ID: <5F87F7FD-B3E3-46B3-B03A-EA7BEF58D179@akamai.com>
References: <20220503021720.69EDC3F4BACA@ary.qy> <2f655efd-603b-ebef-bb01-3859571dbd79@nostrum.com> <20129.1651596111@localhost>
In-Reply-To: <20129.1651596111@localhost>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/16.60.22041000
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.27.164.43]
Content-ID: <1DD8C540AC85D548B7221C3668D2E8DC@akamai.com>
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.486, 18.0.858 definitions=2022-05-03_07:2022-05-02, 2022-05-03 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 suspectscore=0 mlxlogscore=618 phishscore=0 malwarescore=0 spamscore=0 mlxscore=0 bulkscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2205030110
X-Proofpoint-ORIG-GUID: iwTV9rLJGG4KOFFpVosF-2g0CDOMzEqX
X-Proofpoint-GUID: iwTV9rLJGG4KOFFpVosF-2g0CDOMzEqX
X-Proofpoint-Virus-Version: vendor=baseguard engine=ICAP:2.0.205,Aquarius:18.0.858,Hydra:6.0.486,FMLib:17.11.64.514 definitions=2022-05-03_07,2022-05-02_03,2022-02-23_01
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 malwarescore=0 mlxscore=0 suspectscore=0 lowpriorityscore=0 mlxlogscore=589 priorityscore=1501 bulkscore=0 spamscore=0 clxscore=1015 adultscore=0 phishscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-2202240000 definitions=main-2205030110
Archived-At: <https://mailarchive.ietf.org/arch/msg/rfc-interest/AKRVVJoJYJtHa7T5Y8e4uW-YoDQ>
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="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: rfc-interest-bounces@rfc-editor.org
Sender: rfc-interest <rfc-interest-bounces@rfc-editor.org>
X-Original-From: "Salz, Rich" <rsalz@akamai.com>
From: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>

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

We don't want any barriers to our stuff being globally accessible, even if it means a search engine, or us, sometimes get it wrong.

_______________________________________________
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