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

"Hollenbeck, Scott" <shollenbeck@verisign.com> Wed, 29 January 2020 15:51 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 447E5120090 for <regext@ietfa.amsl.com>; Wed, 29 Jan 2020 07:51:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.299
X-Spam-Level:
X-Spam-Status: No, score=-4.299 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, URIBL_BLOCKED=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 NwTJq6mWgx2d for <regext@ietfa.amsl.com>; Wed, 29 Jan 2020 07:51:47 -0800 (PST)
Received: from mail6.verisign.com (mail6.verisign.com [69.58.187.32]) (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 008EE120020 for <regext@ietf.org>; Wed, 29 Jan 2020 07:51:46 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=verisign.com; l=3978; q=dns/txt; s=VRSN; t=1580313107; h=from:to:date:message-id:references:in-reply-to: content-transfer-encoding:mime-version:subject; bh=t7RFAVq6E6w12YogipE4bWBVPk9CM5hTHEn0Tbt4CIs=; b=mNv0agmFyGe2IoS2L01LxsMtunS66KMVolpEASm/FT/Oa/i4J2e9wBph MUhJtbxVV3VWRHX0I9YvmNBGi1orTBYwO3vg8M7na08N7oac/PexnxcV0 y9UEyHtPT3zJlTdCiD5c7UIti4tw32yiEH8Je8ejgPIzhc9dOpKpPOfwB GsqRH2eVsaUXwDhs3cOzbyC/hmKw26WLiGbA0kSTjVn1ag7/Q3xTsOnXl r9t7obrTsQ/PcA6AbUFy+yiiLmtNZjWGD156lhZBLjf9jrjxzjY7DFhBY qMXOreXoDllHAVMOfOpQ/mHhs+hNteMRZY1BSZEDGY9hl7SBT/QzAFcFD w==;
IronPort-SDR: Vcte7+4p7FbgLuByp2CsZjZ9pCSp6WPiStClSs0omVSpNzaeUZdFEXqL0R2K/4sQ1snJCC5TtN 5cc86TV+s6/+59C001Fo9Z1Djunkpjsl3t0FbvF5Njn3Q8gHAUoxWd4oM/fmU069o8VTJFZNdD wk/utj3MQL48r/c7LD9sfWVXASOxYb/UasUb7Iibp8u+IMvqG8MCB1+HIHN0g63xs68yVPGAhV ptArSA6cTzOHktmWFRoyjz8nJ48n/umTa3cVUNBAXwAFmWLGvcJTi+tomFyx4IEqPIN8j3FW7K Ld8=
X-IronPort-AV: E=Sophos;i="5.70,378,1574139600"; d="scan'208";a="524314"
IronPort-PHdr: =?us-ascii?q?9a23=3AqIxyKxLpP0VpTh2gxNmcpTZWNBhigK39O0sv0r?= =?us-ascii?q?FitYgXK/z9rarrMEGX3/hxlliBBdydt6sYzbGI+P+/ESxYuNDd6StEKMQNHz?= =?us-ascii?q?Y+yuwu1zQ6B8CEDUCpZNXLVAcdWPp4aVl+4nugOlJUEsutL3fbo3m18CJAUk?= =?us-ascii?q?6nbVk9Kev6AJPdgNqq3O6u5ZLTfx9IhD2gar9uMRm6twrcutQZjId4JKs8yx?= =?us-ascii?q?TFr3lKdu9LwW9kOU+fkwzz68ut8pNv6Thct+4k+8VdTaj0YqM0QKBCAj87KW?= =?us-ascii?q?41/srrtRfCTQuL+HQRV3gdnwRLDQbY8hz0R4/9vSTmuOVz3imaJtD2QqsvWT?= =?us-ascii?q?u+9adrSQTnhzkBOjUk7WzYkM1wjKZcoBK8uxxyxpPfbY+JOPZieK7WYNUXTn?= =?us-ascii?q?dDUMlMTSxMGoOyYZUSAeodM+hWrIf9qFkPrRSiCgejC/jiyiNRhn/0waE2z/?= =?us-ascii?q?gtHR/A0Qc9H9wOqnPUrNDtOascU+61y63IzTHdYPNQwjjy9pTHchM5rfqRQL?= =?us-ascii?q?x/bc3RyVUzFw/Lk16drpflPzOS1uQJt2iU8exgWvmxhGE7qAF8uSavydk2io?= =?us-ascii?q?nInYIVy1/E9SNjzIkpIt24TVd2bNi5G5VesCGaMpF5QsIkQ2xwpik7xacJuZ?= =?us-ascii?q?ujfCgO1psr3RjfZOKbc4SQ/B3iW/yeITJghHJhZr2znQq98U+lyuHkSMa130?= =?us-ascii?q?xFri9fntbQsXAN0hre4dWERPtl5kqtxCqD2xrO5uxGL004j7fXJp4vz7IqmZ?= =?us-ascii?q?cetVzPEjLqlEnskaObdFko9vK15+noYbjqvIKQOoxshgHwLKsjmdCzDOE9Pw?= =?us-ascii?q?UMQ2eX5f6z2bj+8ULlXLpHi/07nbTHv5DUIMkWorO2DBJL3Ysl9h2xFS2p0M?= =?us-ascii?q?4CknkCNF9FfRWHgJX3NFzWO/D4COu/g0yrkDd22/DKJr3hDYvJLnjEiLrsYK?= =?us-ascii?q?pz5VZBxAUz1d5R6JNbBq0fLP7pRE/+qNvYDgUhMwCu2enoFc9x1p0EWWKUBK?= =?us-ascii?q?+VKr/dsViN5u43IumMYpEauCrlJvQ4+/Lil2I1lF0TcKWzwJcaaH61Eu5pLk?= =?us-ascii?q?ideXbsh80OEWYOvgowVuzqj1iCXCZIZ3ayWKI84jU7B5ygDYjYWI+inL+B0T?= =?us-ascii?q?ylHpJIfGBGC0uMEXbnd4WCQfsDdCWSIsp5njweSbehU5Mh1Q2ptALizrpoNP?= =?us-ascii?q?DU+iwftZ750Nh14OPTlR8o9TNqEsud1HqAT2B1nmMUXTM5wKZ/oVZnxleCza?= =?us-ascii?q?hym+ZYGsBL5/NVTgc6MobRz/ZkBND9RA3AccuJRU2nQtq4HTExQMg9w9gUY0?= =?us-ascii?q?ZySJ2eiUWJ2iOwArhTk7uFCoY5/qX03nntYc170TDHyONp21wvWMpIc2mhiK?= =?us-ascii?q?Bl+gTUL4/IjwOSkbzsdLhKmGaH7mqMwHqSlEBVTAA2Vr/KFzhLfEbZoMTlzk?= =?us-ascii?q?LPU7HoDq4oZFhv08mHf+FqbdntgFNMSfzgfJzlaGWthy34UQ2IwbeIYYzgdm?= =?us-ascii?q?4e9DvQEkkfkg8Vu32BMF5tVW+av2vCAWk2RhrUaET2/LwmpQ=3D=3D?=
X-IPAS-Result: =?us-ascii?q?A2HdAgAAqTFe/zGZrQpmHAEBAQEBBwEBEQEEBAEBgXuDF?= =?us-ascii?q?YExCpUkmzgJAQEBAQEBAQEBBwEbFAEBAoQ+AoJPOBMCAwEBCwEBAQQBAQEBA?= =?us-ascii?q?QUDAQEBAoYgDII7InFEAQEBAQEBAQEBJAEBAQEBASMCDVQzNQEBAQEDOksEA?= =?us-ascii?q?gEIEQQBAR8QMh0IAQEEARIIgx+vLYInhUqEZYE4jDqBQj6EJD6EIxCGBASNO?= =?us-ascii?q?IkbmA92AweCOYdCjm0jg0CXP45gmw0CBAIEBQIVgWmBe3BQgmwJRxgNkhCEW?= =?us-ascii?q?YV6dIwFgTKBEAEB?=
Received: from BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) by BRN1WNEX02.vcorp.ad.vrsn.com (10.173.153.49) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Wed, 29 Jan 2020 10:51:38 -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; Wed, 29 Jan 2020 10:51:38 -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/dHsolAAMLssAAPB6esAAMXbkAAAEsjbg
Date: Wed, 29 Jan 2020 15:51:38 +0000
Message-ID: <852cde22fbf94b03966417cda91a1475@verisign.com>
References: <0d07b9a1683f4389931b2e7864edb14c@verisign.com> <274c0386-1754-8fc8-9e0d-f3a852a43fc1@iit.cnr.it> <4257030f1d8645e39c87ee772ad6a98e@verisign.com> <0867f8a0-fcee-5287-b210-6eeac804f446@iit.cnr.it>
In-Reply-To: <0867f8a0-fcee-5287-b210-6eeac804f446@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/BvUVrzUlU2xNjqTmXBmSJMgLfoc>
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 15:51:50 -0000

> -----Original Message-----
> From: Mario Loffredo <mario.loffredo@iit.cnr.it>
> Sent: Wednesday, January 29, 2020 3:36 AM
> To: Hollenbeck, Scott <shollenbeck@verisign.com>om>; regext@ietf.org
> Subject: [EXTERNAL] Re: [regext] 7482bis: Partial String Search Clarification
>
>
> 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.

I've also made this change in -01.

Scott