Re: [eppext] [gtld-tech] RDAP server of the registry

Gustavo Lozano <> Wed, 07 October 2015 16:38 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9D4541ACE4E for <>; Wed, 7 Oct 2015 09:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -3.13
X-Spam-Status: No, score=-3.13 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, MIME_BASE64_BLANKS=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_NEUTRAL=0.779, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id en6UUP3WLsVa for <>; Wed, 7 Oct 2015 09:38:12 -0700 (PDT)
Received: from ( []) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 9BEA81A1A97 for <>; Wed, 7 Oct 2015 09:38:12 -0700 (PDT)
Received: from ( by ( with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 7 Oct 2015 09:38:10 -0700
Received: from ([]) by PMBX112-W1-CA-1.PEXCH112.ICANN.ORG ([]) with mapi id 15.00.1044.021; Wed, 7 Oct 2015 09:38:10 -0700
From: Gustavo Lozano <>
To: "Hollenbeck, Scott" <>, =?iso-8859-1?Q?Patrik_Wallstr=F6m?= <>
Thread-Topic: [eppext] [gtld-tech] RDAP server of the registry
Thread-Index: AQHRAR6K/sste7+5UkCCDDnuwhzYJQ==
Date: Wed, 7 Oct 2015 16:38:05 +0000
Message-ID: <>
References: <> <> <> <> <> <> <> <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
user-agent: Microsoft-MacOutlook/
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: []
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg=sha1; boundary="B_3527066279_1021800"
MIME-Version: 1.0
Archived-At: <>
Cc: Kaveh Ranjbar <>, "" <>, "" <>
Subject: Re: [eppext] [gtld-tech] RDAP server of the registry
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Wed, 07 Oct 2015 16:38:14 -0000

On 10/7/15, 10:41, "Hollenbeck, Scott" <> wrote:

>> -----Original Message-----
>> From: Gustavo Lozano []
>> Sent: Wednesday, October 07, 2015 10:00 AM
>> To: Patrik Wallström; Hollenbeck, Scott
>> Cc: Kaveh Ranjbar;;
>> Subject: Re: [eppext] [gtld-tech] RDAP server of the registry
>> gTLD Registries want to have full requirements and an implementation
>> plan
>> for all RDSS (i.e. whois, rdap) related activities, therefore the
>> schedule
>> to have the gTLD profile ready looks tight.
>Gustavo, what's driving that schedule? How does it fit with the RDDS
>development processes that are either under way or being considered? The
>I was part of made a number of recommendations that depend on RDAP. Where
>those recommendations come into play?

The schedule for implementing the thick Whois policy that is
under way.

>This gTLD registry operator wants to be sure that we do this once, we do
>so that we don't have to undo things in the future, and we make
>implementation decisions based on consensus policies. If that takes time,
>be it.

I think that we share the same objective. The gTLD profile was sent to the
RySG, RrSG, ICANN gtld-tech mailing list, and this group in order to
obtain feedback. The RDAP profile will be published once that the
ICANN-contracted parties agree that it¹s ready. This is the same the
process that we used with the Whois clarification advisory.

The schedule that Francisco described in his email (i.e.
appears to work from our perspective, but based on the feedback, it may
not work.

A great percentage of the provisions in the gTLD profile are related to
ICANN policy, and some are just a translation of the requirements in the
Registry Agreement and the Whois advisory (I.e.
7-en) to RDAP. There are provisions that could be part of a BCP, but I
don't think that there is an issue. We can work in the gTLD profile and
BCP(s) in parallel. Once the BCP(s) are ready, the gTLD profile is
modified or a new version is released.

I think that is really important to consider all users of RDAP (I.e.
ccTLDs, gTLDs, RIRs) if the WG decides to work on BCP(s).