Re: [BEHAVE] RFC3489bis-07 now available

Rémi Denis-Courmont <remi.denis-courmont@nokia.com> Wed, 18 July 2007 06:46 UTC

Return-path: <behave-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB3IS-000475-E6; Wed, 18 Jul 2007 02:46:04 -0400
Received: from behave by megatron.ietf.org with local (Exim 4.43) id 1IB3IN-0003wh-9k for behave-confirm+ok@megatron.ietf.org; Wed, 18 Jul 2007 02:45:59 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IB3IJ-0003kV-KA for behave@ietf.org; Wed, 18 Jul 2007 02:45:55 -0400
Received: from smtp.nokia.com ([131.228.20.170] helo=mgw-ext11.nokia.com) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IB3IJ-0005Ic-5d for behave@ietf.org; Wed, 18 Jul 2007 02:45:55 -0400
Received: from esebh106.NOE.Nokia.com (esebh106.ntc.nokia.com [172.21.138.213]) by mgw-ext11.nokia.com (Switch-3.2.5/Switch-3.2.5) with ESMTP id l6I6jd0r015626; Wed, 18 Jul 2007 09:45:50 +0300
Received: from esebh104.NOE.Nokia.com ([172.21.143.34]) by esebh106.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 09:45:49 +0300
Received: from esebh102.NOE.Nokia.com ([172.21.138.183]) by esebh104.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 09:45:49 +0300
Received: from esdhcp05132.research.nokia.com ([172.21.51.32]) by esebh102.NOE.Nokia.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 18 Jul 2007 09:45:48 +0300
From: Rémi Denis-Courmont <remi.denis-courmont@nokia.com>
Organization: Nokia TP-SP-SWD
To: ext Philip Matthews <philip_matthews@magma.ca>, Behave WG <behave@ietf.org>, ext Jonathan Rosenberg <jdrosen@cisco.com>, Dan Wing <dwing@cisco.com>
Subject: Re: [BEHAVE] RFC3489bis-07 now available
Date: Wed, 18 Jul 2007 09:45:45 +0300
User-Agent: KMail/1.9.6
References: <46929E54.50301@cisco.com> <200707171542.19726.remi.denis-courmont@nokia.com> <E8FCAF25-FD6E-4878-B32D-EB730B9CE195@magma.ca>
In-Reply-To: <E8FCAF25-FD6E-4878-B32D-EB730B9CE195@magma.ca>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
Message-Id: <200707180945.46590.remi.denis-courmont@nokia.com>
X-OriginalArrivalTime: 18 Jul 2007 06:45:48.0799 (UTC) FILETIME=[467E60F0:01C7C907]
X-Nokia-AV: Clean
X-Spam-Score: 0.0 (/)
X-Scan-Signature: ea4ac80f790299f943f0a53be7e1a21a
Cc:
X-BeenThere: behave@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: mailing list of BEHAVE IETF WG <behave.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/behave>
List-Post: <mailto:behave@ietf.org>
List-Help: <mailto:behave-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/behave>, <mailto:behave-request@ietf.org?subject=subscribe>
Errors-To: behave-bounces@ietf.org

On Tuesday 17 July 2007 21:24:30 you wrote:
> >> * defined length limits on all free-form fields
> >
> > That's really appreciable! But but, the limit should most likely be
> > expressed
> > in bytes rather than in characters. Otherwise, it is pretty
> > ambiguous whether
> > the limit is in code points or bytes.
>
> I don't  really see this.
> For the username, it says
>     It MUST contain a
>     UTF-8 encoded sequence of less than 128 characters.
> How is this ambiguous?

To re-iterate the question, does "character" mean "code point" or "byte"? It 
is totally ambiguous.

To me, a UTF-8 encoded sequence of less than 128 characters is up to 
(128-1)*6+1=763 bytes, counting the terminating nul (and that's a bit big, 
IMHO). To most implementors it's going to be 127(+1) bytes.

I would much rather have:

	It MUST contain a valid UTF-8 encoded sequence of less than 128 bytes.

-- 
Rémi Denis-Courmont


_______________________________________________
Behave mailing list
Behave@ietf.org
https://www1.ietf.org/mailman/listinfo/behave