Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)

Joe Abley <jabley@hopcount.ca> Tue, 18 February 2014 18:58 UTC

Return-Path: <jabley@hopcount.ca>
X-Original-To: dnsop@ietfa.amsl.com
Delivered-To: dnsop@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EF3C81A0513 for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:15 -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
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id R4e4dKT1G2Pd for <dnsop@ietfa.amsl.com>; Tue, 18 Feb 2014 10:58:14 -0800 (PST)
Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) by ietfa.amsl.com (Postfix) with ESMTP id 0F70C1A03ED for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:58:14 -0800 (PST)
Received: by mail-ie0-f171.google.com with SMTP id to1so2245114ieb.2 for <dnsop@ietf.org>; Tue, 18 Feb 2014 10:58:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hopcount.ca; s=google; h=content-type:mime-version:subject:from:in-reply-to:date:cc :message-id:references:to; bh=K/bftl5+AQ1F1sI+gAf6UzOxnmw+0E+slIQG3Nd4754=; b=DUIIgQw2vi1xRVoLKUQk13XJtcagwlMheVosQ6LItlNBS5/h48fOeb/JIkv9gGHT/h EhEJRd2WmAZ+wddDPQW1qKJj9R4q27aeQrTLjRbdXT/bAR8bW5C07Uqqv1OQ0pK6b+l4 5CXF4S6ok6+PFyhAURr6je5p1Yc4TwJ7enx2k=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:message-id:references:to; bh=K/bftl5+AQ1F1sI+gAf6UzOxnmw+0E+slIQG3Nd4754=; b=VYoph9uw1rI8hu60DlZsI6oGVWYbaitUxzQQ5cbVIpp/AaETrst53z6GwU0UnLuthd a1oyAgoqppoAsRxkIRlaEyrCFf6jsh/P1XmaenR1Ozk7md9/RfO5uLPiNr/1LpKgcEVJ CgpMy3S1wY0KXvTrzp97oYewSPwshUBJHjbVR/MA7TnDYZReVCm1oq11UVovkrEEccXl SQQyIjhgmPG3n3e5sAljBflaVjgrevfkS1q4v26KcgpHZzOLDHV8CRo1wl+taDhjrTnX aELSY+eBXwYpgOrr8Un0WhwBPrfcgQOXhFF991GtZmCFYodygIOKH8tXtc80aTwG80lZ rqlQ==
X-Gm-Message-State: ALoCoQnz7mF44RDyahAhPi1zbOOZ0vuYHbZddxh/ht/a7nwR3wDKV+K/JxpiI5pBpjU7HM3QqRRL
X-Received: by 10.50.132.66 with SMTP id os2mr23212994igb.33.1392749891021; Tue, 18 Feb 2014 10:58:11 -0800 (PST)
Received: from ?IPv6:2001:4900:1042:1:2866:4c7e:3e97:d8b7? ([2001:4900:1042:1:2866:4c7e:3e97:d8b7]) by mx.google.com with ESMTPSA id rj10sm42745127igc.8.2014.02.18.10.58.09 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 18 Feb 2014 10:58:09 -0800 (PST)
Content-Type: multipart/signed; boundary="Apple-Mail=_0422C840-287E-4372-A36E-162DDEB7D20C"; protocol="application/pgp-signature"; micalg=pgp-sha1
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
From: Joe Abley <jabley@hopcount.ca>
In-Reply-To: <6.2.5.6.2.20140218074550.0c380cc8@resistor.net>
Date: Tue, 18 Feb 2014 13:58:08 -0500
Message-Id: <5B5AE40C-6D26-419C-A16A-392AF2C33446@hopcount.ca>
References: <CAESS1RPh+UK+r=JzZ9nE_DUqcvNtZiS6TNt1CDN-C0uiU7HP=A@mail.gmail.com> <52FEF407.30405@redbarn.org> <20140215140133.GA6990@sources.org> <alpine.LFD.2.10.1402151449280.23619@bofh.nohats.ca> <D82F49E8-9A06-4F52-8E3E-DF5C8D0B7549@virtualized.org> <53006595.5010207@frobbit.se> <6.2.5.6.2.20140218074550.0c380cc8@resistor.net>
To: SM <sm@resistor.net>
X-Mailer: Apple Mail (2.1827)
Archived-At: http://mailarchive.ietf.org/arch/msg/dnsop/a_uRkmyA681WSrrbNhmrI9u-5b4
Cc: dnsop <dnsop@ietf.org>, Paul Wouters <paul@nohats.ca>, David Conrad <drc@virtualized.org>
Subject: Re: [DNSOP] meta issue: WG to discuss DNS innovation (was Re: draft-hzhwm-start-tls-for-dns-00)
X-BeenThere: dnsop@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <dnsop.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dnsop>, <mailto:dnsop-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/dnsop/>
List-Post: <mailto:dnsop@ietf.org>
List-Help: <mailto:dnsop-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dnsop>, <mailto:dnsop-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 18 Feb 2014 18:58:16 -0000

On 2014-02-18, at 10:54, SM <sm@resistor.net>; wrote:

> Seriously, it may take some effort to get things deployed but that is not an insurmountable task [1].  One of the problems is that there isn't any money in doing that.
> 
> [...]
> 
> 1. I actually looked into it some time back. 

I had some experience with this recently with the document that became RFC 7043.

Code-point assignment was swift. Implementation in major nameservers was swift (although one or two of them left the types commented out in the source until the RFC was published). The RFC publication process was not arduous, even given the privacy concerns with this particular proposal.

I appreciate that knowing the process made things easier (mainly; I was wrong about some things and had to be educated). But I would not describe the process as difficult, and certainly not insurmountable.


Joe