Re: [Internetgovtech] Transition to the web

John Curran <jcurran@istaff.org> Tue, 15 July 2014 17:52 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 A71AB1A0AE1 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 10:52:58 -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 Fxgviv_qH5F6 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 10:52:57 -0700 (PDT)
Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47E3A1A0AD9 for <internetgovtech@iab.org>; Tue, 15 Jul 2014 10:52:57 -0700 (PDT)
Received: from pool-108-56-179-253.washdc.fios.verizon.net ([108.56.179.253] helo=[192.168.1.7]) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.72) (envelope-from <jcurran@istaff.org>) id 1X76uO-000Kkl-Ip; Tue, 15 Jul 2014 17:52:56 +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: U2FsdGVkX18xLgvZcdjBbwSUSqwvbMiV
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
From: John Curran <jcurran@istaff.org>
In-Reply-To: <A0AE8C76-1FF5-4B67-8F0D-D27E2FAE7927@standardstrack.com>
Date: Tue, 15 Jul 2014 13:52:54 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E0A3629-062E-4BF2-8987-B5E549CE2F3F@istaff.org>
References: <6.2.5.6.2.20140708142055.0d5fbb78@elandnews.com> <D1AC4482BED7C04DAC43491E9A9DBEC3998608C6@BK-EXCHMBX01.blacknight.local> <20140709161653.GM59034@mx1.yitter.info> <9B506E73B33873103AE5EC52@JcK-HP8200.jck.com> <20140709171401.GB2935@mx1.yitter.info> <53BD843F.1070304@cs.tcd.ie> <53BD84BB.7000002@meetinghouse.net> <53BDA867.7090701@gmail.com> <53BE602F.7020108@firsthand.net> <53BE6384.5030504@cs.tcd.ie> <53BE69D2.9070509@firsthand.net> <6.2.5.6.2.20140711000259.0cc016e8@resistor.net> <53BFD828.3070007@firsthand.net> <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> <53C1E977.4050306@meetinghouse.net> <C2727BEC-6E3A-45E7-A3C2-DD4A6F118ED9@istaff.org> <20140715164338.DD4681F86B4@mail-01-ewr.dyndns.com> <"4341AA4C-33BE-436B-9272 - 4BD87171A43B"@istaff.org> <A0AE8C76-1FF5-4B67-8F0D-D27E2FAE7927@standardstrack.com>
To: Eric Burger <eburger@standardstrack.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/RTMD6CI6uV7Ld0hjCgm8Ey4GRI8
Cc: internetgovtech@iab.org
Subject: Re: [Internetgovtech] Transition to the web
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 17:52:58 -0000

On Jul 15, 2014, at 1:33 PM, Eric Burger <eburger@standardstrack.com> wrote:

> If the proposal is to have gobs of new registries, that’s a bad idea. Been there and luckily not too much bad happened, but one can envision how lots of badness can happen in the future.
> 
> However, if the proposal is to have gobs of redundant, distributed, cryptographically secure (meaning compromise is obvious) of an allocation data base, that is an excellent idea. BitCoin works without a centralized data base, so we have existence proofs, too. I vaguely recall something about “working code” and the IETF…
> 
> That could work for IP address allocation, which would admittedly be a less than ideal situation for the RIR’s businesses. For this scheme to work for the parameters directory, we would need a technology such that only the IETF Trust (as holder of the copyright) could update it. I really do not see it working for the DNS root zone, because what goes in, and what does not go in, is a matter of politics, not a matter of a sufficient number of uncompromised nodes agreeing on what a value is.

There's no reason for the IETF shouldn't explore new and innovative
mechanisms for identifier coordination, as long as the resulting 
identifiers are useful to the affected community (remember that one 
side effect of the current mechanisms is some degree of routing 
aggregation for routine cases.)  If a better mechanism comes along, 
the affected community is very likely figure out how to fund it 
one way or the other.

(However, I think much of the present IANA Stewardship discussion 
should be focused on how to keep the current IANA model running in 
a proposed post-NTIA world, since there's quite a bit of real-world
reliance on it today)

/John

Disclaimer: My views alone.