Re: [regext] 7482bis: Partial String Search Clarification

"Hollenbeck, Scott" <shollenbeck@verisign.com> Tue, 28 January 2020 14:11 UTC

Return-Path: <shollenbeck@verisign.com>
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 521571200D7 for <regext@ietfa.amsl.com>; Tue, 28 Jan 2020 06:11:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level:
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=verisign.com
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 eEcphFRC2rau for <regext@ietfa.amsl.com>; Tue, 28 Jan 2020 06:11:14 -0800 (PST)
Received: from mail2.verisign.com (mail2.verisign.com [72.13.63.31]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 422AC120058 for <regext@ietf.org>; Tue, 28 Jan 2020 06:11:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=3310; q=dns/txt; s=VRSN; t=1580220674; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=mjNVEa9YSL1mYdwVUh65wwXtQrmL5DPbReyxCaD5GNA=; b=ZaEQZLfHXRv9Rz7Dsxlom3f5E10rpiknUPfOYiBia+OEOjOZjy9xBxKC 7eJ1FvGfhwffi2jT4FPgl8UCPh8YvEVqfMHMcGCHkBAdnUiObtg3nNHdc Y0aBeUHQhFQNc/vVlaRdkJ4UGgDvp2SrxCk9KHszY9QQsHkcUDJaTIgMS hAr+VcZ+0lqoela9BgMcV/cbfZPWuEEnCijUP1PuXbc9tHBqFXKjMp3v4 I5Y00K0nQZzGUkZOZW7YXj+GEKFaePnXBPrHbYtNhuk6nL5h3wMu53RJm rDjLY0x++xXhHQEJnxeJmzPR4+WVDg0QMTdDrS3JaosxEaM34fhNKBnwE Q==;
IronPort-SDR: 39dd8pW10BikFwJiDTgt0zElSk1ym/RWdre3hTT4nki+8NauqJcao+90rzHcv2bwDCQVu2x16l kQjgzi36N5O/dGqlB4PvSUx0DAmMDxND/a529BafGFoobcGBFO9uOWZCuSyXMJuAj9jfzDNJT1 qryL2ijyC8rRi4cZVQORJkFNbBUlj7zTPi0gwBL5u5WL7vc+rEmV6soQWfVOHmbgoPzHtoZN13 tNOjTjalWUmT9GnOrmEJHM4ebQtv7uj4AtGea/Rq9rSxEbUAT3UileI5GNLakkoii1UUgsyunc gYg=
X-IronPort-AV: E=Sophos;i="5.70,374,1574121600"; d="scan'208";a="37105"
IronPort-PHdr: 9a23:kmkdzxfP2pcOlwjNW+CmKFHxlGMj4u6mDksu8pMizoh2WeGdxc27ZBKN2/xhgRfzUJnB7Loc0qyK6vymAjBLvMbJ8ChbNsAVDFld0YRetjdjKfbNMVf8Iv/uYn5yN+V5f3ghwUuGN1NIEt31fVzYry76xzcTHhLiKVg9fbytScbdgMutyu+95YDYbRlWizqhe7NyKwi9oRnMusUMjoZuN6k8xgHHr3ZHdOhbxWBlLk+Xkxrg+8u85pFu/zletv4768JMTaD2dLkkQLJFCzgrL3o779DxuxnZSguP6HocUmEInRdNHgPI8hL0UIrvvyXjruZy1zWUMsPwTbAvRDSt9LxrRwPyiCcGLDE27mfagdFtga1BoRKhoxt/w5PIYIyQKfFzcL/Rcc8cSGFcWMtaSi5PDZ6mb4YXD+QPI/tWr5XzqVUNoxuxBwisC//gxDBHnXL2wbQ60+Y9HQ3awAAsAdQDu2nUotXvM6cSVPi4wKfKwzXEa/NW3Sny6I7TfR8/vf6MXqp8etfMx0YzEAPFkkmQpYL4ND6SzeQNs2+b7+5kVe2xjW4osB9+rSSsxso3lInGmJgVylHf9SV4z4Y1I8e0R1J8Yd6hCZZdsTyROYVxQsMnWW5ouSA6x6UYtp+0ZicKzYwnxxrBZPCddYiH/A7jWP6PLjZ3nn1lfaq/hxKs/kS61uL8Ucy03E5UoStKiNbMs2oB2ADU6siCTPZ240Sv2S6X2gzO9u1IO104mKjVJpI737I9lpQevV7MEyL1gEn6kbOael859uWq9+jreKjqq5CfOoNulw3zMbwimsKhDuk7LgQDWm2W9Oag27H/50L0RahGgeEqnaTcsJ3VONoUpqC8DgJRz4ks9giwAjG729oCh3YHNkhKeBefgojsPFHBPe73AO+kg1SpjDdr3/fGPqD9ApnVLnjMjrPhfbFl5kNB1AQ91c1T6JJMBL8OIf3/RlL9uMbGDhAlNAy02f7nBM9n2YwDQ26PHLWZMLjUsVOS+u0vJOyMaJcUuDb7Nfcl++bjgWIllVMHYKWk35UaZGqlEvlmLUiVe3Xhj9QZHWcPpAU+TejqiFOYUT5UYna/R7k85jE8CIKiCYfMWIatj6ef0yinHZ1bfX5GBU6WEXfpbIWEWvgMaCSILsB9lTwEUKCtS5U92hG2qA/6171nI/LR+iICr5Lj1d916/fXlRE1+zx0Ad6d3H+QQGFzhW4IRj423LxlrUNhzFeDy7J0g/1EFdZL/fNGTh86NYLAz+x9E93yQBzOftiXR1epXtWrGjAxQcwtw98AeUp9HM+ijh+QlxatVvUQnqaKA9ow9azSxXX9IO58ymqA3687yVg6CIMbMGS8h6k58w/dCZTEn0Kxlqe2M68axmjM6DHHhSCUsU5VQBJYUKjZUzYYfESc5YDj60zPX6OGCLk7PE1G08HUeYVQbdi8x3VBQPPuPt7TaGH101y7AgqUjPvYd4rtf2EQ2i/QA0ssjQ0J/G2HOg54DSCk9TGNRAdyHE7iNhu/udJ1r2m2Gxc5
X-IPAS-Result: A2HfAgDjPzBe/zCZrQplHAEBAQEBBwEBEQEEBAEBgXuDFYExCpVGmzgJAQEBAQEBAQEBBwEbFAEBAoQ+AoJLOBMCAwEBCwEBAQQBAQEBAQUDAQEBAoYgDII7IhhZRAEBAQEBAQEBAQIBAQEfAQEBAQEBIwINVDM1AQEBAQM6SwQCAQgRBAEBHxAyHQgBAQQBEgiDH68mgieFSoR+gTiMOIFCPoQkPoQjEIYEBI04iRuJUY4+dgMHgjmHQo5tI4NAlzyOYJZ1hBgCBAIEBQIVgWmBe3BQgmwJRxgNkhCEWYV6dItugTKBEAEB
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX01.vcorp.ad.vrsn.com (10.173.153.48) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Tue, 28 Jan 2020 09:11:06 -0500
Received: from BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde]) by BRN1WNEX02.vcorp.ad.vrsn.com ([fe80::7c0a:1cc:5def:9dde%4]) with mapi id 15.01.1779.002; Tue, 28 Jan 2020 09:11:06 -0500
From: "Hollenbeck, Scott" <shollenbeck@verisign.com>
To: "mario.loffredo@iit.cnr.it" <mario.loffredo@iit.cnr.it>, "regext@ietf.org" <regext@ietf.org>
Thread-Topic: [EXTERNAL] Re: [regext] 7482bis: Partial String Search Clarification
Thread-Index: AdXR8Jng5DjZCeksQPmsuSA/dHsolAAMLssAAPB6esA=
Date: Tue, 28 Jan 2020 14:11:06 +0000
Message-ID: <4257030f1d8645e39c87ee772ad6a98e@verisign.com>
References: <0d07b9a1683f4389931b2e7864edb14c@verisign.com> <274c0386-1754-8fc8-9e0d-f3a852a43fc1@iit.cnr.it>
In-Reply-To: <274c0386-1754-8fc8-9e0d-f3a852a43fc1@iit.cnr.it>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.170.148.18]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/PBvn43npYzy9IIUZLXTocJMnx1A>
Subject: Re: [regext] 7482bis: Partial String Search Clarification
X-BeenThere: regext@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Jan 2020 14:11:16 -0000

> -----Original Message-----
> From: Mario Loffredo <mario.loffredo@iit.cnr.it>
> Sent: Thursday, January 23, 2020 9:14 AM
> To: Hollenbeck, Scott <shollenbeck@verisign.com>; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] 7482bis: Partial String Search Clarification
> 
> 
> Il 23/01/2020 14:40, Hollenbeck, Scott ha scritto:
> > This is a 7482 clarification proposal that I received off-list.
> >
> > Current text:
> > Partial string searching uses the asterisk ('*', US-ASCII value 0x002A)
> character to match zero or more trailing characters.  A character string
> representing multiple domain name labels MAY be concatenated to the end
> of the search pattern to limit the scope of the search.  For example, the
> search pattern "exam*" will match "example.com" and "example.net".  The
> search pattern "exam*.com" will match "example.com".  If an asterisk
> appears in a search string, any label that contains the non-asterisk characters
> in sequence plus zero or more characters in sequence in place of the asterisk
> would match. Additional pattern matching processing is beyond the scope of
> this specification.
> >
> > Proposed new text:
> > Partial string searching uses the asterisk ('*', US-ASCII value 0x002A)
> character to match zero or more trailing characters.  A character string
> representing [a domain label suffix] MAY be concatenated to the end of the
> search pattern to limit the scope of the search.  For example, the search
> pattern "exam*" will match "example.com" and "example.net".  The search
> pattern "exam*.com" will match "example.com".  If an asterisk appears in a
> search string, any label that contains the non-asterisk characters in sequence
> plus zero or more characters in sequence in place of the asterisk would
> match. [Only a single asterisk is allowed for a partial string search.] Additional
> pattern matching processing is beyond the scope of this specification.
> >
> > What do people think about this proposal?
> 
> My opinion is that allowing one or more asterisks in partial matching should
> be a matter of the server policy.

Mario, I'd like to push back a bit on this suggestion. The intent of the original text was to allow for only a single pattern-matching asterisk, so if we change the text to allow more than one we're changing the protocol. A protocol change means we'd need to re-spin 7482 at the Proposed Standard level, and that's something I'm trying to avoid for now.

Additionally, if we say "server policy", we'd need to figure out how to publish and discover these policies. That, too, goes beyond what's currently in 7482.

My preference for improving search would be to produce another draft/RFC that adds whatever new capabilities are desired. There was an effort to do this a while back in an Internet-Draft that described regular expression searching, but that draft never caught on with anyone. We've also seen very little implementation of partial string searching in the real world (it's not included in ICANN's gTLD profile, for example), so there may not be a lot of support for the concept. So, can we just clarify the original intent in 7482bis and leave search improvement to another effort?

Scott