Re: Split the IANA functions?
Robert Elz <kre@munnari.OZ.AU> Thu, 09 January 2014 00:11 UTC
Return-Path: <kre@munnari.OZ.AU>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D46D41ADE88 for <ietf@ietfa.amsl.com>; Wed, 8 Jan 2014 16:11:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.333
X-Spam-Level:
X-Spam-Status: No, score=0.333 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HOST_EQ_AU=0.327, HOST_MISMATCH_AU=2.444, RP_MATCHES_RCVD=-0.538] autolearn=no
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 bQV5oJBNhnM1 for <ietf@ietfa.amsl.com>; Wed, 8 Jan 2014 16:11:14 -0800 (PST)
Received: from munnari.OZ.AU (munnari.OZ.AU [202.29.151.3]) by ietfa.amsl.com (Postfix) with ESMTP id 6AC5D1ADE86 for <ietf@ietf.org>; Wed, 8 Jan 2014 16:11:14 -0800 (PST)
Received: from perseus.noi.kre.to (localhost [IPv6:::1]) by munnari.OZ.AU with ESMTP id s0906TYd007938; Thu, 9 Jan 2014 07:06:50 +0700 (ICT)
Received: from perseus.noi.kre.to (localhost [127.0.0.1]) by perseus.noi.kre.to (8.14.7/8.14.2) with ESMTP id s0906M0V023749; Thu, 9 Jan 2014 07:06:23 +0700 (ICT)
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.5
From: Robert Elz <kre@munnari.OZ.AU>
To: manning bill <bmanning@isi.edu>
Subject: Re: Split the IANA functions?
In-Reply-To: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu>
References: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> <CAMm+LwinAb6+7BoMzwBWyu63vofndxK9VY6DSNN0Ykza4SxuMQ@mail.gmail.com> <52CB0010.5010407@gmail.com> <CAMm+LwhN8+z9q4KQXVY9bWA6TAqxx1=Qg0OUfK=VGCSDg5uWEA@mail.gmail.com> <DD618936-0D13-41F1-8D89-2E3171D864B5@istaff.org> <52CB31F4.3090703@cs.tcd.ie> <52CB987A.20300@cisco.com> <20140107144412.GB11068@mx1.yitter.info>
Mime-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Date: Thu, 09 Jan 2014 07:06:22 +0700
Message-ID: <2520.1389225982@perseus.noi.kre.to>
Cc: "ietf@ietf.org Discussion" <ietf@ietf.org>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 09 Jan 2014 00:11:16 -0000
Date: Wed, 8 Jan 2014 13:07:12 -0800 From: manning bill <bmanning@isi.edu> Message-ID: <94F13021-48B9-4CE9-995A-1081DC75A52D@isi.edu> | There can be/ have been multiple roots in the DNS - HOWEVER, there is | a always a single root _per class_. I'm not sure that's correct. Nor do I know it is incorrect. Classes were (and are) so under-specified that exactly how they were intended to work (if there was ever a clear and understood interpretation of that) seems lost in the mists of time. Another interpretation is that classes operate more like BIND's implementation of views - that is allow different data for the same types in the same namespace - except without requiring the server to guess bases on source address of the query which set of data is required. I am not even certain I am convinced whether the set of available types is global, or varies per class, nor whether the same lookup algorithm applies (does A == a in all classes?) Probably, but who knows. But even if you're correct, then conceptually, what is now isi.edu simply becomes isi.edu.internet. (whether actually written that way or not) and then the set of classes would become the "top level domains", and we're back at a single tree, with a single root, that root being a list of all of the classes. There really is no way out of this - people wanting multiple roots really just want to change who controls that rot - usually to someone they consider friendly to themselves (like themselves) rather than someone that they consider the enemy (ietf/iana/icann/...) kre
- Split the IANA functions? Phillip Hallam-Baker
- Re: Split the IANA functions? Brian E Carpenter
- Re: Split the IANA functions? Phillip Hallam-Baker
- Re: Split the IANA functions? John Curran
- Re: Split the IANA functions? Stephen Farrell
- Re: Split the IANA functions? Phillip Hallam-Baker
- RE: Split the IANA functions? l.wood
- Re: Split the IANA functions? Abdussalam Baryun
- Re: Split the IANA functions? John Curran
- Re: Split the IANA functions? John Curran
- Re: Split the IANA functions? Brian E Carpenter
- Re: Split the IANA functions? Eliot Lear
- Re: Split the IANA functions? Dave Crocker
- Re: Split the IANA functions? Abdussalam Baryun
- Re: Split the IANA functions? Phillip Hallam-Baker
- Re: Split the IANA functions? Andrew Sullivan
- Re: Split the IANA functions? Eliot Lear
- Re: Split the IANA functions? Patrik Fältström
- Re: Split the IANA functions? avri doria
- Re: Split the IANA functions? Dave Crocker
- Re: Split the IANA functions? Phillip Hallam-Baker
- Re: Split the IANA functions? Andrew Sullivan
- Re: Split the IANA functions? David Conrad
- Re: Split the IANA functions? Stephen Kent
- DNS heirarchy, multiple roots, etc [was Re: Split… Thomas Narten
- Re: DNS heirarchy, multiple roots, etc [was Re: S… Patrik Fältström
- Re: DNS heirarchy, multiple roots, etc [was Re: S… John C Klensin
- Re: DNS heirarchy, multiple roots, etc [was Re: S… Phillip Hallam-Baker
- Re: DNS heirarchy, multiple roots, etc [was Re: S… Suzanne Woolf
- Re: Split the IANA functions? manning bill
- Re: Split the IANA functions? Andrew Sullivan
- Re: Split the IANA functions? Robert Elz
- DNS design (was: Re: Split the IANA functions?) John C Klensin
- Re: DNS design (was: Re: Split the IANA functions… Phillip Hallam-Baker
- Re: DNS design Eliot Lear
- Multiple Namespaces Re: Split the IANA functions? Olafur Gudmundsson
- Re: DNS design John C Klensin
- Re: Multiple Namespaces Re: Split the IANA functi… Brian E Carpenter
- Re: Multiple Namespaces Re: Split the IANA functi… David Conrad
- Re: Multiple Namespaces Re: Split the IANA functi… Paul Hoffman
- Re: Multiple Namespaces Re: Split the IANA functi… Dave Crocker
- Re: Multiple Namespaces Re: Split the IANA functi… Phillip Hallam-Baker
- Re: DNS design George Michaelson