IETF Logo Mail Archive

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

Dave Crocker <dcrocker@gmail.com> Thu, 15 November 2012 20:01 UTC

Return-Path: <dcrocker@gmail.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 460BB21F8487 for <domainrep@ietfa.amsl.com>; Thu, 15 Nov 2012 12:01:56 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.75
X-Spam-Level:
X-Spam-Status: No, score=-1.75 tagged_above=-999 required=5 tests=[AWL=0.206, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, RCVD_IN_NJABL_PROXY=1.643]
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 QtAYkqdMSFOO for <domainrep@ietfa.amsl.com>; Thu, 15 Nov 2012 12:01:55 -0800 (PST)
Received: from mail-pb0-f44.google.com (mail-pb0-f44.google.com [209.85.160.44]) by ietfa.amsl.com (Postfix) with ESMTP id 60ADF21F8A52 for <domainrep@ietf.org>; Thu, 15 Nov 2012 12:01:37 -0800 (PST)
Received: by mail-pb0-f44.google.com with SMTP id uo1so1411439pbc.31 for <domainrep@ietf.org>; Thu, 15 Nov 2012 12:01:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=rlKOecY8zhjTl/Wn3qTBGWueFlP+I6hpMytGaH8Q4gc=; b=AKGSSX9I8qrxa4puQOiPa9ZpXeBHdVPmdzA76HpguGFc48WOd1czHZLswfJLfe8uZL ZkDk4hKz/GvJcO+z4QyaVy49PZcfmz75GH3iEYNehYBA17KpreSaLR4tHAQyQEUoDJU7 j4WmbYi7hKp0/nRfPELR+vlBeSH8lBpaX0xtawvvTGL+8pisWFG3HYNrg3EHy4FRMEY1 pKvUW/MH3OJqZC/k9JVGRFItQh0Lce7s3iPu7O4FxuihfQcutMmTvbQDyrKjYvnIgf58 OtWAWrrvGeRaKrvQSD8MaoL1coBfDhyoHCWI4WYTxBSk53jedSWB6vXvM/g3fsK4gMwM O3tg==
Received: by 10.66.73.132 with SMTP id l4mr6219194pav.48.1353009697184; Thu, 15 Nov 2012 12:01:37 -0800 (PST)
Received: from [192.168.1.6] (adsl-67-127-56-94.dsl.pltn13.pacbell.net. [67.127.56.94]) by mx.google.com with ESMTPS id ue7sm9963617pbc.53.2012.11.15.12.01.35 (version=SSLv3 cipher=OTHER); Thu, 15 Nov 2012 12:01:36 -0800 (PST)
Message-ID: <50A54A17.1090400@gmail.com>
Date: Thu, 15 Nov 2012 12:01:27 -0800
From: Dave Crocker <dcrocker@gmail.com>
Organization: Brandenburg InternetWorking
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:16.0) Gecko/20121026 Thunderbird/16.0.2
MIME-Version: 1.0
To: "David F. Skoll" <dfs@roaringpenguin.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> <20121115142044.61478035@hydrogen.roaringpenguin.com>
In-Reply-To: <20121115142044.61478035@hydrogen.roaringpenguin.com>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
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 20:01:56 -0000

On 11/15/2012 11:20 AM, David F. Skoll wrote:
> I prefer case-sensitivity because it narrows the acceptable range
> of inputs.


and it increases the source of human errors.


in any event:

    1. If we can document standard practice for json, then that's the 
practice we should use.

    2. Whatever the choice, it needs to be explicit in our docs.  Don't 
rely on assumptions about the infrastructure (json, or whatever.)

d/

-- 
  Dave Crocker
  bbiw.net

v2.15.0 | Report a Bug | By Email