IETF Logo Mail Archive

Re: Multiple Namespaces Re: Split the IANA functions?

David Conrad <drc@virtualized.org> Thu, 09 January 2014 19:41 UTC

Return-Path: <drc@virtualized.org>
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 A40581AE542 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2014 11:41:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.44
X-Spam-Level:
X-Spam-Status: No, score=-2.44 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.538, SPF_HELO_PASS=-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 yAclPcVBtzl8 for <ietf@ietfa.amsl.com>; Thu, 9 Jan 2014 11:41:08 -0800 (PST)
Received: from alpha.virtualized.org (alpha.virtualized.org [199.233.229.186]) by ietfa.amsl.com (Postfix) with ESMTP id EA53A1AE541 for <ietf@ietf.org>; Thu, 9 Jan 2014 11:41:05 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by alpha.virtualized.org (Postfix) with ESMTP id 0B3C284B42; Thu, 9 Jan 2014 14:40:55 -0500 (EST)
Received: from alpha.virtualized.org ([127.0.0.1]) by localhost (alpha.virtualized.org [127.0.0.1]) (maiad, port 10024) with ESMTP id 28278-04; Thu, 9 Jan 2014 14:40:54 -0500 (EST)
Received: from [10.0.1.6] (c-24-4-109-25.hsd1.ca.comcast.net [24.4.109.25]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: drc@virtualized.org) by alpha.virtualized.org (Postfix) with ESMTPSA id 29DC78445C; Thu, 9 Jan 2014 14:40:53 -0500 (EST)
Content-Type: multipart/signed; boundary="Apple-Mail=_282946E1-63F1-446F-AE57-C72AE4EBC395"; protocol="application/pgp-signature"; micalg="pgp-sha1"
Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\))
Subject: Re: Multiple Namespaces Re: Split the IANA functions?
From: David Conrad <drc@virtualized.org>
In-Reply-To: <52CEF4E9.1070505@gmail.com>
Date: Thu, 09 Jan 2014 11:40:52 -0800
Message-Id: <87AA61A3-DC75-44AA-9E87-93DC4210A404@virtualized.org>
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> <52CEF4E9.1070505@gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
X-Mailer: Apple Mail (2.1827)
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:41:09 -0000

On Jan 9, 2014, at 11:13 AM, Brian E Carpenter <brian.e.carpenter@gmail.com> wrote:
>> 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.

The problem is that this issue keeps repeating, particularly in (shall we say) non-technical venues. In a private message I semi-seriously suggested someone should write an RFC that deprecates classes other than IN.  However, I'm beginning to think this might not be that bad of an idea -- at least there would be a document that the non-technical folks who keep raising the issue could be pointed at...

Regards,
-drc

v2.23.0 | Report a Bug | By Email