Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
Paul Vixie <paul@redbarn.org> Tue, 26 May 2015 22:33 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 A7B0D1B32C7 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:33:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.511
X-Spam-Level:
X-Spam-Status: No, score=-0.511 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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 m42fZfMCsbBq for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:33:53 -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 2466D1B323B for <dnsop@ietf.org>; Tue, 26 May 2015 15:33:53 -0700 (PDT)
Received: from [172.16.35.163] (unknown [109.235.242.75]) (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 BB04318725; Tue, 26 May 2015 22:33:51 +0000 (UTC)
Message-ID: <5564F4CC.50805@redbarn.org>
Date: Tue, 26 May 2015 15:33:48 -0700
From: Paul Vixie <paul@redbarn.org>
User-Agent: Postbox 3.0.11 (Windows/20140602)
MIME-Version: 1.0
To: Francisco Obispo <fobispo@uniregistry.com>
References: <20150526200703.15413.qmail@ary.lan> <3B05F60A-8865-45B8-A36C-042E0F5CC92C@uniregistry.com> <alpine.OSX.2.11.1505261730060.65578@ary.lan> <CEA65A4A-1AE4-4582-8EF2-732DEEED8D70@uniregistry.com> <alpine.OSX.2.11.1505261753230.65578@ary.lan> <77464DBE-7F4F-478F-9035-E9B2044D6D2D@uniregistry.com>
In-Reply-To: <77464DBE-7F4F-478F-9035-E9B2044D6D2D@uniregistry.com>
X-Enigmail-Version: 1.2.3
Content-Type: text/plain; charset="windows-1252"
Content-Transfer-Encoding: 8bit
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/4JUSaS3NejjgpNGRz7Qboaz0Wvs>
Cc: dnsop@ietf.org, John R Levine <johnl@taugh.com>
Subject: Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps
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, 26 May 2015 22:33:54 -0000
Francisco Obispo wrote: > >> On May 26, 2015, at 2:53 PM, John R Levine <johnl@taugh.com >> <mailto:johnl@taugh.com>> wrote: >> >> Interisle's report. There's a link to it about three messages back. > > Which is my point. > > We are making tons of assertions from 1 DITL window, making > assumptions about how the Internet works with just a slice of the puzzle. > > We now know that the major “risks” identified did not occur in > practice (at least for other TLDs), if something stops working, most > likely someone (tech) will realize they made a mistake, fix it and > move on. francisco, i object, and i also disagree. i object, because as a tld registry, you are making a self-interested argument here. i'd prefer you to find someone who makes no money when a new TLD is allocated and get them to carry this torch. as a senior member of the uniregistry technical staff, you have a conflict of interest. as my friend, you have extremely high standards of personal behaviour. i also disagree. people don't know when something stops working, it just makes their experience worse and they don't know why. the most likely outcome is they'll just live in digital squalor. DITL happens to be representative. (you've operated f-root; you know what the root servers see.) my take on the data is, .HOME, .CORP, and .LOCAL are poisoned for all time, no further discussion needed. to the extent that the new gTLD programme has any public benefit purpose, that purpose must be balanced with digital public safety. if there's a risk, then the risk is too high, because if there's a benefit, the benefit is too low. -- Paul Vixie
- [DNSOP] followup and proposed actions: RFC 6761 i… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… Warren Kumari
- Re: [DNSOP] followup and proposed actions: RFC 67… Daniel Kahn Gillmor
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Tom Ritter
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… John R Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Francisco Obispo
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Wouters
- [DNSOP] dotless names (was Re: followup and propo… David Conrad
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] followup and proposed actions: RFC 67… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… Paul Vixie
- Re: [DNSOP] dotless names (was Re: followup and p… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Jim Reid
- Re: [DNSOP] dotless names (was Re: followup and p… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Patrik Fältström
- Re: [DNSOP] followup and proposed actions: RFC 67… Suzanne Woolf
- Re: [DNSOP] followup and proposed actions: RFC 67… Bob Harold
- Re: [DNSOP] followup and proposed actions: RFC 67… John Levine
- Re: [DNSOP] followup and proposed actions: RFC 67… Mark Andrews
- Re: [DNSOP] followup and proposed actions: RFC 67… Lyman Chapin
- Re: [DNSOP] followup and proposed actions: RFC 67… Rubens Kuhl
- Re: [DNSOP] followup and proposed actions: RFC 67… Andrew Sullivan