Re: [dnsext] getting people to use new RRTYPEs

Ted Lemon <Ted.Lemon@nominum.com> Fri, 26 April 2013 11:11 UTC

Return-Path: <Ted.Lemon@nominum.com>
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 B03D521F9876 for <dnsext@ietfa.amsl.com>; Fri, 26 Apr 2013 04:11:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -105.733
X-Spam-Level:
X-Spam-Status: No, score=-105.733 tagged_above=-999 required=5 tests=[AWL=0.866, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, 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 dwoocZdPa92q for <dnsext@ietfa.amsl.com>; Fri, 26 Apr 2013 04:11:59 -0700 (PDT)
Received: from exprod7og125.obsmtp.com (exprod7og125.obsmtp.com [64.18.2.28]) by ietfa.amsl.com (Postfix) with ESMTP id AE85921F9822 for <dnsext@ietf.org>; Fri, 26 Apr 2013 04:11:58 -0700 (PDT)
Received: from shell-too.nominum.com ([64.89.228.229]) (using TLSv1) by exprod7ob125.postini.com ([64.18.6.12]) with SMTP ID DSNKUXpg/jUyKp3MLTIy7gMGvzDDMhFepr9B@postini.com; Fri, 26 Apr 2013 04:11:58 PDT
Received: from archivist.nominum.com (archivist.nominum.com [64.89.228.108]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by shell-too.nominum.com (Postfix) with ESMTP id D49AE1B80DF for <dnsext@ietf.org>; Fri, 26 Apr 2013 04:11:57 -0700 (PDT)
Received: from webmail.nominum.com (cas-02.win.nominum.com [64.89.228.132]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (Client CN "mail.nominum.com", Issuer "Go Daddy Secure Certification Authority" (verified OK)) by archivist.nominum.com (Postfix) with ESMTPS id CC44E190061; Fri, 26 Apr 2013 04:11:57 -0700 (PDT) (envelope-from Ted.Lemon@nominum.com)
Received: from MBX-01.WIN.NOMINUM.COM ([64.89.228.133]) by CAS-02.WIN.NOMINUM.COM ([64.89.228.132]) with mapi id 14.02.0318.004; Fri, 26 Apr 2013 04:11:57 -0700
From: Ted Lemon <Ted.Lemon@nominum.com>
To: Jim Reid <jim@rfc1035.com>
Thread-Topic: [dnsext] getting people to use new RRTYPEs
Thread-Index: AQHOQgAKmbqqIBDfGUqSx8JOnKnZJZjnqx42gADTHICAAAbzgIAAC0YAgAA+nwA=
Date: Fri, 26 Apr 2013 11:11:56 +0000
Message-ID: <8D23D4052ABE7A4490E77B1A012B63077515F6C4@mbx-01.win.nominum.com>
References: <alpine.BSF.2.00.1304251758160.66546@joyce.lan> <20130426004632.B5E1E32FAF70@drugs.dv.isc.org> <9A4E511F-92E1-4286-AD91-4E438C821774@rfc1035.com> <517A22FF.2090309@bogus.com> <077D73D9-1E5F-431C-95D4-1D01D49853DC@rfc1035.com>
In-Reply-To: <077D73D9-1E5F-431C-95D4-1D01D49853DC@rfc1035.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [192.168.1.10]
Content-Type: text/plain; charset="Windows-1252"
Content-ID: <F02894D838DF724C91BE65732128D83D@nominum.com>
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Cc: "<dnsext@ietf.org>" <dnsext@ietf.org>
Subject: Re: [dnsext] getting people to use new RRTYPEs
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>
X-List-Received-Date: Fri, 26 Apr 2013 11:12:00 -0000

On Apr 26, 2013, at 3:27 AM, Jim Reid <jim@rfc1035.com> wrote:
> Fine. However the latter is more visible => creating the perception that getting type codes is "hard".

<no hat>

I think that if you want to get a document through the IETF, and you say "oh, but I don't want to do that bit, because it's too hard," then you are really being unreasonable.   During the worst period of "new RRtype resistance" about a decade ago, I and several others managed to get a new RRtype through the intarea DNS working group.   We did get yelled at, but we persisted, and we got the result we wanted.

This is how the IETF works.   You are watching sausage being made: it isn't pretty.   No amount of public shaming is going to change this: the current conversation is an existence proof, since this sort of shaming has been going on as long as I've been participating, and the mailing list still has threads like the EUI64 thread.   This is what it means to say anyone can participate.

If you want to get work through the IETF, you have to be brave, because you will—you must—draw criticism.   And you don't get to say "I want to get my work through the IETF, but I'd like to skip that bit of the process because those guys are hard to deal with, please."

All of this is completely independent of the debate that's going on here about SPF; my point is simply that if you aren't willing to engage in debate in the IETF, you are probably in the wrong IETF.