IETF Logo Mail Archive

Re: Multiple Namespaces Re: Split the IANA functions?

Brian E Carpenter <brian.e.carpenter@gmail.com> Thu, 09 January 2014 19:13 UTC

Return-Path: <brian.e.carpenter@gmail.com>
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 E20A21ADFB2 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2014 11:13:47 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, SPF_PASS=-0.001] 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 0FFSG6Q79LUy for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2014 11:13:46 -0800 (PST)
Received: from mail-pa0-x22f.google.com (mail-pa0-x22f.google.com [IPv6:2607:f8b0:400e:c03::22f]) by ietfa.amsl.com (Postfix) with ESMTP id 6B0361AE005 for <ietf@ietf.org>; Thu, 9 Jan 2014 11:13:46 -0800 (PST)
Received: by mail-pa0-f47.google.com with SMTP id kq14so3681606pab.34 for <ietf@ietf.org>; Thu, 09 Jan 2014 11:13:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=IL2PsBQkGvqe52h2FaNovcmNUA7gVggGrTcXaR1JG9Q=; b=mQ4wRx0R1vnPbKj56umVPiARJnnBnihkFcCNheCaCKsAec5/XTC7K1PviMaqS1nYvK yzgpobsvgGZtKcvButkfagXb/7hweVY+pUnGQe5BTbX4GC2kFpyRzjg89L+URwiJ/SJ7 dEmZdWNoIJdo5G4ka6EWrSxnFpcIIOBEKsuLDm6wVzLRNRmAuwESWdWX3hBhtJBQmDd3 0NZDWdGf4piV4XRoaubwpsA2Xo6layLhuU7jxgWq4VHTRxYHdzFarkhLEqVr/pILoaRT rU5x8C8ZvQo9e0YhamuoSwKClQwlOOjtlvAhU1LSe1R4KuqX6jjU35OjAFI/mUyfSVEQ DfWA==
X-Received: by 10.68.211.102 with SMTP id nb6mr5712301pbc.39.1389294816865; Thu, 09 Jan 2014 11:13:36 -0800 (PST)
Received: from [192.168.178.21] (164.199.69.111.dynamic.snap.net.nz. [111.69.199.164]) by mx.google.com with ESMTPSA id ns7sm1542415pbc.32.2014.01.09.11.13.34 for <multiple recipients> (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 09 Jan 2014 11:13:36 -0800 (PST)
Message-ID: <52CEF4E9.1070505@gmail.com>
Date: Fri, 10 Jan 2014 08:13:45 +1300
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
User-Agent: Thunderbird 2.0.0.6 (Windows/20070728)
MIME-Version: 1.0
To: Olafur Gudmundsson <ogud@ogud.com>
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
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> <2520.1389225982@perseus.noi.kre.to> <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com>
In-Reply-To: <03224C28-8623-41FE-839F-A544D174DDB3@ogud.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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 19:13:48 -0000

> Working out a timeline to complete an effort to make all of this work is left as an exercise to the reader

Since it's an infinite regression (any N namespaces can be converted to a single
namespace by adding N unique suffixes or prefixes) I think the timescale
is infinite.

Seriously. We have a perfectly fine unambiguous namespace. Enough already.

   Brian

v2.23.0 | Report a Bug | By Email