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

Gustavo Lozano <gustavo.lozano@icann.org> Wed, 07 October 2015 16:38 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: eppext@ietfa.amsl.com
Delivered-To: eppext@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D4541ACE4E for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 09:38:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.13
X-Spam-Level:
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 mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id en6UUP3WLsVa for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 09:38:12 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9BEA81A1A97 for <eppext@ietf.org>; Wed, 7 Oct 2015 09:38:12 -0700 (PDT)
Received: from PMBX112-W1-CA-1.pexch112.icann.org (64.78.40.21) by PMBX112-W1-CA-2.pexch112.icann.org (64.78.40.23) with Microsoft SMTP Server (TLS) id 15.0.1044.25; Wed, 7 Oct 2015 09:38:10 -0700
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.1044.021; Wed, 7 Oct 2015 09:38:10 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: "Hollenbeck, Scott" <shollenbeck@verisign.com>, Patrik Wallström <pawal@blipp.com>
Thread-Topic: [eppext] [gtld-tech] RDAP server of the registry
Thread-Index: AQHRAR6K/sste7+5UkCCDDnuwhzYJQ==
Date: Wed, 07 Oct 2015 16:38:05 +0000
Message-ID: <D23ABF8F.C14B6%gustavo.lozano@icann.org>
References: <D23802A0.C0D5E%gustavo.lozano@icann.org> <831693C2CDA2E849A7D7A712B24E257F4A0A9B8A@BRN1WNEXMBX02.vcorp.ad.vrsn.com> <9FBF2B96-1FF2-4A5F-9697-388AEA71BF67@ripe.net> <831693C2CDA2E849A7D7A712B24E257F4A0AB58B@BRN1WNEXMBX02.vcorp.ad.vrsn.com> <88246F46-92E4-4848-BC5B-2275E942C4AF@ripe.net> <831693C2CDA2E849A7D7A712B24E257F4A0ABD5A@BRN1WNEXMBX02.vcorp.ad.vrsn.com> <DE7011CD-9673-4A41-8F15-B37B51BE9879@blipp.com> <D23A9BCF.C1455%gustavo.lozano@icann.org> <831693C2CDA2E849A7D7A712B24E257F4A0AC026@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
In-Reply-To: <831693C2CDA2E849A7D7A712B24E257F4A0AC026@BRN1WNEXMBX02.vcorp.ad.vrsn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.5.5.150821
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [192.0.32.234]
Content-Type: multipart/signed; protocol="application/pkcs7-signature"; micalg="sha1"; boundary="B_3527066279_1021800"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/peB29X2wyDicBxIK0A8_oe4_6RI>
Cc: Kaveh Ranjbar <kranjbar@ripe.net>, "gtld-tech@icann.org" <gtld-tech@icann.org>, "eppext@ietf.org" <eppext@ietf.org>
Subject: Re: [eppext] [gtld-tech] RDAP server of the registry
X-BeenThere: eppext@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: EPPEXT <eppext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/eppext>, <mailto:eppext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/eppext/>
List-Post: <mailto:eppext@ietf.org>
List-Help: <mailto:eppext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/eppext>, <mailto:eppext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Oct 2015 16:38:14 -0000


On 10/7/15, 10:41, "Hollenbeck, Scott" <shollenbeck@verisign.com> wrote:

>> -----Original Message-----
>> From: Gustavo Lozano [mailto:gustavo.lozano@icann.org]
>> Sent: Wednesday, October 07, 2015 10:00 AM
>> To: Patrik Wallström; Hollenbeck, Scott
>> Cc: Kaveh Ranjbar; gtld-tech@icann.org; eppext@ietf.org
>> Subject: Re: [eppext] [gtld-tech] RDAP server of the registry
>
>[snip]
>
>> 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
>policy
>development processes that are either under way or being considered? The
>EWG
>I was part of made a number of recommendations that depend on RDAP. Where
>do
>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
>it
>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,
>so
>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.
http://mm.icann.org/pipermail/gtld-tech/2015-September/000507.html)
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.
https://www.icann.org/resources/pages/registry-agreement-raa-rdds-2015-04-2
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).

Regards,

Gustavo

>
>Scott