IETF Logo Mail Archive

Re: [weirds] Search Engines Indexing RDAP Server Content

Francisco Arias <francisco.arias@icann.org> Fri, 29 January 2016 16:54 UTC

Return-Path: <francisco.arias@icann.org>
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 978FE1A87D4 for <weirds@ietfa.amsl.com>; Fri, 29 Jan 2016 08:54:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.202
X-Spam-Level:
X-Spam-Status: No, score=-4.202 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001] autolearn=ham
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 V2wMd9T60uzA for <weirds@ietfa.amsl.com>; Fri, 29 Jan 2016 08:54:51 -0800 (PST)
Received: from out.west.pexch112.icann.org (pfe112-ca-1.pexch112.icann.org [64.78.40.7]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD9311A87C7 for <weirds@ietf.org>; Fri, 29 Jan 2016 08:54:51 -0800 (PST)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) with Microsoft SMTP Server (TLS) id 15.0.1130.7; Fri, 29 Jan 2016 08:54:49 -0800
Received: from PMBX112-W1-CA-1.pexch112.icann.org ([64.78.40.21]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([64.78.40.21]) with mapi id 15.00.1130.005; Fri, 29 Jan 2016 08:54:49 -0800
From: Francisco Arias <francisco.arias@icann.org>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, "weirds@ietf.org" <weirds@ietf.org>, "regops@nlnetlabs.nl" <regops@nlnetlabs.nl>, "gtld-tech@icann.org" <gtld-tech@icann.org>
Thread-Topic: [weirds] Search Engines Indexing RDAP Server Content
Thread-Index: AQHRWrXDcIqNwxGiSxmdhJxaDQVVfw==
Date: Fri, 29 Jan 2016 16:54:49 +0000
Message-ID: <D047F538-672C-4258-9370-838C82FF16FD@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.160109
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.35.2]
Content-Type: text/plain; charset="utf-8"
Content-ID: <F6B0A9409CC5AB49B751BDB1FA8A0241@pexch112.icann.org>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/iS_ln0NC0r_uc0-TkEsvuEnHrvI>
Subject: Re: [weirds] 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 16:54:53 -0000

Hi Scott,

In all the cross-posting, it seems you may have left out the list where people have currently in scope doing something about this https://community.icann.org/display/gTLDRDS/Next-Generation+gTLD+Registration+Directory+Services+to+Replace+Whois

Regards,

-- 
Francisco







On 1/29/16, 5:34 AM, "weirds on behalf of Hollenbeck, Scott" <weirds-bounces@ietf.org on behalf of shollenbeck@verisign.com> wrote:

>(cross-posting to multiple lists - sorry if that's inconvenient)
>
>So I saw a tweet from Gavin Brown (@GavinBrown) that describes how one particular search engine has indexed the RDAP server of a gTLD registry operator:
>
>https://twitter.com/GavinBrown/status/692718904058191872
>
>This is all the more reason to work on a client authentication specification that includes support for varying responses based on client identity and authorization. I've been working on such a specification and welcome feedback on the approach:
>
>https://datatracker.ietf.org/doc/draft-hollenbeck-weirds-rdap-openid/
>
>It also begs the question of the need for a BCP describing operational practices for server operators. There are ways for web servers to influence or restrict crawler behavior, but what's appropriate in this context?
>
>Scott
>
>_______________________________________________
>weirds mailing list
>weirds@ietf.org
>https://www.ietf.org/mailman/listinfo/weirds

v2.23.0 | Report a Bug | By Email