Re: [DNSOP] Pity (was Re: Expiration impending: <draft-jabley-dnssec-trust-anchor-11.txt>)

Paul Vixie <paul@redbarn.org> Fri, 09 October 2015 19:25 UTC

Return-Path: <paul@redbarn.org>
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 303A31B4BBF for <dnsop@ietfa.amsl.com>; Fri, 9 Oct 2015 12:25:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.012
X-Spam-Level:
X-Spam-Status: No, score=-0.012 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] 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 SjvHBz2BFTf5 for <dnsop@ietfa.amsl.com>; Fri, 9 Oct 2015 12:25:31 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 11E551B4BBE for <dnsop@ietf.org>; Fri, 9 Oct 2015 12:25:31 -0700 (PDT)
Received: from [IPv6:2001:559:8000:cb:256a:7041:ae78:55eb] (unknown [IPv6:2001:559:8000:cb:256a:7041:ae78:55eb]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id E909213B5B for <dnsop@ietf.org>; Fri, 9 Oct 2015 19:25:30 +0000 (UTC)
Message-ID: <561814A6.3040703@redbarn.org>
Date: Fri, 09 Oct 2015 12:25:26 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 4.0.5 (Windows/20150923)
MIME-Version: 1.0
To: dnsop@ietf.org
References: <20151009011039.36478.qmail@ary.lan> <90410066-79B0-4DDE-89F7-CE2BB5DA2307@karoshi.com> <E6CCA2DC-7EA6-40BC-BBFE-EAE3505589A3@hopcount.ca> <790654E4-3EF8-44B3-BD92-638EACA0959A@karoshi.com> <F5A8CCB7-5E1C-4547-AD55-1EDE286E59C7@hopcount.ca> <20151009191327.GL20427@mx2.yitter.info>
In-Reply-To: <20151009191327.GL20427@mx2.yitter.info>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="ISO-8859-1"
Content-Transfer-Encoding: 7bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/hqtgPb2b_rw7eyu3W3wuEtUDDNA>
Subject: Re: [DNSOP] Pity (was Re: Expiration impending: <draft-jabley-dnssec-trust-anchor-11.txt>)
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: <https://mailarchive.ietf.org/arch/browse/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: Fri, 09 Oct 2015 19:25:33 -0000


Andrew Sullivan wrote:
> ...
>
> For whatever it's worth, I think this outcome shows that the IETF is no longer able to take uncontroversial descriptions of what people are doing them and process them with anything like the dispatch they deserve. I think that's unfortunate and is another symptom of the IETF losing its relevance to the wider Internet, which is just going to go off without us if we cannot handle what is happening there.

if i had sought IETF help with DLV, we might have a problem statement
final draft by now, instead we're finally killing it having learned
everything and done everything we needed to learn and do.

when david ulevitch created the "afasterinternet.com" web site i thought
he was just being cheeky. no longer. he needed client-subnet for his
business, that year, not this year. i didn't and still don't like that
protocol and i fear its long term implications, but i understand why he
did it the way he did it.

those of you who witnessed the failed DNS MODA effort, or the successful
RRL or RPZ efforts, now know my thinking.

when randy bush started referring to IETF as the IVTF (V = Vendor), i
thought he was just being cranky. no longer.

internet protocol development should look nothing like today's IETF or
today's W3C, and instead become like the XMPP Standards Foundation
(https://en.wikipedia.org/wiki/XMPP_Standards_Foundation).

some soul-searching may be required. "stop helping me so hard, damn it."

-- 
Paul Vixie