IETF Logo Mail Archive

Re: [regext] RDAP questions

Gustavo Lozano <gustavo.lozano@icann.org> Tue, 09 August 2016 18:31 UTC

Return-Path: <gustavo.lozano@icann.org>
X-Original-To: regext@ietfa.amsl.com
Delivered-To: regext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0973212D519 for <regext@ietfa.amsl.com>; Tue, 9 Aug 2016 11:31:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.436
X-Spam-Level:
X-Spam-Status: No, score=-5.436 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-1.247, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=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 werZWvBaerHS for <regext@ietfa.amsl.com>; Tue, 9 Aug 2016 11:31:04 -0700 (PDT)
Received: from out.west.pexch112.icann.org (pfe112-ca-2.pexch112.icann.org [64.78.40.10]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C28F412D0AE for <regext@ietf.org>; Tue, 9 Aug 2016 11:31:04 -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.1178.4; Tue, 9 Aug 2016 11:31:02 -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.1178.000; Tue, 9 Aug 2016 11:31:02 -0700
From: Gustavo Lozano <gustavo.lozano@icann.org>
To: Andy Newton <andy@arin.net>, Brian Mountford <mountford@google.com>
Thread-Topic: [regext] RDAP questions
Thread-Index: AQHR8mwuoWlNwX2tqUKvOMjxySRAxw==
Date: Tue, 09 Aug 2016 18:31:01 +0000
Message-ID: <D3CF5FFE.1174C5%gustavo.lozano@icann.org>
References: <CALRmJyiz3yx=Gxa9LeWNUJU5CJczvc6ojjyVwUPL4mcbD5wKiw@mail.gmail.com> <64CC805B-AD64-4127-8645-C576104AFA8B@arin.net>
In-Reply-To: <64CC805B-AD64-4127-8645-C576104AFA8B@arin.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.6.6.160626
x-ms-exchange-messagesentrepresentingtype: 1
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_3553587059_3222011"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/_yfstr-br7ngm1S-BkVjvVI3VtI>
Cc: "regext@ietf.org" <regext@ietf.org>
Subject: Re: [regext] RDAP questions
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Registration Protocols Extensions <regext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/regext>, <mailto:regext-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/regext/>
List-Post: <mailto:regext@ietf.org>
List-Help: <mailto:regext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/regext>, <mailto:regext-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Aug 2016 18:31:07 -0000

Brian, Andy,

Comments inline.

Regards,
Gustavo

From:  regext <regext-bounces@ietf.org> on behalf of Andy Newton
<andy@arin.net>
Date:  Wednesday, August 3, 2016 at 11:09
To:  Brian Mountford <mountford@google.com>
Cc:  "regext@ietf.org" <regext@ietf.org>
Subject:  Re: [regext] RDAP questions

> 
> 
>> On Aug 3, 2016, at 12:32 PM, Brian Mountford <mountford@google.com> wrote:
>> 
>> I have a couple questions about RDAP RFC 7483.
>> RFC 7483 4.7. Port 43 WHOIS Server
>> For registries such as ourselves, is this supposed to be the registrar¹s
>> server, or ours? I would have thought the registrar¹s since WHOIS AWIP is
>> that way. But the registrar¹s WHOIS is a URL, whereas this is explicitly not
>> so.
> 
> 
> Somebody else will have to answer as to which whois server this is suppose to
> reference (I think registrar). But there is no whois URI scheme, which is why
> that is explicitly not a URI.

In the case of the RDAP profile (gTLD space), the ³port43² element is not
expected to be used, because Whois/43 tcp will be deprecated in the future.
The objective of the RDAP profile is to keep everything in RDAP, and in the
case of ³thin² registrations, the RDAP URI of the RDAP service of the
Registrar is provided to the end-user as described in 2.3 of the RDAP
profile 
(https://www.icann.org/resources/pages/rdap-operational-profile-2016-07-26-e
n).

> 
>> RFC 7483 5.1. The Entity Object Class
>> The RFC indicates that among the items of information we should return for an
>> entity is its role (admin, tech, billing, registrar, etc.). But contacts
>> don¹t necessarily have a single role. The same contact could have more than
>> one role in more than one domain. In our database, the role tag is associated
>> with the mapping of the domain to the contact, not with the contact itself.
>> So it¹s not clear how we can provide this information for contacts found
>> using a direct search. For contacts displayed as part of a domain search, or
>> for registrars, it¹s not a problem.
> 
> You have it exactly correct. If somebody were to lookup a contact directly,
> there is no context in which to have a role and therefore the ³roles² array
> should not be present.
> 
> -andy
>

v2.23.0 | Report a Bug | By Email