Re: [weirds] Questions about suffix matches in domain and nameserver searches

"Hollenbeck, Scott" <shollenbeck@verisign.com> Sun, 01 November 2015 02:02 UTC

Return-Path: <shollenbeck@verisign.com>
X-Original-To: weirds@ietfa.amsl.com
Delivered-To: weirds@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B5A4A1B500D for <weirds@ietfa.amsl.com>; Sat, 31 Oct 2015 19:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7] 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 zdu8O6lM13b4 for <weirds@ietfa.amsl.com>; Sat, 31 Oct 2015 19:02:29 -0700 (PDT)
Received: from mail-oi0-f98.google.com (mail-oi0-f98.google.com [209.85.218.98]) (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 AA5BD1B500C for <weirds@ietf.org>; Sat, 31 Oct 2015 19:02:29 -0700 (PDT)
Received: by oigi82 with SMTP id i82so6716563oig.0 for <weirds@ietf.org>; Sat, 31 Oct 2015 19:02:28 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:content-type:content-transfer-encoding :mime-version; bh=mLiLWKbfttFJ+fqLEomE1UhKr74Aj64/tXKnvUgJHpM=; b=aOYQtxJPsFcrTrzT1DreEM+yoI/FftK+JZAClvdLXWAG4So07kMhflyGjhKqjLUMtw Ja6S6LMVw6bIy06VQ7A7zFf1P+Vn4oNip0WKayjeJELSc3srGN3DeHUAS4JNiq6758jI S/sPFai2542mL29un4FG6/QwfC4vCopEk6Q9Q/vfLV/FLjT/qWROEdqD9/XV9NT4CpKP sTtD8rPp79f3+wO8halBFuMidUgjJOuW4mgjeVATOW6rrRP/xKPQE3Le0hX/OrDmgBVP LNyAVXLnQbV7TqfqHusLEDUs1OjisUkt/RlzJSYWkRbnQJio1YkBPU+th9VlVjVREJM2 llUg==
X-Gm-Message-State: ALoCoQlzAr7Y+UXIW7M1yS5KQNJttfMI+qfihF/oIeqdZkbD75yJr2gMLC/8/a5M+zDwPjql4IQA/1vW0OZ+YwAIjagkhD+mDA==
X-Received: by 10.55.79.205 with SMTP id d196mr20332749qkb.76.1446343348659; Sat, 31 Oct 2015 19:02:28 -0700 (PDT)
Received: from brn1lxmailout02.verisign.com (brn1lxmailout02.verisign.com. [72.13.63.42]) by smtp-relay.gmail.com with ESMTPS id a90sm1689603qkj.2.2015.10.31.19.02.28 (version=TLSv1 cipher=RC4-SHA bits=128/128); Sat, 31 Oct 2015 19:02:28 -0700 (PDT)
X-Relaying-Domain: verisign.com
Received: from brn1wnexcas01.vcorp.ad.vrsn.com (brn1wnexcas01 [10.173.152.205]) by brn1lxmailout02.verisign.com (8.13.8/8.13.8) with ESMTP id tA122RBC010153 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Sat, 31 Oct 2015 22:02:28 -0400
Received: from BRN1WNEXMBX01.vcorp.ad.vrsn.com ([::1]) by brn1wnexcas01.vcorp.ad.vrsn.com ([::1]) with mapi id 14.03.0174.001; Sat, 31 Oct 2015 22:02:27 -0400
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: Andrew Newton <andy@hxr.us>, Brian Mountford <mountford@google.com>
Thread-Topic: [weirds] Questions about suffix matches in domain and nameserver searches
Thread-Index: AQHRFCNLIw5lxn79qEyeQtcjNaurNJ6GaaGw
Date: Sun, 1 Nov 2015 02:02:26 +0000
Message-ID: <831693C2CDA2E849A7D7A712B24E257F4A0D3033@BRN1WNEXMBX01.vcorp.ad.vrsn.com>
References: <CALRmJyh8wX3f2tVmk9cfegK=LjF1Bm_j_Hq5Yd1C4NjSUJnKKw@mail.gmail.com> <CAAQiQRdgKUT3S+cVr8=Hk=YBNr_E7d9thNJ=2HaMpesJi2cfLg@mail.gmail.com>
In-Reply-To: <CAAQiQRdgKUT3S+cVr8=Hk=YBNr_E7d9thNJ=2HaMpesJi2cfLg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.173.152.4]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/weirds/hZoS1_Vbeepv5cHj4O6VsmDuGW8>
Cc: "weirds@ietf.org" <weirds@ietf.org>
Subject: Re: [weirds] Questions about suffix matches in domain and nameserver 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: Sun, 01 Nov 2015 02:02:31 -0000

> -----Original Message-----
> From: weirds [mailto:weirds-bounces@ietf.org] On Behalf Of Andrew
> Newton
> Sent: Saturday, October 31, 2015 5:30 PM
> To: Brian Mountford
> Cc: weirds@ietf.org
> Subject: Re: [weirds] Questions about suffix matches in domain and
> nameserver searches
> 
> On Fri, Oct 30, 2015 at 1:40 PM, Brian Mountford <mountford@google.com>
> wrote:
> > But then I'm not sure how one would efficiently
> > implement the domain label suffixes.
> 
> I'm sure if I thought about it for awhile, I could figure something
> out. But you are correct that standard SQL 'like' matching won't do
> the trick. Perhaps somebody from a domain registry could provide some
> hints.
> 
> > I am tempted to think
> > that the authors figured that queries too complicated for a given
> system
> > would just get rejected as per the wiggle room in the RFC.
> 
> That is the answer you have been looking for. :)

Andy's right. Search functionality was a late addition to the document, and we struggled to find a reasonable compromise between minimally needed functionality and complexity.

Scott