Re: [dnsext] [dane] TLSA == RRtype 52

Paul Hoffman <paul.hoffman@vpnc.org> Mon, 16 April 2012 21:55 UTC

Return-Path: <dnsext-bounces@ietf.org>
X-Original-To: namedroppers-archive-gleetwall6@lists.ietf.org
Delivered-To: ietfarch-namedroppers-archive-gleetwall6@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0658011E809C; Mon, 16 Apr 2012 14:55:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1334613357; bh=xEPx/ZXJ1kKgZnWg+AD/kFMhIp8h1z5XylIOnwPDmAo=; h=Mime-Version:From:In-Reply-To:Date:Message-Id:References:To: Subject:List-Id:List-Unsubscribe:List-Archive:List-Post:List-Help: List-Subscribe:Content-Type:Content-Transfer-Encoding:Sender; b=uW3pz4dW+0t/2AF0ndhDt7GGpC+/rsxaZrbFvUtNnjhR73FoaY7GURfS7A3XgnH4y e23UNe6lyc/OC9s4qzgY0tjvtWHA5UN3n1Y8mFfbyv8pWQ427A1mTc6WTuoPij1JNy 35BGUZmbJmBfU0elryCnKtHtsmBGq+mAfjGAmYLo=
X-Original-To: dnsext@ietfa.amsl.com
Delivered-To: dnsext@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F04711E809C for <dnsext@ietfa.amsl.com>; Mon, 16 Apr 2012 14:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.558
X-Spam-Level:
X-Spam-Status: No, score=-102.558 tagged_above=-999 required=5 tests=[AWL=0.041, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id m8TRfkNEpsuZ for <dnsext@ietfa.amsl.com>; Mon, 16 Apr 2012 14:55:54 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 7F06211E807F for <dnsext@ietf.org>; Mon, 16 Apr 2012 14:55:54 -0700 (PDT)
Received: from [10.20.30.103] (50-0-66-4.dsl.dynamic.fusionbroadband.com [50.0.66.4]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.3) with ESMTP id q3GLtr5Q045413 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <dnsext@ietf.org>; Mon, 16 Apr 2012 14:55:53 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Mime-Version: 1.0 (Apple Message framework v1257)
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <20120416195934.GM49880@mail.yitter.info>
Date: Mon, 16 Apr 2012 14:55:53 -0700
Message-Id: <0F55A6EF-643F-4145-A54F-5D85D415C7A2@vpnc.org>
References: <201204121730.q3CHUZcF021835@new.toad.com> <20120412215921.GP74554@registro.br> <4F889C4E.3050001@ogud.com> <8A01597C-D02E-4279-B755-E12CC6137EA2@vpnc.org> <4F896E48.10204@ogud.com> <811782ED-AF00-4D84-9341-1FCB3DFACE0E@vpnc.org> <4F8C3E23.4050201@ogud.com> <20120416164009.GE49880@mail.yitter.info> <4F8C71E6.1010103@ogud.com> <20120416195934.GM49880@mail.yitter.info>
To: DNSEXT Working Group <dnsext@ietf.org>
X-Mailer: Apple Mail (2.1257)
Subject: Re: [dnsext] [dane] TLSA == RRtype 52
X-BeenThere: dnsext@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: DNS Extensions working group discussion list <dnsext.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsext>, <mailto:dnsext-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsext>
List-Post: <mailto:dnsext@ietf.org>
List-Help: <mailto:dnsext-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsext>, <mailto:dnsext-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: dnsext-bounces@ietf.org
Errors-To: dnsext-bounces@ietf.org

> On Mon, Apr 16, 2012 at 03:24:22PM -0400, Olafur Gudmundsson wrote:
>> But the application in this case referenced a particular version of an
>> Internet draft:

We applied in good faith, assuming that our application was for the protocol, not a single draft. If the DNSEXT WG chairs felt that we should wait until the draft could not have any wire changes, the DNSEXT WG chairs should have told us that at the time of the application.

The registration at IANA does not name the draft; it lists the name for the DANE WG chair who applied for code point. A sensible interpretation of that is "the person who is named gets to decide what the code point means", not "go ask that person which draft he applied for". If given a choice between what one co-chair and IANA thinks, versus the other co-chair, I hope most people pick the former.

This would not be an issue if a DNSEXT co-chair (Olafur) had not exhorted people to implement using the assigned code point even though the spec is not stable. In that message, he (wisely) did not say "implement only the -18 draft, and we might screw you over later if the spec changes". Most developers care about implementing a stable spec. The spec will be stable when the IESG sends it to the RFC Editor, hopefully in a few weeks. If a developer wants, they can use the code point now; nothing stops them other than the desire to ship stable code.

--Paul Hoffman

_______________________________________________
dnsext mailing list
dnsext@ietf.org
https://www.ietf.org/mailman/listinfo/dnsext