Re: [Json] String comparisons -- LAST CHANCE ON PROPOSALS

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 11 June 2013 22:37 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5F9D21F9A6F for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 15:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -11.599
X-Spam-Level:
X-Spam-Status: No, score=-11.599 tagged_above=-999 required=5 tests=[AWL=1.000, BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_HI=-8]
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 P3q7xVCcTj3T for <json@ietfa.amsl.com>; Tue, 11 Jun 2013 15:37:39 -0700 (PDT)
Received: from rcdn-iport-8.cisco.com (rcdn-iport-8.cisco.com [173.37.86.79]) by ietfa.amsl.com (Postfix) with ESMTP id 0E19521F99D8 for <json@ietf.org>; Tue, 11 Jun 2013 15:37:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=834; q=dns/txt; s=iport; t=1370990259; x=1372199859; h=from:to:subject:date:message-id:in-reply-to:content-id: content-transfer-encoding:mime-version; bh=JuoEoNCpafjMza7344RCsoHq7fdG2y8uegxPi0a8BN4=; b=a84biXGkNpp2RQ1uGeH/QpjeLhm6I0WXuEt1v9ELpo+0wxL2E9dT7WLo EvDT9f62oWP8E9vDslRFtc6MziKat2oErqFrTDmFHuRi+3eLKwte3/dAG O/g30eILSP1xuUQ0XkE0QQn0jWd/0+vWzcfDsNL2DFv2eHVUQ5Q1ARC2s I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: AmcFAO+lt1GtJXHB/2dsb2JhbABZgwl5gi1Hu1oNdBZ0giUBBCMRVwEIGgIGIAIEMBUQAgQBEgiIBahqSpB0gSaNWziCTDNhA6kCgw+CJw
X-IronPort-AV: E=Sophos;i="4.87,847,1363132800"; d="scan'208";a="221620356"
Received: from rcdn-core2-6.cisco.com ([173.37.113.193]) by rcdn-iport-8.cisco.com with ESMTP; 11 Jun 2013 22:37:38 +0000
Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core2-6.cisco.com (8.14.5/8.14.5) with ESMTP id r5BMbc2K025252 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 11 Jun 2013 22:37:38 GMT
Received: from xmb-rcd-x10.cisco.com ([169.254.15.56]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.02.0318.004; Tue, 11 Jun 2013 17:37:38 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Thread-Topic: [Json] String comparisons -- LAST CHANCE ON PROPOSALS
Thread-Index: AQHOZstdmr5W5m3hD0WXxrQEky05Y5kxCi+A
Date: Tue, 11 Jun 2013 22:37:37 +0000
Message-ID: <A723FC6ECC552A4D8C8249D9E07425A70FC40C50@xmb-rcd-x10.cisco.com>
In-Reply-To: <0FBD58CE-748D-419A-8578-CCBF3FDF97CE@vpnc.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/14.3.4.130416
x-originating-ip: [64.101.72.72]
Content-Type: text/plain; charset="utf-8"
Content-ID: <385E544C4028B84C9F048A7DB045F771@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Subject: Re: [Json] String comparisons -- LAST CHANCE ON PROPOSALS
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 11 Jun 2013 22:37:45 -0000

On 6/11/13 11:44 AM, "Paul Hoffman" <paul.hoffman@vpnc.org> wrote:

>For example, the following four keys MUST be considered equivalent:
>
>* "\u002F"
>* "\u002f"
>* "\/"
>* "/"

I'd like to suggest adding some names that are not equivalent as well,
like:

"\u212B" (ANGSTROM SIGN: Å)
"\u00C5" (LATIN CAPITAL LETTER A WITH RING ABOVE: Å)
"A\u030A" (LATIN CAPITAL LETTER A, COMBINING RING ABOVE: Å)
"\u00E5" (LATIN SMALL LETTER A WITH RING ABOVE, å)

and if we could put *&!@# non-ASCII7 characters in an RFC, that would
actually make sense to the reader.

-- 
Joe Hildebrand