Re: Update of RFC 2606 based on the recent ICANN changes ?
Stephane Bortzmeyer <bortzmeyer@nic.fr> Sun, 29 June 2008 19:53 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 12CBB3A6942; Sun, 29 Jun 2008 12:53:05 -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 9B3213A69C1 for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 12:53:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[AWL=0.150, BAYES_00=-2.599]
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 IeA5ei-9P3N8 for <ietf@core3.amsl.com>; Sun, 29 Jun 2008 12:53:02 -0700 (PDT)
Received: from mail.bortzmeyer.org (aetius.bortzmeyer.org [217.70.190.232]) by core3.amsl.com (Postfix) with ESMTP id DF9743A6942 for <ietf@ietf.org>; Sun, 29 Jun 2008 12:53:01 -0700 (PDT)
Received: by mail.bortzmeyer.org (Postfix, from userid 10) id 7CF76949EC; Sun, 29 Jun 2008 21:53:08 +0200 (CEST)
Received: by mail.sources.org (Postfix, from userid 1000) id 52A631906DF; Sun, 29 Jun 2008 21:51:17 +0200 (CEST)
Date: Sun, 29 Jun 2008 21:51:17 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Marshall Eubanks <tme@multicasttech.com>
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <20080629195117.GA28916@sources.org>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
MIME-Version: 1.0
Content-Disposition: inline
In-Reply-To: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
X-Transport: UUCP rules
X-Operating-System: Debian GNU/Linux lenny/sid
User-Agent: Mutt/1.5.18 (2008-05-17)
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>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
On Fri, Jun 27, 2008 at 02:43:17PM -0400, Marshall Eubanks <tme@multicasttech.com> wrote a message of 20 lines which said: > It seems like additional TLD domains, beyond just the 4 in RFC 2606, > should be either reserved or blocked. I have the feeling that it is a recurring question, although I cannot find immediately a pointer to the relevant discussions. Anyway, I'm not sure it is a good idea and, should we publish a RFC, it could possibly explain why people should not use local TLDs like ".local". > Suggestions include .local (apparently used heavily by Microsoft), > .internal As far as I know (but I cannot find a formal statement from the IAB or a RFC), "local" TLDs like ".local" are regarded as a bad idea, mostly because they are a pain to manage, should two organizations merge. Also, they are vulnerable to leaks (in the Received: headers of email, for instance). Globally unique domains are therefore better. At a time (when Network Solutions was taking money from ".com" registrants and when most ccTLDs were terribly closed), these TLD were the only reasonable solution for some people. Now, it is much more realistic to obtain a domain name in the TLD of your choice for a very small price. Rather than reserving ".local", shouldn't we advise people to use a regular domain name? > (and, not least, whether there is a better mail list for this > discussion). dnsop ? _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Update of RFC 2606 based on the recent ICANN chan… Marshall Eubanks
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … SM
- Re: Update of RFC 2606 based on the recent ICANN … SM
- Re: Update of RFC 2606 based on the recent ICANN … Marshall Eubanks
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Joe Abley
- RE: Update of RFC 2606 based on the recent ICANN … Hallam-Baker, Phillip
- Re: Update of RFC 2606 based on the recent ICANN … Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Lawrence Conroy
- Re: Update of RFC 2606 based on the recent ICANN … Joe Baptista
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICANN … SM
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Philip Guenther
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Tony Finch
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- RE: Update of RFC 2606 based on the recent ICANN … Hallam-Baker, Phillip
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … Thomas Narten
- Re: Update of RFC 2606 based on the recent ICANN … David Conrad
- Re: Update of RFC 2606 based on the recent ICANN … Philip Guenther
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Paul Hoffman
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Thomas Narten
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- Re: Update of RFC 2606 based on the recent ICANN … Steve Crocker
- Re: Update of RFC 2606 based on the recent ICANN … Paul Hoffman
- Re: Update of RFC 2606 based on the recent ICANN … Ole Jacobsen
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Paul Hoffman
- RE: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICANN … Steve Crocker
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- RE: Update of RFC 2606 based on the recent ICANN … Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- RE: Update of RFC 2606 based on the recent ICANN … Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICANN … SM
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICANN … SM
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- RE: Update of RFC 2606 based on the recent ICANN … Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Services and top-level DNS names (was: Re: Update… John C Klensin
- RE: Services and top-level DNS names (was: Re: Up… Bernard Aboba
- Single-letter names (was: Re: Update of RFC 2606 … John C Klensin
- RE: Services and top-level DNS names (was: Re: Up… John C Klensin
- RE: Services and top-level DNS names (was: Re: Up… Bernard Aboba
- Re: Services and top-level DNS names (was: Re: Up… John Levine
- Re: Services and top-level DNS names (was: Re: Up… Dave Crocker
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- RE: Services and top-level DNS names (was: Re: Up… John C Klensin
- RE: Single-letter names (was: Re: Update of RFC 2… JFC Morfin
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Services and top-level DNS names Karl Auerbach
- Re: Services and top-level DNS names (was: Re: Up… John Levine
- Re: Services and top-level DNS names Frank Ellermann
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- Re: Services and top-level DNS names Frank Ellermann
- Re: Services and top-level DNS names (was: Re: Up… John Levine
- Re: Services and top-level DNS names (was: Re: Up… Brian E Carpenter
- Re: Services and top-level DNS names (was: Re: Up… John C Klensin
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- Re: Services and top-level DNS names (was: Re: Up… John Levine
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- Re: Services and top-level DNS names (was: Re: Up… John Levine
- Re: Services and top-level DNS names (was: Re: Up… Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … moore
- Re: Services and top-level DNS names (was: Re: Up… Jaap Akkerhuis
- Re: Update of RFC 2606 based on the recent ICANN … Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICANN … Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICANN … Vint Cerf
- Re: Single-letter names (was: Re: Update of RFC 2… William Tan
- Re: Single-letter names (was: Re: Update of RFC 2… Vint Cerf
- RE: Single-letter names (was: Re: Update of RFC 2… Edmon Chung
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- Re: Services and top-level DNS names (was: Re: Up… John C Klensin
- RE: Single-letter names (was: Re: Update of RFC 2… michael.dillon
- RE: Single-letter names (was: Re: Update of RFC 2… Ted Hardie
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- Re: Services and top-level DNS names (was: Re: Up… Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Theodore Tso
- Re: Update of RFC 2606 based on the recent ICANN … Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Theodore Tso
- Re: Update of RFC 2606 based on the recent ICANN … Willie Gillespie
- Re: Update of RFC 2606 based on the recent ICANN … Karl Auerbach
- Re: Update of RFC 2606 based on the recent ICANN … Theodore Tso
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … James Seng
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Dave Crocker
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Joe Abley
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICANN … Douglas Otis
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Services and top-level DNS names (was: Re: Up… John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Services and top-level DNS names (was: Re: Up… Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … Marshall Eubanks
- Re: Services and top-level DNS names (was: Re: Up… John C Klensin
- RE: Services and top-level DNS names (was: Re: Up… Cellario Luca
- Re: Update of RFC 2606 based on the recent ICANN … Bob Braden
- Re: Single-letter names Eric Brunner-Williams
- RE: Single-letter names (was: Re: Update of RFC 2… John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Tony Finch
- Re: Update of RFC 2606 based on the recent ICANN … John Levine
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … John C Klensin
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Keith Moore
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Mark Andrews
- Re: Update of RFC 2606 based on the recent ICANN … Bill Manning
- Re: Update of RFC 2606 based on the recent ICANN … Joe Touch
- Re: Update of RFC 2606 based on the recent ICANN … Ted Faber