[weirds] RDAP registrar entities

Brian Mountford <mountford@google.com> Fri, 30 October 2015 16:02 UTC

Return-Path: <mountford@google.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id EE5921B2D53 for <weirds@ietfa.amsl.com>; Fri, 30 Oct 2015 09:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.388
X-Spam-Status: No, score=-1.388 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=no
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id VEF6Yoki-6pk for <weirds@ietfa.amsl.com>; Fri, 30 Oct 2015 09:02:03 -0700 (PDT)
Received: from mail-vk0-x235.google.com (mail-vk0-x235.google.com [IPv6:2607:f8b0:400c:c05::235]) (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 CD7041A883E for <weirds@ietf.org>; Fri, 30 Oct 2015 09:02:02 -0700 (PDT)
Received: by vkex70 with SMTP id x70so49850466vke.3 for <weirds@ietf.org>; Fri, 30 Oct 2015 09:02:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:content-type; bh=rbXAslsA7l6CXRBFAZkffJfm2ook+lBYYrzEDnc9rJ8=; b=WV5RHcEp6Q7jlsKSr7My+4nRFEcaCkmKSxa6JkyRsWXGeaguhHEdJ7R/grpIIt9dqs wOXknQsf7uO5Is1Zc7erVAMGjoU2ccm5LV3CUmxUg9LpwFwYmmXRIT8kJ1p4Cx+/swKq i+j4f8HAEnzxuFFh+5IqPHG1l9qJU0cXlnOjQfq4uxKLom+G05F7EY2b5FWDRwwSwZif gDRvW10Y4KBWt3/vLbl+1l5sFNZAiShBaFvUIbZo3Yb9+JkHY9W+PPh4iGpmhzhvpPJ+ rzqLbxK/la+pKaSQIe90nudfoO6TQs55J7pyie2UzHqltumQnqjGmghS8SaBiE4++CU6 J2QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:from:date:message-id:subject:to :content-type; bh=rbXAslsA7l6CXRBFAZkffJfm2ook+lBYYrzEDnc9rJ8=; b=Ek4z6groSwFb+6EFMhrTMTtgQZ78WZ4gtakFxnRvWZjDa1rlcsNjswzf8H3pxS10VK horO03I7xbFg1knBUk00/gKaYvcnHzOwLzXY7fw0E06WuYVtlhDEhq8bpLzH04IJSrTQ eq7UalEgGtg5T1YlIcOW2JPkvvURszFPCrDzgQjNCmt8vcghM8akFPCNbMUc368bd1VQ /Q0i2KuvI0mB90+3WbMqvD+Ann9XZ6IDMtL3Shy4fCmUNy7iYqPR13q59NEyaczAD4TT RQ0OR8gvK0PXvCwI/ZYjwakGrCZYHTgQM3AWmrXQCJItv5AZciwYO91PPsSW5ZCxiHp/ e+/Q==
X-Gm-Message-State: ALoCoQnr11xO9ZuPsILP1y7DU3X8+VcVKCNbzN1Z9xCfnPRAGaUpUXoATxHSM1mncjVsdLJGD5Du
X-Received: by with SMTP id m69mr5868282vkd.66.1446220920770; Fri, 30 Oct 2015 09:02:00 -0700 (PDT)
MIME-Version: 1.0
Received: by with HTTP; Fri, 30 Oct 2015 09:01:41 -0700 (PDT)
From: Brian Mountford <mountford@google.com>
Date: Fri, 30 Oct 2015 12:01:41 -0400
Message-ID: <CALRmJyhTqpJ4NGhrZ4kWv9oenwpA6X=7Ld2S_dg5KGXFeTs8_g@mail.gmail.com>
To: weirds@ietf.org
Content-Type: multipart/alternative; boundary=001a11456322400c940523548cd9
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/Wwqgp8sVZTq471vOVILL_JAH3Ak>
Subject: [weirds] RDAP registrar entities
X-BeenThere: weirds@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "WHOIS-based Extensible Internet Registration Data Service \(WEIRDS\)" <weirds.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/weirds>, <mailto:weirds-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/weirds/>
List-Post: <mailto:weirds@ietf.org>
List-Help: <mailto:weirds-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/weirds>, <mailto:weirds-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 30 Oct 2015 16:02:05 -0000

Hello, all. I have been directed to this list as a possible place to get
some RDAP questions answered. Here's one, regarding RDAP entities, which
appear to include both contacts and registrars. In our system internally,
the two are quite separate, and in fact registrars can themselves have
multiple contacts, just as a domain can. So I'm trying to figure out how to
fit the data into the RDAP format.

First of all, is there a reason why registrars and contacts were lumped
together into one type of thing? Just curious.

The example in RFC 7483 for a registrar included several addresses and
phone numbers, as if the sample registrar also had contacts associated with
it. But none of the addresses and phone numbers were marked with anything
that would distinguish between the contacts (e.g. a type of "admin",
"tech", etc.). Should we just take all the data we have for a registrar,
including all addresses of associated contacts, and throw them into the
entity JSON object one after another? Can we mark them with the contact
role as a type? Or does type always need to be "home" or "work"?

RFC 7482 describes searching for an entity by name. In the case of our
registrars, we have two things that could be a "name": the name of the
registrar itself, and the name of any associated contact. Am I correct that
the search is confined to the registrar name? Or are we supposed to look
through to the contact names, and pass back any registrar with a matching