IETF Logo Mail Archive

Re: [DNSOP] followup and proposed actions: RFC 6761 interim and next steps

Francisco Obispo <fobispo@uniregistry.com> Tue, 26 May 2015 22:00 UTC

Return-Path: <fobispo@uniregistry.com>
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 D86CD1B3222 for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:00:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_PASS=-0.001, T_REMOTE_IMAGE=0.01, 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 THEElGo7aPmc for <dnsop@ietfa.amsl.com>; Tue, 26 May 2015 15:00:00 -0700 (PDT)
Received: from zimbra1.uniregistry.com (zimbra1.uniregistry.com [162.221.214.42]) by ietfa.amsl.com (Postfix) with ESMTP id C096F1A8AF8 for <dnsop@ietf.org>; Tue, 26 May 2015 14:59:59 -0700 (PDT)
Received: from zimbra1.uniregistry.com (localhost [127.0.0.1]) by zimbra1.uniregistry.com (Postfix) with ESMTP id 9BB57327BBB; Tue, 26 May 2015 21:59:57 +0000 (UTC)
Received: from zimbra1.uniregistry.com (localhost [127.0.0.1]) by zimbra1.uniregistry.com (Postfix) with ESMTP id 8FFD1327BCE; Tue, 26 May 2015 21:59:57 +0000 (UTC)
Received: from [64.96.164.20] (unknown [64.96.164.20]) by zimbra1.uniregistry.com (Postfix) with ESMTPSA id E0A3D327BBB; Tue, 26 May 2015 21:59:56 +0000 (UTC)
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2098\))
Content-Type: multipart/signed; boundary="Apple-Mail=_6B8CAD99-EE5B-409A-B9D2-AEFD82944774"; protocol="application/pgp-signature"; micalg="pgp-sha256"
X-Pgp-Agent: GPGMail 2.5b6
From: Francisco Obispo <fobispo@uniregistry.com>
In-Reply-To: <alpine.OSX.2.11.1505261753230.65578@ary.lan>
Date: Tue, 26 May 2015 14:59:54 -0700
Message-Id: <77464DBE-7F4F-478F-9035-E9B2044D6D2D@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>
To: John R Levine <johnl@taugh.com>
X-Mailer: Apple Mail (2.2098)
Archived-At: <http://mailarchive.ietf.org/arch/msg/dnsop/zcSXx1bzOVN_Lc-g4km_bP9kuFQ>
Cc: dnsop@ietf.org
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:00:02 -0000

> On May 26, 2015, at 2:53 PM, John R Levine <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 Obispo
CTO - Registry Operations
____________________________

 <http://www.uniregistry.com/>
2161 San Joaquin Hills Road
Newport Beach, CA 92660

Office +1 949 706 2300 x4202
fobispo@uniregistry.link

v2.23.0 | Report a Bug | By Email