Re: [keyassure] draft-ietf-dane-protocol
Paul Hoffman <paul.hoffman@vpnc.org> Wed, 19 January 2011 02:01 UTC
Return-Path: <paul.hoffman@vpnc.org>
X-Original-To: keyassure@core3.amsl.com
Delivered-To: keyassure@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0C7E73A708F for <keyassure@core3.amsl.com>; Tue, 18 Jan 2011 18:01:50 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.723
X-Spam-Level:
X-Spam-Status: No, score=-101.723 tagged_above=-999 required=5 tests=[AWL=0.323, BAYES_00=-2.599, HELO_MISMATCH_COM=0.553, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Mddfs5fElVzE for <keyassure@core3.amsl.com>; Tue, 18 Jan 2011 18:01:49 -0800 (PST)
Received: from hoffman.proper.com (Hoffman.Proper.COM [207.182.41.81]) by core3.amsl.com (Postfix) with ESMTP id 349103A703F for <keyassure@ietf.org>; Tue, 18 Jan 2011 18:01:49 -0800 (PST)
Received: from MacBook-08.local (75-101-30-90.dsl.dynamic.sonic.net [75.101.30.90]) (authenticated bits=0) by hoffman.proper.com (8.14.4/8.14.3) with ESMTP id p0J24RV6068607 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for <keyassure@ietf.org>; Tue, 18 Jan 2011 19:04:27 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Message-ID: <4D3646AA.8060106@vpnc.org>
Date: Tue, 18 Jan 2011 18:04:26 -0800
From: Paul Hoffman <paul.hoffman@vpnc.org>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7
MIME-Version: 1.0
To: keyassure@ietf.org
References: <F9645C67-A75B-4306-8165-FA1EF858D476@princeton.edu>
In-Reply-To: <F9645C67-A75B-4306-8165-FA1EF858D476@princeton.edu>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Subject: Re: [keyassure] draft-ietf-dane-protocol
X-BeenThere: keyassure@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Key Assurance With DNSSEC <keyassure.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/keyassure>
List-Post: <mailto:keyassure@ietf.org>
List-Help: <mailto:keyassure-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/keyassure>, <mailto:keyassure-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 19 Jan 2011 02:01:50 -0000
On 1/18/11 5:28 PM, Steve Schultze wrote: > I'm in favor of a version of Matt's text in section 3.0: > > http://www.ietf.org/mail-archive/web/keyassure/current/msg00923.html > > Any reason why that's not a good idea? We have so far chosen not to get into any nuts-and-bolts of DNSSEC checking, and this would send us far down that path. It is a big step, and we should consider it carefully. FWIW, I think we should take that step because we have gotten no support from the DNSEXT WG on last-mile DNSSEC, but I know others here don't agree. > I'm not totally sure whether > the text should go into the intro to section 3 or in 3.1. I'm not > really a fan of the "The preceding paragraph is probably wrong" > parenthetical in 3.1. Nor are Jakob and I, of course. But early honesty helps shine a spotlight on places that need work.
- [keyassure] draft-ietf-dane-protocol Steve Schultze
- Re: [keyassure] draft-ietf-dane-protocol Paul Hoffman