[weirds] Entity name searches

Brian Mountford <mountford@google.com> Fri, 06 November 2015 20:55 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 D63B81A003A for <weirds@ietfa.amsl.com>; Fri, 6 Nov 2015 12:55:14 -0800 (PST)
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 4I_6x1BYrQvf for <weirds@ietfa.amsl.com>; Fri, 6 Nov 2015 12:55:13 -0800 (PST)
Received: from mail-vk0-x22c.google.com (mail-vk0-x22c.google.com [IPv6:2607:f8b0:400c:c05::22c]) (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 AC30A1A01F7 for <weirds@ietf.org>; Fri, 6 Nov 2015 12:55:13 -0800 (PST)
Received: by vkbk63 with SMTP id k63so11270847vkb.0 for <weirds@ietf.org>; Fri, 06 Nov 2015 12:55:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:from:date:message-id:subject:to:cc:content-type; bh=4g0TLLBXCU403aKo3t1itNPVMWHI4Qb1nvp1c/jZ2NQ=; b=dY5ftspg6Wg2RxwahGTSJ+1mj73H2Xgd1JFAE5UAzEEGtEx8uRzn0Pfz+GT3HHm/KC jydBo0ko51pRbg/0fJhGvG2vyp7j7gIZ+yqIApIr2ZESXcv0RiSgy80IgVie8goP2os+ /l3gm1NyrDolGCyW/pZy0++OwCeacxhYx8rATtXnzd6wJ8hPl/GNlMSVq6A4069mT/sC ts7zuSkGxVcn7iu7pp+2lOEDPNLCYQHOr9CTtxJRYF/FIPrISQiH+ytBFY5Hrh6xTu94 YN69L5HTEpdnnxIWZVCkw1FsnZajzwMEkPc5W0WNgOmxnBJn8bYOYvXhH8ovzjLdZbWj Rb/A==
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:cc :content-type; bh=4g0TLLBXCU403aKo3t1itNPVMWHI4Qb1nvp1c/jZ2NQ=; b=JshjKE/UYKByoeJo42drYzmbQeGauDYMZtSZDBKubG2+W5fIyYXjfcgQOmZuqVdkyC LIFBMB8K+ZMuS+DuhicDEVrGDlHqaDruqcOh1DcUTeAP4YB78riPo3eN7fTKJPHsn20X o3u2UOvgX+AziPiFVWCRB5kIDq+n+37Yxigaspqpf85S1LUQM2hbAcz5ULjxAtSsQ8ih Gehm9hQ6x/HHKYOB8h1zpIuWefWs9r4PXFfaH32f9iUSQ8QqBwGcy/qGqIAvD21mT5mk puJWRCZvt4VVMOt5tARHSqVxYS/r+qlQUEf68/1UXRT+964ANcjC2NQ+FemxrCNTwwmf 0kcQ==
X-Gm-Message-State: ALoCoQmTi4I59S8aldkqdQupKC/4Est4WfV06XmfPlLFgCsNNRvuuBAOMBwxKMRAimQ5THZHnKTB
X-Received: by with SMTP id m69mr15770045vkd.66.1446843312736; Fri, 06 Nov 2015 12:55:12 -0800 (PST)
MIME-Version: 1.0
Received: by with HTTP; Fri, 6 Nov 2015 12:54:53 -0800 (PST)
From: Brian Mountford <mountford@google.com>
Date: Fri, 6 Nov 2015 15:54:53 -0500
Message-ID: <CALRmJyi6i-fo12M0M-gx9Ds50P+0esmX1cRkaFwW_2_L=xcNvg@mail.gmail.com>
To: weirds@ietf.org
Content-Type: multipart/alternative; boundary=001a11456322b3bfd10523e575da
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/3zbHYJwZO9clG4vsSiTkAkhEaeQ>
Cc: Justine Tunney <jart@google.com>
Subject: [weirds] Entity name searches
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, 06 Nov 2015 20:55:15 -0000

RFC 7483 describes entity name searches. As I understand it, the searches
are to use the same rules as for domains and nameservers: a prefix,
followed by at most one wildcard, followed by some number of domain labels.
I have been assuming that there will be no domain labels for entity names,
so it would just be a prefix search.

My coworker has pointed out to me that this isn't necessarily so useful.
You could search for contacts by first name, but not by last, and so on. Is
that in fact what you have in mind with these sorts of searches?

And only names? There is no provision for searching entities by address,

Also, what is to be done with non-ASCII characters? Should the names be
folded to ASCII values, so that a search for "Bohm" will match an O with an
umlaut? Or is that not correct behavior? Is this to be a case-insensitive
search? What about whitespace? We didn't see clear directives in the RFC,
but maybe we missed them.