Re: rather than argue and bicker about who said what...

Keith Moore <moore@cs.utk.edu> Sat, 18 January 2003 00:23 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h0I0NY502578 for ietf-822-bks; Fri, 17 Jan 2003 16:23:34 -0800 (PST)
Received: from snipe.mail.pas.earthlink.net (snipe.mail.pas.earthlink.net [207.217.120.62]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h0I0NXo02574 for <ietf-822@imc.org>; Fri, 17 Jan 2003 16:23:33 -0800 (PST)
Received: from user-119b1dm.biz.mindspring.com ([66.149.133.182] helo=envy.indecency.org) by snipe.mail.pas.earthlink.net with smtp (Exim 3.33 #1) id 18Zglq-0001SU-00; Fri, 17 Jan 2003 16:23:34 -0800
Date: Fri, 17 Jan 2003 19:20:11 -0500
From: Keith Moore <moore@cs.utk.edu>
To: Russ Allbery <rra@stanford.edu>
Cc: moore@cs.utk.edu, ietf-822@imc.org
Subject: Re: rather than argue and bicker about who said what...
Message-Id: <20030117192011.276d09a2.moore@cs.utk.edu>
In-Reply-To: <yl3cnrz6q1.fsf@windlord.stanford.edu>
References: <20030115141509.249e6d96.moore@cs.utk.edu> <H8tF87.EvM@clw.cs.man.ac.uk> <20030116181613.13bd871d.moore@cs.utk.edu> <yladi0oe6k.fsf@windlord.stanford.edu> <H8uzA0.28@clw.cs.man.ac.uk> <yl3cnrz6q1.fsf@windlord.stanford.edu>
X-Mailer: Sylpheed version 0.8.8claws (GTK+ 1.2.10; i386--netbsdelf)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-822@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-822/mail-archive/>
List-ID: <ietf-822.imc.org>
List-Unsubscribe: <mailto:ietf-822-request@imc.org?body=unsubscribe>

> > That is actually a very good point. There is an expectation, built into
> > NNTP, that users will be able to filter newsgroup-names using "wildmats"
> > (which are a restricted form of regular expression). The draft of the
> > new NNTP standard (draft-ietf-nntpext-base-15.txt) goes to considerable
> > trouble to define wildmats in such a way that they will work with UTF-8.
> 
> Which is an argument in favor of using UTF-8 newsgroup names on the wire
> between news servers, since then a UTF-8-aware wildmat will work as one
> expects.  If newsgroup names are decoded into UTF-8 before matching,
> wildmat matches will always work as expected.

seems like the code needs to be changed either way.  existing expression
matchers seem unlikely to do useful things with utf-8 regardless of whether or
not the utf-8 is encoded as ascii.   for instance, will the * character match
a sequence of octets or a sequence of utf-8 characters?