IETF Logo Mail Archive

Re: [Internetgovtech] Contracts, what problems we are solving

John Curran <jcurran@istaff.org> Tue, 15 July 2014 23:59 UTC

Return-Path: <jcurran@istaff.org>
X-Original-To: internetgovtech@ietfa.amsl.com
Delivered-To: internetgovtech@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 414E51A01C1 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 16:59:25 -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, RCVD_IN_DNSWL_NONE=-0.0001] 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 j_xZraDqA3hS for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 16:59:23 -0700 (PDT)
Received: from mho-01-ewr.mailhop.org (mho-03-ewr.mailhop.org [204.13.248.66]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A74601A01BE for <internetgovtech@iab.org>; Tue, 15 Jul 2014 16:59:23 -0700 (PDT)
Received: from pool-108-56-179-253.washdc.fios.verizon.net ([108.56.179.253] helo=[192.168.1.7]) by mho-01-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1X7Cd0-0007AN-UV; Tue, 15 Jul 2014 23:59:23 +0000
X-Mail-Handler: Dyn Standard SMTP by Dyn
X-Originating-IP: 108.56.179.253
X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information)
X-MHO-User: U2FsdGVkX182dkg8IRTMZX30bFNSvQpm
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <53C5B8E0.4030505@abenaki.wabanaki.net>
Date: Tue, 15 Jul 2014 19:59:19 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <5BDD502D-3902-4B57-874F-2D8CFB257E18@istaff.org>
References: <53C06E7C.4010903@gmail.com> <CAD_dc6ihUvV8SDkmoc3fGHWoOoR6nFhRz-=tgCjKnuNvRO2JXw@mail.gmail.com> <53C0F1D9.3090400@cisco.com> <53C17B5C.4090600@abenaki.wabanaki.net> <C5750A628D4D973F3C44F6DC@JcK-HP8200.jck.com> <53C1B2C6.40501@meetinghouse.net> <72F8472D-2913-4BEC-9260-6DAC7791BBF8@virtualized.org> <53C1DD6C.8030501@gmail.com> <43DD1894-54A8-44D0-AE58-6F3D395F43DD@ericsson.com> <53C4000C.4030401@dcrocker.net> <20140715142048.GE8847@mx1.yitter.info> <6.2.5.6.2.20140715100237.08757120@resistor.net> <CEC25F70-D126-488A-8BC7-1629598D3956@shinkuro.com> <EEC016BC-49F3-43AD-8B52-5E2A7B0F9C29@istaff.org> <53C5B8E0.4030505@abenaki.wabanaki.net>
To: Eric Brunner-Williams <ebw@abenaki.wabanaki.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/9BeBJ0Zb41NAPXlg7fjMeAWSOWQ
Cc: internetgovtech@iab.org
Subject: Re: [Internetgovtech] Contracts, what problems we are solving
X-BeenThere: internetgovtech@iab.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Internet Governance and IETF technical work <internetgovtech.iab.org>
List-Unsubscribe: <https://www.iab.org/mailman/options/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=unsubscribe>
List-Archive: <http://www.iab.org/mail-archive/web/internetgovtech/>
List-Post: <mailto:internetgovtech@iab.org>
List-Help: <mailto:internetgovtech-request@iab.org?subject=help>
List-Subscribe: <https://www.iab.org/mailman/listinfo/internetgovtech>, <mailto:internetgovtech-request@iab.org?subject=subscribe>
X-List-Received-Date: Tue, 15 Jul 2014 23:59:25 -0000

On Jul 15, 2014, at 7:27 PM, Eric Brunner-Williams <ebw@abenaki.wabanaki.net> wrote:

> On 7/15/14 12:10 PM, John Curran wrote:
>> While I seriously doubt such a change would be prudent from an overall Internet
>> stability perspective ...
> 
> See below.

Actually, there are much more relevant transitions that have already been
successfully accomplished for various portions of this space [SRI->GSI/NSI,
NSI->ARIN, DDN/ISI->ICANN, ARIN->ICANN], and yes, the Internet continued
throughout.  The fact that we can transition providers for these services
still does not mean we should do so without good cause.

FYI,
/John

Disclaimer: My views alone.

v2.23.0 | Report a Bug | By Email