Re: [dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00

John Levine <> Mon, 07 March 2011 20:36 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D6F7A3A659C for <>; Mon, 7 Mar 2011 12:36:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -110.786
X-Spam-Status: No, score=-110.786 tagged_above=-999 required=5 tests=[AWL=0.413, BAYES_00=-2.599, HABEAS_ACCREDITED_SOI=-4.3, RCVD_IN_BSP_TRUSTED=-4.3, USER_IN_WHITELIST=-100]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 5iMRAcWi5opT for <>; Mon, 7 Mar 2011 12:36:20 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 8B8ED3A657C for <>; Mon, 7 Mar 2011 12:36:20 -0800 (PST)
Received: (qmail 12199 invoked from network); 7 Mar 2011 20:37:33 -0000
Received: from ( by with QMQP; 7 Mar 2011 20:37:33 -0000
DKIM-Signature: v=1; a=rsa-sha256; c=simple;; h=date:message-id:from:to:subject:in-reply-to:cc:mime-version:content-type:content-transfer-encoding:vbr-info; s=14903.4d75420d.k1103;; bh=dRjL2nolRgMSqkkX7a5pJczWKO23VMvVAjPmyZtuQYw=; b=GkdlHeRT2Sz1EvdXHPhS9ytctUSqHwtPFvgPoNMYY6qiaEb5Bqc1/J11QVmFxtgDHbwa8/IniCcu5G8GAJmAMqjgXv1pbtWepwt2WBjiJ9vIPui77XUSQ0B9Fg2nvcQYZqFQlFJuFIiaeo3thBRqCoJWgHdiwydnbke7HOiV/UE=
VBR-Info:; mc=all;
Date: 7 Mar 2011 20:37:33 -0000
Message-ID: <20110307203733.84226.qmail@joyce.lan>
From: John Levine <>
In-Reply-To: <>
X-Headerized: yes
Mime-Version: 1.0
Content-type: text/plain; charset=utf-8
Content-transfer-encoding: 7bit
Subject: Re: [dnsext] New Version Notification for draft-barton-clone-dns-labels-fun-profit-00
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DNS Extensions working group discussion list <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 07 Mar 2011 20:36:23 -0000

>Title:		 Cloning Domain Name System (DNS) Labels for Fun and Profit

Looks promising.

In section 3, why does a CARNS have to make future queries to the
preferred version?  Is it to improve cacheing, or is there something
else about it that I'm missing?

In 1.1, "truly equal" is really an application issue.  From a user's
point of view, if a web browser changes the name in the displayed URL
to the preferred one, the names aren't equal, and if it shows what you
entered, they are, regardless of what bits the DNS might have
returned, Ditto mail programs changing domains in mail addresses and
so forth.  With that in mind, I don't see the fact that the
application can tell which name is preferred as a significant issue.