Re: [precis] Ambiguity in specification of case mapping in RFC 7613 and draft-ietf-precis-nickname

[Tom Worster <[e-mail]>]

On 11/4/15, 10:37 AM, "Peter Saint-Andre" <[e-mail]> wrote:
>
>That may be. We could simply remove the offending sentence:
>
>OLD
>
>    3.  Case Mapping Rule: Unicode Default Case Folding MUST be applied,
>        as defined in the Unicode Standard [Unicode] (at the time of this
>        writing, the algorithm is specified in Chapter 3 of
>        [Unicode7.0]).  The primary result of doing so is that uppercase
>        characters are mapped to lowercase characters.  In applications
>        that prohibit conflicting nicknames, this rule helps to reduce
>        the possibility of confusion by ensuring that nicknames differing
>        only by case (e.g., "stpeter" vs. "StPeter") would not be
>        presented to a human user at the same time.
>
>NEW
>
>
>    3.  Case Mapping Rule: Unicode Default Case Folding MUST be applied,
>        as defined in the Unicode Standard [Unicode] (at the time of this
>        writing, the algorithm is specified in Chapter 3 of
>        [Unicode7.0]).  In applications that prohibit conflicting
>        nicknames, this rule helps to reduce the possibility of
>        confusion by ensuring that nicknames differing only by case
>        (e.g., "stpeter" vs. "StPeter") would not be presented to a
>        human user at the same time.
>
>If we do that, we're no longer dancing around issues.

Splendid idea!

Tom