Re: [precis] some open issues

Peter Saint-Andre <stpeter@stpeter.im> Wed, 07 March 2012 21:15 UTC

Return-Path: <stpeter@stpeter.im>
X-Original-To: precis@ietfa.amsl.com
Delivered-To: precis@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FE0521F84FE for <precis@ietfa.amsl.com>; Wed, 7 Mar 2012 13:15:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.675
X-Spam-Level:
X-Spam-Status: No, score=-102.675 tagged_above=-999 required=5 tests=[AWL=-0.076, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id S8MrlsKpXtgd for <precis@ietfa.amsl.com>; Wed, 7 Mar 2012 13:15:12 -0800 (PST)
Received: from stpeter.im (mailhost.stpeter.im [207.210.219.225]) by ietfa.amsl.com (Postfix) with ESMTP id 00C3021F84D6 for <precis@ietf.org>; Wed, 7 Mar 2012 13:15:12 -0800 (PST)
Received: from squire.local (unknown [72.163.0.129]) (Authenticated sender: stpeter) by stpeter.im (Postfix) with ESMTPSA id 0781F40058; Wed, 7 Mar 2012 14:27:11 -0700 (MST)
Message-ID: <4F57CFDE.9040701@stpeter.im>
Date: Wed, 07 Mar 2012 14:15:10 -0700
From: Peter Saint-Andre <stpeter@stpeter.im>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:10.0.2) Gecko/20120216 Thunderbird/10.0.2
MIME-Version: 1.0
To: Andrew Sullivan <ajs@anvilwalrusden.com>
References: <4F54EB17.3010208@stpeter.im> <20120305171157.GO76465@mail.yitter.info> <4F57CB29.7070208@stpeter.im> <20120307210024.GV79276@mail.yitter.info>
In-Reply-To: <20120307210024.GV79276@mail.yitter.info>
X-Enigmail-Version: 1.3.5
OpenPGP: url=https://stpeter.im/stpeter.asc
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
Cc: precis@ietf.org
Subject: Re: [precis] some open issues
X-BeenThere: precis@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Preparation and Comparison of Internationalized Strings <precis.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/precis>, <mailto:precis-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/precis>
List-Post: <mailto:precis@ietf.org>
List-Help: <mailto:precis-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/precis>, <mailto:precis-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Mar 2012 21:15:13 -0000

On 3/7/12 2:00 PM, Andrew Sullivan wrote:
> On Wed, Mar 07, 2012 at 01:55:05PM -0700, Peter Saint-Andre wrote:
> 
>>>> The problem statement document mentions the need to specify whether an
>>>> application protocol preserves case. However, the framework document
>>>> does not require profile documents to specify whether they preserve
>>>> case, nor does it provide guidelines or mechanisms for doing so.
>>>
>>> This came up more than once in discussion, however, so I presume
>>> people still think it's important.
>>
>> Right. The question is whether we need a way to signal that somehow
>> (ick) or whether, as Joe says, we can leave it up to entities which
>> function as "registrars" in a given application protocol.
> 
> Well, the reason for it is, I guess, obvious; but in case anyone
> hasn't been following: a lot of protocols have the idea of
> case-insensitive matching.  This is trivial in ASCII and at least hard
> in everything else.  If case is never preserved, then we don't have to
> worry about it.  If case is preserved but also relevant for matching,
> then we don't actually need to worry about it either.  But if case is
> preserved but matching is supposed to be case-insensitive, then
> everything hurts.  I'm ok with punting this to the individual
> protocols, but I think at the very least we need to explain in some
> detail why they need to make a decision (and maybe suggest what it
> ought to be).

Yes, that seems quite reasonable.

Peter

-- 
Peter Saint-Andre
https://stpeter.im/