IETF Logo Mail Archive

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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 07 October 2015 14:41 UTC

Return-Path: <shollenbeck@verisign.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 6184C1A065C for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 07:41:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.3
X-Spam-Level:
X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_LOW=-0.7] 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 jBr41CelnSKt for <eppext@ietfa.amsl.com>; Wed, 7 Oct 2015 07:41:29 -0700 (PDT)
Received: from mail-qg0-f98.google.com (mail-qg0-f98.google.com [209.85.192.98]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F4831A03F9 for <eppext@ietf.org>; Wed, 7 Oct 2015 07:41:29 -0700 (PDT)
Received: by qged68 with SMTP id d68so1002338qge.2 for <eppext@ietf.org>; Wed, 07 Oct 2015 07:41:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:mime-version; bh=7rITNUelYT90GOD1Vl56aXQkTjgxAsqOX5Fs/gxW+Hw=; b=iQvHstIFJ78xRi5EUfJhEyfnAxEHBG94CPA+tZQ/vTxIuN3S+yk4/mzkeCKJ9wgOH3 LtFQHtXvKgNH4xdsyiTZ7tzprOMcLgu9MsfNMVoJfpCJWsvXA7ksrpDSinw3v/4W72q/ Socb752hkQsv6YyCu6BCS+q/I7obXQiAWlr6cQ6gQ4+LtW9e+EKEiWGyy87jJv1zLK9x 4EDqRrCCTKqEE4wi+Z58Ieca+JEi3Vyt+vQBI3Duvq2dIwmLtgItZgTpxGRvSNpCzj00 yTZjjcPOz6CDcqtS4Lr8tKjeuloox8gvywGA0+kR6BAMlN0VzJIntwgxv9vkBsV+Kck3 1Faw==
X-Gm-Message-State: ALoCoQkMD8K9Heh68Z06QqeLAkc0UOhAhKQ/HAbPl2jewTOYitBT3jbXvIdqLuh7lhP4KW3nydc4sRB3Te1Zg0nrYW3/nteW+g==
X-Received: by 10.140.101.226 with SMTP id u89mr1930923qge.90.1444228888486; Wed, 07 Oct 2015 07:41:28 -0700 (PDT)
Received: from brn1lxmailout01.verisign.com (brn1lxmailout01.verisign.com. [72.13.63.41]) by smtp-relay.gmail.com with ESMTPS id f131sm4108541qka.2.2015.10.07.07.41.28 (version=TLSv1 cipher=RC4-SHA bits=128/128); Wed, 07 Oct 2015 07:41:28 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas02.vcorp.ad.vrsn.com (brn1wnexcas02 [10.173.152.206]) by brn1lxmailout01.verisign.com (8.13.8/8.13.8) with ESMTP id t97EfR5d016436 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Wed, 7 Oct 2015 10:41:27 -0400
Received: from BRN1WNEXMBX02.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas02.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Wed, 7 Oct 2015 10:41:27 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Gustavo Lozano <gustavo.lozano@icann.org>, Patrik Wallström <pawal@blipp.com>
Thread-Topic: [eppext] [gtld-tech] RDAP server of the registry
Thread-Index: AQHQ/3rntucFay3MHE6AZbmw28rIeZ5dIheggAGh9YCAAAlGYIAAen8AgACX8ZCAAFz6AIAAGGWA///F5VA=
Date: Wed, 07 Oct 2015 14:41:26 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A0AC026@BRN1WNEXMBX02.vcorp.ad.vrsn.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>
In-Reply-To: <D23A9BCF.C1455%gustavo.lozano@icann.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: multipart/signed; boundary="----=_NextPart_000_00B4_01D100EC.B71F51E0"; protocol="application/x-pkcs7-signature"; micalg="SHA1"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/NotzhJlZucfCWY_2a0Y5fiIYtxA>
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 14:41:31 -0000

> -----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

v2.23.0 | Report a Bug | By Email