Re: Update of RFC 2606 based on the recent ICANN changes ?

Mark Andrews <Mark_Andrews@isc.org> Thu, 03 July 2008 23:14 UTC

Return-Path: <ietf-bounces@ietf.org>
X-Original-To: ietf-archive@megatron.ietf.org
Delivered-To: ietfarch-ietf-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 540AE3A6A40; Thu, 3 Jul 2008 16:14:37 -0700 (PDT)
X-Original-To: ietf@core3.amsl.com
Delivered-To: ietf@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id AE72A3A6AC3 for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 16:14:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.458
X-Spam-Level:
X-Spam-Status: No, score=-3.458 tagged_above=-999 required=5 tests=[AWL=1.141, BAYES_00=-2.599, GB_I_LETTER=-2]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ARzsUNymimBN for <ietf@core3.amsl.com>; Thu, 3 Jul 2008 16:14:35 -0700 (PDT)
Received: from drugs.dv.isc.org (drugs.dv.isc.org [IPv6:2001:470:1f00:820:214:22ff:fed9:fbdc]) by core3.amsl.com (Postfix) with ESMTP id 8F70D3A6A1D for <ietf@ietf.org>; Thu, 3 Jul 2008 16:14:34 -0700 (PDT)
Received: from drugs.dv.isc.org (localhost [127.0.0.1]) by drugs.dv.isc.org (8.14.2/8.14.2) with ESMTP id m63NEY56048085; Fri, 4 Jul 2008 09:14:34 +1000 (EST) (envelope-from marka@drugs.dv.isc.org)
Message-Id: <200807032314.m63NEY56048085@drugs.dv.isc.org>
To: Frank Ellermann <hmdmhdfmhdjmzdtjmzdtzktdkztdjz@gmail.com>
From: Mark Andrews <Mark_Andrews@isc.org>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
In-reply-to: Your message of "Thu, 03 Jul 2008 01:59:14 +0200." <g4h4jm$fcn$1@ger.gmane.org>
Date: Fri, 04 Jul 2008 09:14:34 +1000
Cc: ietf@ietf.org
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: IETF-Discussion <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
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>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org

> Mark Andrews wrote:
> 
> > The Internet went to multi-label hostnames ~20 years ago.
> 
> As noted in RFC 2821 as "one dot required" syntax, also
> mentioned in RFC 3696.  Recently *overruled* by 2821bis.

	There is a difference between allowing protocol to be used
	in a "local" only mode (single label) and a "global" mode
	(multi-label) and saying you must support single label in
	a global context.

	Single label names are local in scope.  Attempting to use
	them in a global context does not work.  As the names in
	"." get more interesting the probability of collisions with
	existing names goes up.  Not many people choose two letter
	labels for the least significant parts of their host names
	unless they are choosing their initials.

	Museum on the other hand is a real English word.  I'm sure
	you will find lots other uses of "museum" in the DNS.  The
	same thing will happen with other TLD's as the rules are
	relaxed.

	Single label hostnames are not globally unique.  They SHOULD
	NOT be used in a context where globally unique names are
	required.

	Mark
 
-- 
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews@isc.org
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf