[eppext] RDAP server of the registry

Gustavo Lozano <gustavo.lozano@icann.org> Mon, 05 October 2015 14:34 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 2DEA81ACE71 for <eppext@ietfa.amsl.com>; Mon, 5 Oct 2015 07:34:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.829
X-Spam-Level:
X-Spam-Status: No, score=-2.829 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, J_CHICKENPOX_37=0.6, MIME_QP_LONG_LINE=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 p7Kcl_AW24U1 for <eppext@ietfa.amsl.com>; Mon, 5 Oct 2015 07:34:16 -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 3C23A1ACE6F for <eppext@ietf.org>; Mon, 5 Oct 2015 07:34:16 -0700 (PDT)
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 Microsoft SMTP Server (TLS) id 15.0.1044.25; Mon, 5 Oct 2015 07:34:14 -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; Mon, 5 Oct 2015 07:34:14 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: "gtld-tech@icann.org" <gtld-tech@icann.org>
Thread-Topic: RDAP server of the registry
Thread-Index: AQHQ/3rntucFay3MHE6AZbmw28rIeQ==
Date: Mon, 5 Oct 2015 14:34:13 +0000
Message-ID: <D23802A0.C0D5E%gustavo.lozano@icann.org>
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_3526886048_24897183"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/eppext/pwUjkOaM0op9apjK_EyiZwS2h2I>
Cc: "eppext@ietf.org" <eppext@ietf.org>
Subject: [eppext] 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: Mon, 05 Oct 2015 14:34:18 -0000

Hello,
 
The first version of the ICANN gTLD profile was published days ago, (see:
http://mm.icann.org/pipermail/gtld-tech/2015-September/000507.html), this
document describes basic parameters and objects to be implemented by
ICANN-contracted parties.
 
The gTLD Whois output contains a field with the Whois server of the
Registrar. In the case of thin registries, this allows the end user to get
the registration data from the registrar, and in the case of thick
registries, this allows the end user to query for extra Whois fields (e.g.
registrar expiration date).
 
The gTLD profile support the same functionality with the following
mechanism:
 
The RDAP domain lookup response MUST contain a links object as defined in
RFC7483 section 4.2. The links object MUST contain the elements rel:related
and href pointing to the Registrar's RDAP URL for the queried domain object.
 
Questions for this group:
 
* What do you think about this proposal? If you have different ideas on how
to provide this functionality, please share it with the group.
* What is your opinion about documenting this mechanism in an I-D?



 
Regards,
Gustavo Lozano
ICANN