From: "Greg Aaron" <greg@illumintel.com>
To: "'Hollenbeck, Scott'" <shollenbeck@verisign.com>,
 "'Gustavo Lozano'" <gustavo.lozano@icann.org>,
 =?iso-8859-1?Q?'Patrik_Wallstr=F6m'?= <pawal@blipp.com>
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>
Date: Wed, 7 Oct 2015 13:00:04 -0400
Message-ID: <046b01d10121$9e35f5a0$daa1e0e0$@com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Thread-Index: AQHQ/3rntucFay3MHE6AZbmw28rIeZ5dIheggAGh9YCAAAlGYIAAen8AgACX8ZCAAFz6AIAAGGWA///F5VCAACTY0A==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Uix1IWVl1Lr2bAgT7zahysnOJzc>
Cc: gtld-tech@icann.org, eppext@ietf.org
Subject: Re: [eppext] [gtld-tech]   RDAP server of the registry
Precedence: list

Scott, the term "consensus policies" has a specific and formal meaning =
at
ICANN.  Were you using that meaning in your post?

All best,
--Greg


-----Original Message-----
From: gtld-tech-bounces@icann.org [mailto:gtld-tech-bounces@icann.org] =
On
Behalf Of Hollenbeck, Scott
Sent: Wednesday, October 07, 2015 10:41 AM
To: Gustavo Lozano; Patrik Wallstr=F6m
Cc: gtld-tech@icann.org; eppext@ietf.org
Subject: Re: [gtld-tech] [eppext] RDAP server of the registry

* PGP - S/MIME Signed by an unverified key: 10/7/2015 at 10:41:25 AM

> -----Original Message-----
> From: Gustavo Lozano [mailto:gustavo.lozano@icann.org]
> Sent: Wednesday, October 07, 2015 10:00 AM
> To: Patrik Wallstr=F6m; 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=20
> 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?

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.

Scott

* Hollenbeck, Scott <shollenbeck@verisign.com>
* Issuer: Symantec Corporation - Unverified