IETF Logo Mail Archive

Re: [dane] Encoding local parts in better ways

Sean Leonard <dev+ietf@seantek.com> Wed, 14 October 2015 15:11 UTC

Return-Path: <dev+ietf@seantek.com>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7E2681ABD3E for <dane@ietfa.amsl.com>; Wed, 14 Oct 2015 08:11:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level:
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Ptyk2jnq6c_P for <dane@ietfa.amsl.com>; Wed, 14 Oct 2015 08:11:20 -0700 (PDT)
Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 99F811A88D2 for <dane@ietf.org>; Wed, 14 Oct 2015 08:11:07 -0700 (PDT)
Received: from [192.168.123.105] (unknown [75.83.2.34]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id 79DD0509BE; Wed, 14 Oct 2015 11:11:04 -0400 (EDT)
Content-Type: multipart/signed; boundary="Apple-Mail=_6043BBBC-9830-4255-87C9-A2CFE4402F66"; protocol="application/pkcs7-signature"; micalg="sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <D243D61B.1C562%gwiley@verisign.com>
Date: Wed, 14 Oct 2015 08:10:03 -0700
Message-Id: <41654219-9895-465D-B17A-C35CD16224D4@seantek.com>
References: <20150921035448.5523.qmail@ary.lan> <D243D61B.1C562%gwiley@verisign.com>
To: "Wiley, Glen" <gwiley@verisign.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/h8YDD10RGbbcYB0Of6NfWL7Hw2M>
Cc: "dane@ietf.org" <dane@ietf.org>
Subject: Re: [dane] Encoding local parts in better ways
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DNS-based Authentication of Named Entities <dane.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dane>, <mailto:dane-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dane/>
List-Post: <mailto:dane@ietf.org>
List-Help: <mailto:dane-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dane>, <mailto:dane-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 14 Oct 2015 15:11:21 -0000

On Oct 14, 2015, at 6:59 AM, Wiley, Glen <gwiley@verisign.com> wrote:

> John,
> 
> I read the draft.
> 
> In the list of approaches you include literal, encoded, regex and pointer
> but I didn¹t see a place to refer to hashes (such as SHA224).  While there
> are different views on the use of hashes for local parts, would it makes
> sense to allow for the future use of a hash?

Probably makes sense conceptually as a sub-part of “encoded” (Section 4). Some encodings are reversible (e.g., base32); others are one-way (e.g., CRC); yet others are one-way and also collision-resistant (e.g., SHA-224). The commonality that they share is that they preserve the byte-for-byte/case-sensitive matching of SMTP.

Sean

v2.23.0 | Report a Bug | By Email