Re: Update of RFC 2606 based on the recent ICANN changes ?
John C Klensin <john-ietf@jck.com> Tue, 01 July 2008 21: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 D6EF43A6BED; Tue, 1 Jul 2008 14:53:22 -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 4616E3A6BDF for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 14:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.236
X-Spam-Level:
X-Spam-Status: No, score=-1.236 tagged_above=-999 required=5 tests=[AWL=1.363, 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 FEafnIZ1qXMs for <ietf@core3.amsl.com>; Tue, 1 Jul 2008 14:53:20 -0700 (PDT)
Received: from bs.jck.com (ns.jck.com [209.187.148.211]) by core3.amsl.com (Postfix) with ESMTP id 86F823A6BFB for <ietf@ietf.org>; Tue, 1 Jul 2008 14:53:17 -0700 (PDT)
Received: from [127.0.0.1] (helo=p3.JCK.COM) by bs.jck.com with esmtp (Exim 4.34) id 1KDnmi-000Ab9-Oa; Tue, 01 Jul 2008 17:53:13 -0400
Date: Tue, 01 Jul 2008 17:53:11 -0400
From: John C Klensin <john-ietf@jck.com>
To: Thomas Narten <narten@us.ibm.com>, ietf@ietf.org
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Message-ID: <105D288AF30DA6D8EE55976A@p3.JCK.COM>
In-Reply-To: <200807012051.m61KpLeq021685@cichlid.raleigh.ibm.com>
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com> <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org> <6.2.5.6.2.20080627121824.02c55340@resistor.net> <A9ACF7FB-BC78-44D9-AA61-4FCACE821677@virtualized.org> <9486A1E5-864F-4B23-9EBA-697C1A7A7520@ca.afilias.info> <200807012051.m61KpLeq021685@cichlid.raleigh.ibm.com>
X-Mailer: Mulberry/4.0.8 (Win32)
MIME-Version: 1.0
Content-Disposition: inline
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 Tuesday, 01 July, 2008 16:51 -0400 Thomas Narten <narten@us.ibm.com> wrote: >... > Also, for TLDs like .local, one could also to some extent just > say "buyer beware". Anyone wanting a TLD that is known to not > be useable in practice (for some deployed software) would get > what they deserve. :-) The folk wanting TLDs presumably want > TLDs that can actually be used... >... Thomas, Pretend I'm a fine, upstanding, citizen who is in the domain names business (I guess that would make me a "domaineer" :-)) and whose business model is based on traffic concentration and redirection. I think I would really like to own "local", although not as much as I'd like to own "example.com" or any other name to which the IETF or various protocol designs provide free advertising and traffic direction. Every leaked name that might reference a web page would drive traffic to my site, as well as every action that led those who didn't know what was going on to open http://www.local./ to figure out what was going on. In a more sane world, no one rational would want to build a business or other activity around a TLD named "local". But this is demonstrably not a sane world. john _______________________________________________ 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