Re: [mif] [DNSOP] [dnsext] 2nd Last Call for MIF DNS server selection document Mon, 24 October 2011 06:08 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id AECFC11E8091 for <>; Sun, 23 Oct 2011 23:08:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -5.999
X-Spam-Status: No, score=-5.999 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, J_CHICKENPOX_33=0.6, RCVD_IN_DNSWL_MED=-4]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id ndtzd1tCHOah for <>; Sun, 23 Oct 2011 23:08:26 -0700 (PDT)
Received: from ( []) by (Postfix) with SMTP id 32E4611E808F for <>; Sun, 23 Oct 2011 23:08:25 -0700 (PDT)
Received: (qmail 49707 invoked from network); 24 Oct 2011 06:08:23 -0000
Received: from (HELO localhost) ( by with SMTP; 24 Oct 2011 06:08:23 -0000
Date: Mon, 24 Oct 2011 08:08:22 +0200
Message-Id: <>
In-Reply-To: <>
References: <> <> <>
X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI)
Mime-Version: 1.0
Content-Type: Text/Plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailman-Approved-At: Sun, 23 Oct 2011 23:35:53 -0700
Subject: Re: [mif] [DNSOP] [dnsext] 2nd Last Call for MIF DNS server selection document
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Multiple Interface Discussion List <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Mon, 24 Oct 2011 06:08:27 -0000

> > I can't agree with this statement.  As others have said, the practice of using a search list to allow 'ssh' to reach '' isn't going anywhere, and there are a lot of people that make extensive use of the convenience.
> It needs to die because it's fundamentally broken.   Vanity TLDs will only make it worse.   I understand that there are sites that use it and people who are accustomed to it.   I don't pretend that we can stop them.   We can, however, explain the negative consequences of doing this (some of which might be specific to systems with multiple interfaces), and recommend that they transition away from that practice.   And recommendations for systems with multiple interfaces can be chosen in such a way as to allow search lists to break even more.

I routinely use short names (and thus search lists) in my work. I am
aware of vanity domains, and of RFC 1535. Have I stopped using short
names and search lists? No, the convenience is just too great.

In trying to stop the use of short names and search lists I believe
you're trying to fight human nature. It's a waste of time, and unlikely
to be productive.

Steinar Haug, Nethelp consulting,