IETF Logo Mail Archive

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

"Greg Aaron" <greg@illumintel.com> Wed, 07 October 2015 17:00 UTC

Return-Path: <greg@illumintel.com>
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 F08301B2EEF for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 10:00:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Level:
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] 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 jXd7nl-V50JA for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 10:00:11 -0700 (PDT)
Received: from p3plsmtpa08-10.prod.phx3.secureserver.net (p3plsmtpa08-10.prod.phx3.secureserver.net [173.201.193.111]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAA971B2EF0 for <eppext@ietf.org>; Wed, 7 Oct 2015 10:00:08 -0700 (PDT)
Received: from GregTHINKPAD ([108.36.224.115]) by p3plsmtpa08-10.prod.phx3.secureserver.net with id SH071r0042W0KDo01H07fq; Wed, 07 Oct 2015 10:00:08 -0700
From: Greg Aaron <greg@illumintel.com>
To: "'Hollenbeck, Scott'" <shollenbeck@verisign.com>, 'Gustavo Lozano' <gustavo.lozano@icann.org>, 'Patrik Wallström' <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, 07 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
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHQ/3rntucFay3MHE6AZbmw28rIeZ5dIheggAGh9YCAAAlGYIAAen8AgACX8ZCAAFz6AIAAGGWA///F5VCAACTY0A==
Content-Language: en-us
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/Uix1IWVl1Lr2bAgT7zahysnOJzc>
X-Mailman-Approved-At: Fri, 09 Oct 2015 04:32:49 -0700
Cc: gtld-tech@icann.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 17:00:12 -0000

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öm
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ö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?

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

v2.23.0 | Report a Bug | By Email