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

Mario Loffredo <mario.loffredo@iit.cnr.it> Wed, 29 January 2020 08:38 UTC

Return-Path: <mario.loffredo@iit.cnr.it>
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 005F412022D for <regext@ietfa.amsl.com>; Wed, 29 Jan 2020 00:38:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level:
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 3mYoNzjfaRZD for <regext@ietfa.amsl.com>; Wed, 29 Jan 2020 00:38:29 -0800 (PST)
Received: from smtp.iit.cnr.it (mx3.iit.cnr.it [146.48.98.150]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42B6A120251 for <regext@ietf.org>; Wed, 29 Jan 2020 00:38:28 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by smtp.iit.cnr.it (Postfix) with ESMTP id E9A09600339; Wed, 29 Jan 2020 09:38:26 +0100 (CET)
X-Virus-Scanned: Debian amavisd-new at mx3.iit.cnr.it
Received: from smtp.iit.cnr.it ([127.0.0.1]) by localhost (mx3.iit.cnr.it [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id H3E_DtezWqUC; Wed, 29 Jan 2020 09:38:24 +0100 (CET)
Received: from [192.12.193.108] (pc-loffredo.nic.it [192.12.193.108]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits)) (No client certificate requested) by smtp.iit.cnr.it (Postfix) with ESMTPSA id 0BBC4600232; Wed, 29 Jan 2020 09:38:24 +0100 (CET)
To: "Hollenbeck, Scott" <shollenbeck=40verisign.com@dmarc.ietf.org>, "regext@ietf.org" <regext@ietf.org>
References: <0d07b9a1683f4389931b2e7864edb14c@verisign.com> <274c0386-1754-8fc8-9e0d-f3a852a43fc1@iit.cnr.it> <4257030f1d8645e39c87ee772ad6a98e@verisign.com>
From: Mario Loffredo <mario.loffredo@iit.cnr.it>
Message-ID: <0867f8a0-fcee-5287-b210-6eeac804f446@iit.cnr.it>
Date: Wed, 29 Jan 2020 09:36:26 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1
MIME-Version: 1.0
In-Reply-To: <4257030f1d8645e39c87ee772ad6a98e@verisign.com>
Content-Type: text/plain; charset=iso-8859-15; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: it
Archived-At: <https://mailarchive.ietf.org/arch/msg/regext/UXxeWJS4vRGkwGG7TT4aFpet0zM>
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: Wed, 29 Jan 2020 08:38:33 -0000

Il 28/01/2020 15:11, Hollenbeck, Scott ha scritto:
>> -----Original Message-----
>> From: Mario Loffredo <mario.loffredo@iit.cnr.it>
>> Sent: Thursday, January 23, 2020 9:14 AM
>> To: Hollenbeck, Scott <shollenbeck@verisign.com>om>; 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?

OK. No problem. I made that comment because, in my opinion, what really 
matters for server processing is the position of the asterisks rather 
than their number.

mario

>
> Scott
>
> _______________________________________________
> regext mailing list
> regext@ietf.org
> https://www.ietf.org/mailman/listinfo/regext

-- 
Dr. Mario Loffredo
Servizi Internet e Sviluppo Tecnologico
CNR - Istituto di Informatica e Telematica
via G. Moruzzi 1, I-56124 PISA, Italy
E-Mail: mario.loffredo@iit.cnr.it
Phone: +39.0503153497
Mobile: +39.3462122240
Web: http://www.iit.cnr.it/mario.loffredo