Re: [domainrep] WGLC: draft-ietf-repute-email-identifiers-04

"David F. Skoll" <dfs@roaringpenguin.com> Thu, 15 November 2012 19:20 UTC

Return-Path: <dfs@roaringpenguin.com>
X-Original-To: domainrep@ietfa.amsl.com
Delivered-To: domainrep@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 368B921F85E3 for <domainrep@ietfa.amsl.com>; Thu, 15 Nov 2012 11:20:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xyc6AF3la8eI for <domainrep@ietfa.amsl.com>; Thu, 15 Nov 2012 11:20:54 -0800 (PST)
Received: from colo3.roaringpenguin.com (www.ipv6.roaringpenguin.com [IPv6:2607:f748:1200:fb:70:38:112:54]) by ietfa.amsl.com (Postfix) with ESMTP id 25CA921F841D for <domainrep@ietf.org>; Thu, 15 Nov 2012 11:20:48 -0800 (PST)
Received: from vanadium.roaringpenguin.com ([192.168.10.23]) by colo3.roaringpenguin.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id qAFJKjC7023475; Thu, 15 Nov 2012 14:20:45 -0500
Received: from hydrogen.roaringpenguin.com (dfs@hydrogen.roaringpenguin.com [192.168.10.1]) by vanadium.roaringpenguin.com (8.14.3/8.14.3/Debian-9.4) with ESMTP id qAFJKinp003872 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Thu, 15 Nov 2012 14:20:44 -0500
Date: Thu, 15 Nov 2012 14:20:44 -0500
From: "David F. Skoll" <dfs@roaringpenguin.com>
To: "Murray S. Kucherawy" <superuser@gmail.com>
Message-ID: <20121115142044.61478035@hydrogen.roaringpenguin.com>
In-Reply-To: <CAL0qLwZy5kSaBHrBAqfMffWS99GsLjysgOqoN5AN8AwwpPaXCQ@mail.gmail.com>
References: <509C24FC.8090107@gmail.com> <20121114074216.GB2357@x28.adm.denic.de> <CAL0qLwZPL1FYZ_9g3eh8UY=Pc7sk62qVXOEvoDLAD3RR-R5eqg@mail.gmail.com> <CAL0qLwYGSBhEgTmkxLU3m4u23=udEaZW83CxKbzN5B1m_d+-7g@mail.gmail.com> <831693C2CDA2E849A7D7A712B24E257F0D6B17EE@BRN1WNEXMBX01.vcorp.ad.vrsn.com> <CAL0qLwZy5kSaBHrBAqfMffWS99GsLjysgOqoN5AN8AwwpPaXCQ@mail.gmail.com>
Organization: Roaring Penguin Software Inc.
X-Mailer: Claws Mail 3.7.6 (GTK+ 2.20.1; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=roaringpenguin.com; h=date :from:to:cc:subject:message-id:in-reply-to:references :mime-version:content-type:content-transfer-encoding; s=main; bh=XLzYAIy71YQfAw/+6zIx6vkj4vs=; b=E638sj6FpEhIcN2gKXx0MUDNMMlr 3ARV5gBH9M1BV7dETeIW0I5jznugV3+eKh8gjAIGNGWCtr5RSgG94DvUzHrPDfIU 0PmkOSe+ERpeVrkCpYc7o1DF+CQtLeBmx2TVW0DGGtVBIw1HngyZXq2joPIfuXB7 JhiwzshyyC9HHr5/cojxNRcDKtA1wlhVQd8W8FrLmYwr2WdldorxKOypCIGOI+Kh ok6CO+AKO6bgQ/sk47+IXtghMsNl4CawXKjZckD+ScsO0xpx2ReYFLEDdUAeeBge kGW9eLNE9l7RMGZpql2rJ8MqirhWYuCOG1zhzc1iw+8a1YpILecbAoGgGQ==
X-Scanned-By: CanIt (www . roaringpenguin . com)
X-Scanned-By: MIMEDefang 2.73 on 192.168.10.23
X-CanIt-Geo: No geolocation information available for 192.168.10.23
X-CanItPRO-Stream: outgoing (inherits from default)
X-CanIt-Archive-Cluster: SQVyZJxqklY5buiWXYCN4T/BjiM
X-CanIt-Archived-As: base/20121115 / 01InTkJ7E
Cc: "domainrep@ietf.org" <domainrep@ietf.org>
Subject: Re: [domainrep] WGLC: draft-ietf-repute-email-identifiers-04
X-BeenThere: domainrep@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Domain Reputation discussion list <domainrep.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/domainrep>, <mailto:domainrep-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/domainrep>
List-Post: <mailto:domainrep@ietf.org>
List-Help: <mailto:domainrep-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/domainrep>, <mailto:domainrep-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 15 Nov 2012 19:20:55 -0000

On Thu, 15 Nov 2012 10:41:31 -0800
"Murray S. Kucherawy" <superuser@gmail.com> wrote:

> My own reading (RFC4627) is that the key in a JSON object is Unicode,
> but it says nothing about case sensitivity.

Well, here's one specification that uses JSON:
http://www.jsonrpc.org/specification

and it says: "All member names exchanged between the Client and the
Server that are considered for matching of any kind should be
considered to be case-sensitive."

> The question before us, then, is whether we need to say we expect
> matching to be case-sensitive, since RFC4627 is (perhaps
> deliberately) ambiguous.

I prefer case-sensitivity because it narrows the acceptable range
of inputs.

Regards,

David.