Brian, Andy, Comments inline.
Regards, Gustavo From: regext <regext-boun...@ietf.org> on behalf of Andy Newton <a...@arin.net> Date: Wednesday, August 3, 2016 at 11:09 To: Brian Mountford <mountf...@google.com> Cc: "regext@ietf.org" <regext@ietf.org> Subject: Re: [regext] RDAP questions > > >> On Aug 3, 2016, at 12:32 PM, Brian Mountford <mountf...@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 >
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ regext mailing list regext@ietf.org https://www.ietf.org/mailman/listinfo/regext
