Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt

Olafur Gudmundsson <> Thu, 13 February 2014 16:19 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 9A95A1A0334 for <>; Thu, 13 Feb 2014 08:19:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.6
X-Spam-Status: No, score=-1.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, MIME_8BIT_HEADER=0.3, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id WFxS_jV_yvxN for <>; Thu, 13 Feb 2014 08:19:29 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 256881A030A for <>; Thu, 13 Feb 2014 08:19:29 -0800 (PST)
Received: from localhost (localhost.localdomain []) by (SMTP Server) with ESMTP id D6D3B1A0227; Thu, 13 Feb 2014 11:19:27 -0500 (EST)
X-Virus-Scanned: OK
Received: by (Authenticated sender: with ESMTPSA id AC0561A01C8; Thu, 13 Feb 2014 11:19:26 -0500 (EST)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.6 \(1510\))
From: Olafur Gudmundsson <>
In-Reply-To: <>
Date: Thu, 13 Feb 2014 11:19:26 -0500
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <> <>
To: Patrik Fältström <>
X-Mailer: Apple Mail (2.1510)
Cc: Marc Blanchet <>,
Subject: Re: [DNSOP] I-D Action: draft-wkumari-dnsop-alt-tld-00.txt
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: IETF DNSOP WG mailing list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Feb 2014 16:19:30 -0000

On Feb 13, 2014, at 10:49 AM, Patrik Fältström <> wrote:

> On 2014-02-13 10:23, Marc Blanchet wrote:
>> - why not just register a URN namespace and use it as they see fit?
> Because you only type in a string that "looks like a domain name" in
> applications (for example browsers) without the URI scheme nowadays, and
> people want that to work also with strings in other namespaces.
> I.e. it all, from my perspective, have to do with where the signalling
> is on what namespace to use. And if that signalling is inline, then we
> do have something that can be viewed as the equivalent of a namespace
> collision.
> If people had entered the URI scheme all the time, including "http",
> then we would have been in a different situation.

I think that the draft is not radical enough it is trying to provide some belt and suspenders to a 
syntom rather than address the actual problem. 

The Meta problem is Multiple Namespaces with different resolution technologies. 
Addressing this via a SUFFIX in the domain name feels wrong, 
What I will propose is a Namespace layer solution that is a prefix to the name presented, 
thus names will be presented to the namespace layer as <namespace/name-encoding><space separator><name> 
Examples using ## as the separator    This is normal DNS name, 
	DUTF8##….. (DNS name in UTF8 format)    (by default the name is DNS) 
With a namespace layer we can have the host reject lookup locally if it does not know how to handle the namespace,
rather than dump it out as ".alt" query. 

I know this requires changes in lookup services and code, but it moves the effort to the people that want new namespaces. 

PS: IANA should maintain a registry of namespaces