Re: Services and top-level DNS names (was: Re: Update of RFC 2606

Mark Andrews <> Sat, 05 July 2008 05:00 UTC

Return-Path: <>
Received: from [] (localhost []) by (Postfix) with ESMTP id 2B03028C0CE; Fri, 4 Jul 2008 22:00:25 -0700 (PDT)
Received: from localhost (localhost []) by (Postfix) with ESMTP id 713C13A69A0 for <>; Fri, 4 Jul 2008 22:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[GB_I_LETTER=-2]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id RufEiZ+o3iLs for <>; Fri, 4 Jul 2008 22:00:23 -0700 (PDT)
Received: from ( [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by (Postfix) with ESMTP id 9CF8D3A68CD for <>; Fri, 4 Jul 2008 22:00:22 -0700 (PDT)
Received: from (localhost []) by (8.14.2/8.14.2) with ESMTP id m6550DRW062767; Sat, 5 Jul 2008 15:00:13 +1000 (EST) (envelope-from
Message-Id: <>
To: John Levine <>
From: Mark Andrews <>
Subject: Re: Services and top-level DNS names (was: Re: Update of RFC 2606
In-reply-to: Your message of "Fri, 04 Jul 2008 22:43:49 -0400." <>
Date: Sat, 05 Jul 2008 15:00:13 +1000
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <>
List-Unsubscribe: <>, <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit

> >> No. 4 says "Strings must not cause any technical instability." which 
> >> sounds exactly within IETF scope covers the gist of the technical 
> >> aspects of the ietf list discussion.
> > 	We need "cannot be used in a manner that causes technical
> > 	instablitity.  Known causes include, but are not limited
> > 	to, adding A, AAAA and MX records at the zone apex."
> As someone else pointed out, there are currently about two dozen TLDs with 
> A or MX records at the apex.  Some of them have been like that for many 
> years, and as best I can tell, the Internet has not thereby collapsed.

	How many label our hosts with two letter domain names?

	Do you have any evidence that they have not caused problems?
	I suspect that other sites that used the names just put up
	with the pain of renamimg hosts along with the resultant
	risk of email being misdirected.

> I think we all understand that the use of addresses like http://tld/ and 
> foo@tld may be flaky due to bugs in client software, but if someone wants 
> to spend $100 grand on a TLD and install a flaky A or MX, why is that an 
> urgent problem the IETF needs to solve rather than a private issue between 
> the TLD and its registrants?

	This sentence indicates that you fail to understand all of the
	issues involved.
> Also keep in mind that most of those apex records are in ccTLDs over which 
> ICANN and the IETF have no authority, so no matter what the we were to 
> say, they're not going away.
> Regards,
> John Levine,, Primary Perpetrator of "The Internet for Dummies
> ",
> Information Superhighwayman wanna-be,, ex-Mayor
> "More Wiener schnitzel, please", said Tom, revealingly.
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET:
Ietf mailing list