Re: [dane] How should draft-hoffman-dane-smime be written?

Wes Hardaker <wes@hardakers.net> Fri, 07 September 2012 21:44 UTC

Return-Path: <wes@hardakers.net>
X-Original-To: dane@ietfa.amsl.com
Delivered-To: dane@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A9C4121F85B1 for <dane@ietfa.amsl.com>; Fri, 7 Sep 2012 14:44:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, NO_RELAYS=-0.001]
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 YwZaOgzVzfmi for <dane@ietfa.amsl.com>; Fri, 7 Sep 2012 14:44:06 -0700 (PDT)
Received: from mail.hardakers.net (dawn.hardakers.net [IPv6:2001:470:1f00:187::1]) by ietfa.amsl.com (Postfix) with ESMTP id F3EB521F85AE for <dane@ietf.org>; Fri, 7 Sep 2012 14:44:05 -0700 (PDT)
Received: from localhost (wjhw.hardakers.net [IPv6:2001:470:1f00:187:62d8:19ff:fed4:c8b6]) by mail.hardakers.net (Postfix) with ESMTPSA id 89A0B63F; Fri, 7 Sep 2012 14:44:03 -0700 (PDT)
From: Wes Hardaker <wes@hardakers.net>
To: Paul Wouters <paul@cypherpunks.ca>
References: <403225CD-5DE7-4D49-9B75-C74C11EA5B63@vpnc.org> <alpine.LFD.2.02.1209051941220.28517@bofh.nohats.ca>
Date: Fri, 07 Sep 2012 14:44:03 -0700
In-Reply-To: <alpine.LFD.2.02.1209051941220.28517@bofh.nohats.ca> (Paul Wouters's message of "Wed, 5 Sep 2012 19:46:05 -0400 (EDT)")
Message-ID: <0lipbp8q58.fsf@wjh.hardakers.net>
User-Agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/23.3 (gnu/linux)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, IETF DANE WG list <dane@ietf.org>
Subject: Re: [dane] How should draft-hoffman-dane-smime be written?
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.12
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: <http://www.ietf.org/mail-archive/web/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: Fri, 07 Sep 2012 21:44:06 -0000

Paul Wouters <paul@cypherpunks.ca> writes:

>> 2.  Copy structure of DANE-for-TLS RFC and point to it but don’t copy much
>> 3.  Say “we assume you read and understood DANE-for-TLS, and here
>> are the relevant differences”
>
> 3 preferred, 2 okay.

Ditto.  In some ways I worry about this becoming a repeating problem (I
think it will) and it would have made more sense to split the TLSA
document into logical pieces so you could say things like "go read this
and then apply these minor twiddles", and have the 'this' not be another
protocol-specific document like it is with TLSA.  So, you might think
that I'm thinking the right thing to do is 

  4. publish the TLSA document again in a multi-document, split-up
     fashion so it's more reusable.

But I don't think it's worth the work, so 3 is likely better.

-- 
Wes Hardaker                                     
My Pictures:  http://capturedonearth.com/
My Thoughts:  http://pontifications.hardakers.net/