IETF Logo Mail Archive

Re: [dane] DANE meeting at IETF95 in BA

"John R Levine" <johnl@taugh.com> Tue, 08 March 2016 08:34 UTC

Return-Path: <johnl@taugh.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 6610A12D56A for <dane@ietfa.amsl.com>; Tue, 8 Mar 2016 00:34:10 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level:
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1536-bit key) header.d=iecc.com header.b=DfMMysiT; dkim=pass (1536-bit key) header.d=taugh.com header.b=Av/kTfOO
Received: from mail.ietf.org ([127.0.0.1]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KubnGrf-ZY8V for <dane@ietfa.amsl.com>; Tue, 8 Mar 2016 00:34:09 -0800 (PST)
Received: from miucha.iecc.com (abusenet-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:1126::2]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A1F4E12D55D for <dane@ietf.org>; Tue, 8 Mar 2016 00:34:08 -0800 (PST)
Received: (qmail 53503 invoked from network); 8 Mar 2016 08:34:07 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=iecc.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d0fe.56de8e7f.k1603; bh=7Z7VNl18UThzyjvycBbKL/ueCke33HE0cu1FRMo7rwc=; b=DfMMysiTY0Etv5tpVQl0VgSv1zuRKx0F/PvT3DsH5OE0kY0XMwzZ/oiiJI76ABwDDOBGLqS7UTfmO3GEZ0Cx+n4TA0BRb4kBcqnfiVDUZfz+3KkgbkVIwG8DkBXZ+mHCQbIbAD5IO3NzsHtqD0W+79jCWNnoGGjfIlhhi4yZFInbaken5SXbUYglTndotoNvQQgjyqAvY0lBPvVvIfrD4wFgjX/cns9R7WjK2OBuJCtGhZbmdziTOYQKzMqC+SFH
DKIM-Signature: v=1; a=rsa-sha256; c=simple; d=taugh.com; h=date:message-id:from:to:cc:subject:in-reply-to:references:mime-version:content-type:user-agent; s=d0fe.56de8e7f.k1603; bh=7Z7VNl18UThzyjvycBbKL/ueCke33HE0cu1FRMo7rwc=; b=Av/kTfOO4gPug9CedcEghnD5ls5Gt7n5CCEL9l1kSMW+2Ma/M7ymBrX1nmyWHWDsT467O0TzXeWRBDhchxsnKlFQT8/moaU3/AdwXt/r+tR+9dQljqpEIRoMq86Md+J4KNR7LC1qgmOa4oVBBWNFjn2o+VUfUVbqArvp7WL5EGa1a7k2fgVIdNvT2SoHQnukK/68NaZKO6f8hlXNZrqge0IK4vUIDJ3CUwLr5H1CB1s36bKhUl8vcUfbdSzVtIFd
Received: from localhost ([IPv6:2001:470:1f07:1126::78:696d:6170]) by imap.iecc.com ([IPv6:2001:470:1f07:1126::78:696d:6170]) with ESMTPS (TLS1.0/X.509/SHA1) via TCP6; 08 Mar 2016 08:34:07 -0000
Date: Tue, 08 Mar 2016 09:34:08 +0100
Message-ID: <alpine.OSX.2.11.1603080932201.3525@ary.local>
From: John R Levine <johnl@taugh.com>
To: Sean Leonard <dev+ietf@seantek.com>
In-Reply-To: <56DE6FDC.1060001@seantek.com>
References: <20160307124637.1102.qmail@ary.lan> <56DE6FDC.1060001@seantek.com>
User-Agent: Alpine 2.11 (OSX 23 2013-08-11)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <http://mailarchive.ietf.org/arch/msg/dane/cFEf_IJgYdKqFx2ksaYraeMKUos>
Cc: dane@ietf.org
Subject: Re: [dane] DANE meeting at IETF95 in BA
X-BeenThere: dane@ietf.org
X-Mailman-Version: 2.1.17
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: Tue, 08 Mar 2016 08:34:10 -0000

>> If you meet, I'd like to present draft-bhjl-x509-srv-00 but if you
>> don't meet, that's fine too.
>
> I do not understand what exactly this draft offers over RFC 4387, which 
> already defines the HTTP certificate service, the URI formats, and the SRV 
> records. I get the vague sense that this draft is an alternative to storing 
> individual certificates in the DNS with DANE as draft-ietf-dane-smime-10 
> proposes. (See Section 5 of this draft.)

RFC 4387 is rather vague about how you locate the key server and what URIs 
you use.  This is basically a profile that nails down enough details that 
clients and servers can interoperate.

> That being said, it seems reasonable to present at the DANE meeting, so I 
> support that.

Thanks.

Regards,
John Levine, johnl@taugh.com, Taughannock Networks, Trumansburg NY
Please consider the environment before reading this e-mail.

v2.23.0 | Report a Bug | By Email