Re: [Internetgovtech] Transition to the web

John Curran <jcurran@istaff.org> Tue, 15 July 2014 16:58 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 C9C1C1B28F3 for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 09:58:46 -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 MQrR_baNfurr for <internetgovtech@ietfa.amsl.com>; Tue, 15 Jul 2014 09:58:43 -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 B6F301B28F1 for <internetgovtech@iab.org>; Tue, 15 Jul 2014 09:58:42 -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 1X763s-000Hdb-5o; Tue, 15 Jul 2014 16:58:40 +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: U2FsdGVkX19CEfDaAdAePDUV/S+b6dWC
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: <20140715164338.DD4681F86B4@mail-01-ewr.dyndns.com>
Date: Tue, 15 Jul 2014 12:58:37 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <4341AA4C-33BE-436B-9272-4BD87171A43B@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>
To: JFC Morfin <jefsey@jefsey.com>
X-Mailer: Apple Mail (2.1878.6)
Archived-At: http://mailarchive.ietf.org/arch/msg/internetgovtech/5MgU7-NtMVUdRwUl0zJXMF9siFc
Cc: internetgovtech@iab.org, Miles Fidelman <mfidelman@meetinghouse.net>
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 16:58:47 -0000

On Jul 15, 2014, at 12:40 PM, JFC Morfin <jefsey@jefsey.com> wrote:
> At 16:24 15/07/2014, John Curran wrote:
>> Remember, there is only one DNS root zone (registry) and one IPv4 space and
>> one IPv6 space... each of these registry spaces consist of both technical/
>> specialized entries and "general purpose" entries, but in the end each space
>> must have single consistent registry published containing all entries.  This
>> is particularly important when dealing with non-trivial publications protocols
>> such as DNSSEC.
> 
> What an odd approach to read this as leading in the end at "each space must have single consistent registry published containing all entries" outside of any inter-community agreement.

JFC - We've been here before... My reference (to a single consistent registry
for each space) is with respect to the specific community of users who happen 
to find value in the identifier coordination provided by the "default" registries 
administered by the IANA at behest of the IETF.  Clearly, other communities
can use whatever coordination mechanisms and values they choose (with obvious
interoperability implications for communications between communities...)

I expect most of the readers of this list are interested in the coordination
resulting from these singular IANA registries, as opposed to the frameworks 
for multiple instances of registries with self-organizing communities (but I
easily could be mistaken.)

Thanks!
/John

Disclaimers: My views alone.