Re: [Internetgovtech] Transition to the web

John Curran <jcurran@istaff.org> Tue, 15 July 2014 14:47 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 EB20B1B28BF for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 07:47:51 -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 0456Q6Ji3CqZ for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 07:47:30 -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 237001B28CB for <internetgovtech@iab.org>; Tue, 15 Jul 2014 07:44:59 -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 1X73yU-000K3x-Dn; Tue, 15 Jul 2014 14:44:58 +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: U2FsdGVkX1/I0+iDfuQ08Ljz5s0WLst7
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Content-Type: text/plain; charset="us-ascii"
From: John Curran <jcurran@istaff.org>
X-Priority: 1
In-Reply-To: <53C1B2C6.40501@meetinghouse.net>
Date: Tue, 15 Jul 2014 10:44:56 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <0E45CDDF-D741-4538-8CD0-CC0B042F01C1@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>
To: Miles Fidelman <mfidelman@meetinghouse.net>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/9qKwgWZp_C0VUVvv8dpJWsEJKBM
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 14:47:52 -0000

On Jul 12, 2014, at 6:12 PM, Miles Fidelman <mfidelman@meetinghouse.net> wrote:
> 3. IETF's role is defined in the MOU, but seems to be in addition to, and/or enabled by the DOC-ICANN contract.

Oh please...

Thought-exercise: If the IETF were to specify a entirely new naming protocol
or new Internet address protocol (including a new associated registry space),
the protocol specification by the IETF would, upon adoption of the appropriate
IANA Considerations section, cause a registry to come into being.  On day one,
the policy authority for that registry would be the IAB, with the IANA doing 
whatever form of administration was specified in the considerations section.

Now one would hope that if the IETF created a general-purpose registry space
(where pieces where to be eventually assigned to real-world entities rather 
than simply code points) that it would leverage existing organizations which 
strive to represent the affected user communities (e.g. ICANN, RIRs) but such 
delegation is _not_ inevitable.

The registry spaces are _created_ as a result of IETF's adoption of a protocol 
specification, and IETF wisely realizes it should provide for administration 
of same (hence the IANA).   It's probably not worth dwelling on this for the 
existing DNS, IPv4, and IPv6 address spaces, but the IETF's role is fundamental 
to the existence of these registries themselves, and not "in addition to, and/or 
enabled by" NTIA-DoC, ICANN, or any other party.

/John

Disclaimer: My view alone.