IETF Logo Mail Archive

Re: Unicode/UTF-8 issues (was: comments ondraft-ietf-sasl-anon-00)

Alexey Melnikov <mel@messagingdirect.com> Thu, 20 February 2003 19:18 UTC

Received: (from majordomo@localhost) by above.proper.com (8.11.6/8.11.3) id h1KJIsG29250 for ietf-sasl-bks; Thu, 20 Feb 2003 11:18:54 -0800 (PST)
Received: from rembrandt.esys.ca (IDENT:root@rembrandt.esys.ca [198.161.92.131]) by above.proper.com (8.11.6/8.11.3) with ESMTP id h1KJIrd29246 for <ietf-sasl@imc.org>; Thu, 20 Feb 2003 11:18:53 -0800 (PST)
Received: from messagingdirect.com (gagarin.isode.com [193.133.227.138]) (authenticated) by rembrandt.esys.ca (8.11.0.Beta0/8.11.0.Beta0) with ESMTP id h1KJK8x01507; Thu, 20 Feb 2003 12:20:08 -0700
Message-ID: <3E552A0A.AD59C02B@messagingdirect.com>
Date: Thu, 20 Feb 2003 12:18:34 -0700
From: Alexey Melnikov <mel@messagingdirect.com>
Organization: ACI WorldWide / MessagingDirect
X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: "Kurt D. Zeilenga" <Kurt@OpenLDAP.org>
CC: Philip Guenther <guenther@sendmail.com>, ietf-sasl@imc.org
Subject: Re: Unicode/UTF-8 issues (was: comments ondraft-ietf-sasl-anon-00)
References: <5.2.0.9.0.20030220092854.01a0bd18@127.0.0.1> <5.2.0.9.0.20030220103201.01a11718@127.0.0.1>
Content-Type: text/plain; charset="koi8-r"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-sasl@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-sasl/mail-archive/>
List-ID: <ietf-sasl.imc.org>
List-Unsubscribe: <mailto:ietf-sasl-request@imc.org?body=unsubscribe>

> >I believe Philip was referring to ABNF which allows for overlong UTF8
> >sequences.
>
> I gather that you are saying that ABNF is not precise enough.

Correct.

> (please correct me if I wrongly gathered).  While I can
> see that if you ignored all other text and the comments within
> the ABNF, one could presume that the message, in hex, 0C 30
> was valid.... if one actually ignored all the other text
> and the comments they could also presume that the invalid
> messages 00 (in hex), foo"bar"@x (in ASCII), and many others
> were valid.
>
> Obviously, the grammar is not intended to be taken out of
> context.  It is provided as a tool for understanding the
> text of the specification.

I've seen the version of the grammer that deals with overlong sequence.
Check draft-yergeau-rfc2279bis-04.txt section 4.

Regards,
Alexey Melnikov
__________________________________________
R & D, ACI Worldwide/MessagingDirect
Watford, UK

Work Phone: +44 1923 81 2877
Home Page: http://orthanc.ab.ca/mel

I speak for myself only, not for my employer.
__________________________________________

v2.23.0 | Report a Bug | By Email