Re: [weirds] [Regops] Search Engines Indexing RDAP Server Content

"John Levine" <johnl@taugh.com> Fri, 29 January 2016 17:24 UTC

Return-Path: <johnl@taugh.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CFA9A1A88BD for <weirds@ietfa.amsl.com>; Fri, 29 Jan 2016 09:24:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.664
X-Spam-Level: *
X-Spam-Status: No, score=1.664 tagged_above=-999 required=5 tests=[BAYES_50=0.8, HELO_MISMATCH_COM=0.553, HOST_MISMATCH_NET=0.311, KHOP_DYNAMIC=0.001, SPF_PASS=-0.001] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s0E_-SFJjY7C for <weirds@ietfa.amsl.com>; Fri, 29 Jan 2016 09:24:02 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34A81A88B4 for <weirds@ietf.org>; Fri, 29 Jan 2016 09:24:01 -0800 (PST)
Received: (qmail 83775 invoked from network); 29 Jan 2016 17:24:00 -0000
Received: from unknown (64.57.183.18) by mail1.iecc.com with QMQP; 29 Jan 2016 17:24:00 -0000
Date: 29 Jan 2016 17:23:38 -0000
Message-ID: <20160129172338.51466.qmail@ary.lan>
From: "John Levine" <johnl@taugh.com>
To: weirds@ietf.org
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A14C08E@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
Organization:
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/1LtjVfeG9c2LGPbY7WEFQqLCihI>
Subject: Re: [weirds] [Regops] Search Engines Indexing RDAP Server Content
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 29 Jan 2016 17:24:04 -0000

>We have a difference of opinion, because I tend to think that it's a *good* idea to restrict access
>to *some* data based on a client's identify and level of authorization. I do not want *my* PII
>appearing in search engine search results because it's accessible via RDAP.

Sorry, but I really don't understand what you want here.  There have
been vertical WHOIS search engines forever that let you search WHOIS
data in various ways.  Most of them charge money, but as often as not
some access is free.  That horse left the barn a decade ago.

The stuff that search engines can see is exactly the same as what
casual users see.  If you're saying that you want to make some stuff
unavailable to anyone who doesn't have a password, OK, but now aren't
you running into the whole ICANN mess of what's in WHOIS and what
isn't?

R's,
John

PS: On the third hand, if you want to make it slightly harder for
casual searches to find RDAP info, publishing a robots.txt that says
"Disallow: /" should take about 30 seconds. and will keep the entire
site out of all of the legit search engines.