Re: [dane] Call for Adoption: draft-hoffman-dane-smime.

Richard Barnes <rbarnes@bbn.com> Mon, 24 September 2012 15:06 UTC

Return-Path: <rbarnes@bbn.com>
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 EFDD721F87C4 for <dane@ietfa.amsl.com>; Mon, 24 Sep 2012 08:06:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -107.719
X-Spam-Level:
X-Spam-Status: No, score=-107.719 tagged_above=-999 required=5 tests=[AWL=0.878, BAYES_00=-2.599, GB_I_LETTER=-2, HS_INDEX_PARAM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4, USER_IN_WHITELIST=-100]
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 DSxHk5ZBClMn for <dane@ietfa.amsl.com>; Mon, 24 Sep 2012 08:06:11 -0700 (PDT)
Received: from smtp.bbn.com (smtp.bbn.com [128.33.1.81]) by ietfa.amsl.com (Postfix) with ESMTP id 368E021F87BA for <dane@ietf.org>; Mon, 24 Sep 2012 08:06:11 -0700 (PDT)
Received: from [128.89.253.48] (port=57412) by smtp.bbn.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.77 (FreeBSD)) (envelope-from <rbarnes@bbn.com>) id 1TGAEO-0000rf-Uv; Mon, 24 Sep 2012 11:05:57 -0400
Date: Mon, 24 Sep 2012 17:05:56 +0200
From: Richard Barnes <rbarnes@bbn.com>
To: Paul Wouters <paul@cypherpunks.ca>
Message-ID: <2752740638CF4FA1AA37E7F41A3A9D89@bbn.com>
In-Reply-To: <alpine.LFD.2.02.1209241056440.29827@bofh.nohats.ca>
References: <BCDB44B9-6AB0-4230-B1EF-FDDB37C77F38@kumari.net> <357AB2FD-DF7E-49EC-B3D6-D0F6BC20A79F@kumari.net> <C93F9961257B4ADFA226AD8C89290362@bbn.com> <alpine.LFD.2.02.1209241056440.29827@bofh.nohats.ca>
X-Mailer: sparrow 1.6.3 (build 1172)
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="506076d4_5fb8011c_7b3"
Cc: IETF DANE WG list <dane@ietf.org>
Subject: Re: [dane] Call for Adoption: draft-hoffman-dane-smime.
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: Mon, 24 Sep 2012 15:06:12 -0000

Oh, I'm totally not objecting to the lhs._smimecert.rhs syntax for this use case.  That makes a lot of sense, not least because S/MIME isn't a transport-layer service.  

I was just saying that in general, I don't really see a need for RR types other than TLSA -- especially because protocols can define their own mechanisms for finding TLSA records. 

-- 
Richard Barnes
Sent with Sparrow (http://www.sparrowmailapp.com/?sig)


On Monday, September 24, 2012 at 5:02 PM, Paul Wouters wrote:

> On Mon, 24 Sep 2012, Richard Barnes wrote:
> 
> > -- I don't really see why we need a new RR type here, beyond the cognitive dissonance caused by the three letters "TLS".
> 
> What _port._protocol would one store the SMIME information under?
> 
> If only we had decided not to use protoport prefixing....
> 
> Now we could say, store it _like_ the TLSA record at _smimecert. But
> technically speaking, that is no longer a TLSA record, which
> uses _port._protocol prefixing.
> 
> We'll get more of these type of records, we might as well allocate
> a new RR for this one too.
> 
> Paul