Re: [keyassure] Call for consensus on #17
Warren Kumari <warren@kumari.net> Fri, 11 February 2011 02:14 UTC
Return-Path: <warren@kumari.net>
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 43A5F3A69D3 for <keyassure@core3.amsl.com>; Thu, 10 Feb 2011 18:14:35 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, 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 mk1+kTCxpziE for <keyassure@core3.amsl.com>; Thu, 10 Feb 2011 18:14:34 -0800 (PST)
Received: from vimes.kumari.net (vimes.kumari.net [198.186.192.250]) by core3.amsl.com (Postfix) with ESMTP id 3D7393A69BA for <keyassure@ietf.org>; Thu, 10 Feb 2011 18:14:34 -0800 (PST)
Received: from [10.67.11.82] (64.1.210.2.ptr.us.xo.net [64.1.210.2]) by vimes.kumari.net (Postfix) with ESMTPSA id 99D291B40B76 for <keyassure@ietf.org>; Thu, 10 Feb 2011 21:14:47 -0500 (EST)
Content-Type: text/plain; charset="iso-8859-2"
Mime-Version: 1.0 (Apple Message framework v1081)
From: Warren Kumari <warren@kumari.net>
In-Reply-To: <A55272D7-F8C2-449A-9849-DC31D74B82F1@kumari.net>
Date: Thu, 10 Feb 2011 21:14:46 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <735BEA77-87A6-46CF-86B8-077339D0EBAE@kumari.net>
References: <A4CC96D2-79C9-468D-965C-633C45DAF5F8@kumari.net> <4D42EF85.30004@nic.cz> <87bp31gcvr.fsf@latte.josefsson.org> <4D43079A.20005@vpnc.org> <A55272D7-F8C2-449A-9849-DC31D74B82F1@kumari.net>
To: keyassure@ietf.org
X-Mailer: Apple Mail (2.1081)
Subject: Re: [keyassure] Call for consensus on #17
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: Fri, 11 Feb 2011 02:14:35 -0000
While going through the issue tracker I realized that we hadn't marked this issue as closed. There have been no followups, and so I am officially waving the dead chicken and pulling the big lever marked "Consensus Achieved" -- I know y'all think I just make this stuff up, but I believe in keeping the old traditions alive.... The consensus is, as Ondrej stated: The initial document (draft-ietf-dane-protocol) will support only TLS / DTLS. W On Jan 28, 2011, at 1:26 PM, Warren Kumari wrote: > > On Jan 28, 2011, at 1:14 PM, Paul Hoffman wrote: > >> On 1/28/11 9:24 AM, Simon Josefsson wrote: >>> Ondřej Surý<ondrej.sury@nic.cz> writes: >>> >>>> Hi all, >>>> >>>> upon discussion with my fellow co-chair I hereby call for consensus on >>>> issue #17. >>>> >>>> The consensus would be that the initial document >>>> (draft-ietf-dane-protocol) would support only TLS. >>> >>> Does this exclude DTLS? > > No... Good catch though! > > Apologies for not being clearer -- the document uses the term TLS to refer to both TLS and DTLS, and we have fallen into doing the same thing. > > I have a procmail rule that I pass outgoing mail through that does 'sed/exmaple.com/example.com' on outgoing mail, perhaps I should add 's/TLS/TLS\/DTLS/' :-) > >>> DTLS is not the same protocol as TLS. >> >> DTLS is clearly and completely covered in every WG draft so far. If it is not clear, let the authors know; that would be an error on our part. > > Nope, I believe it is perfectly clear in the doc (clear enough that I automatically see the implied DTLS) > > W >> _______________________________________________ >> keyassure mailing list >> keyassure@ietf.org >> https://www.ietf.org/mailman/listinfo/keyassure >> > > _______________________________________________ > keyassure mailing list > keyassure@ietf.org > https://www.ietf.org/mailman/listinfo/keyassure >
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- [keyassure] Issue #17 - Should draft-ietf-dane-pr… Warren Kumari
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Warren Kumari
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Ilari Liusvaara
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Simon Josefsson
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Hoffman
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… James Cloos
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… James Cloos
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Jakob Schlyter
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Ondřej Surý
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… James Cloos
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Ondřej Surý
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Hoffman
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Warren Kumari
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Simon Josefsson
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Phillip Hallam-Baker
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Hoffman
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Paul Wouters
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… James Cloos
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… James Cloos
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Steingruebl, Andy
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Carl Wallace
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Richard L. Barnes
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Carl Wallace
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Geoff Beier
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Martin Rex
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Warren Kumari
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Warren Kumari
- [keyassure] Call for consensus on #17 (Was: Issue… Ondřej Surý
- Re: [keyassure] Call for consensus on #17 Simon Josefsson
- Re: [keyassure] Call for consensus on #17 Paul Hoffman
- Re: [keyassure] Call for consensus on #17 Warren Kumari
- Re: [keyassure] Call for consensus on #17 Simon Josefsson
- Re: [keyassure] Call for consensus on #17 Warren Kumari
- Re: [keyassure] Issue #17 - Should draft-ietf-dan… Stephen Kent