Re: Update of RFC 2606 based on the recent ICANN changes ?
David Conrad <drc@virtualized.org> Mon, 30 June 2008 13:49 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 6F4AE3A6889;
Mon, 30 Jun 2008 06:49:45 -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 2B1FB3A6889
for <ietf@core3.amsl.com>; Mon, 30 Jun 2008 06:49:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.625
X-Spam-Level:
X-Spam-Status: No, score=-7.625 tagged_above=-999 required=5 tests=[AWL=0.974,
BAYES_00=-2.599, GB_I_LETTER=-2, RCVD_IN_DNSWL_MED=-4]
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 0+cOXyKAUQhA for <ietf@core3.amsl.com>;
Mon, 30 Jun 2008 06:49:43 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190])
by core3.amsl.com (Postfix) with ESMTP id 6173D3A687A
for <ietf@ietf.org>; Mon, 30 Jun 2008 06:49:43 -0700 (PDT)
Received: from [10.0.1.198] (c-71-198-3-247.hsd1.ca.comcast.net [71.198.3.247])
by virtualized.org (Postfix) with ESMTP id 5E8A7266014;
Mon, 30 Jun 2008 06:49:55 -0700 (PDT)
Message-Id: <7DDE5F4C-8910-4DCA-96C1-3BEA5507830B@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: John C Klensin <john-ietf@jck.com>
In-Reply-To: <649DC89B6513C74E89023E29@[192.168.1.110]>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Mon, 30 Jun 2008 06:49:54 -0700
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
<74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org>
<6.2.5.6.2.20080627121824.02c55340@resistor.net>
<BBB8E0B4-7E45-4BE9-B9DF-DEBE294585D6@multicasttech.com>
<6.2.5.6.2.20080627140118.02a43fd8@resistor.net>
<6F1CFDA0-A6E2-4257-8C72-0FCD1E117290@virtualized.org>
<6.2.5.6.2.20080628201322.02e43268@resistor.net>
<FBBF3BB9-D231-494A-AFBE-7F816DD1180C@virtualized.org>
<20080630024615.GA7021@boreas.isi.edu>
<649DC89B6513C74E89023E29@[192.168.1.110]>
X-Mailer: Apple Mail (2.924)
Cc: IETF Discussion <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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ietf-bounces@ietf.org
Errors-To: ietf-bounces@ietf.org
John, On Jun 30, 2008, at 5:43 AM, John C Klensin wrote: > The other two things that seem to be getting lost in this discussion > is that one can write all of the RFCs one like, but rules like this > are ultimately useless unless ICANN agrees to them ICANN has already deferred to the IETF on technical matters (see IDNs). I'm unclear why ICANN would ignore IETF technical input on this matter. > I don't know if the gNSO would like that or not, but it seems to > argue that we should be conservation about what names we reserve and > thereby promote. Yep. The only additional label (to those in 2606) that seems to have a technical justification for being disallowed would appear to be ".local" due to the zeroconf(-like) mechanisms that use it. > Perhaps we should ask ICANN to reserve all single-letter TLDs (in > any script) for IETF use. I don't necessarily agree or disagree, but what would be the technical justification? Regards, -drc _______________________________________________ Ietf mailing list Ietf@ietf.org https://www.ietf.org/mailman/listinfo/ietf
- Update of RFC 2606 based on the recent ICANN ch... Marshall Eubanks
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... SM
- Re: Update of RFC 2606 based on the recent ICAN... SM
- Re: Update of RFC 2606 based on the recent ICAN... Marshall Eubanks
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Joe Abley
- RE: Update of RFC 2606 based on the recent ICAN... Hallam-Baker, Phillip
- Re: Update of RFC 2606 based on the recent ICAN... Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Lawrence Conroy
- Re: Update of RFC 2606 based on the recent ICAN... Joe Baptista
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICAN... SM
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Philip Guenther
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Tony Finch
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- RE: Update of RFC 2606 based on the recent ICAN... Hallam-Baker, Phillip
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... Thomas Narten
- Re: Update of RFC 2606 based on the recent ICAN... David Conrad
- Re: Update of RFC 2606 based on the recent ICAN... Philip Guenther
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Paul Hoffman
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Thomas Narten
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- Re: Update of RFC 2606 based on the recent ICAN... Steve Crocker
- Re: Update of RFC 2606 based on the recent ICAN... Paul Hoffman
- Re: Update of RFC 2606 based on the recent ICAN... Ole Jacobsen
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Paul Hoffman
- RE: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICAN... Steve Crocker
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- RE: Update of RFC 2606 based on the recent ICAN... Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- RE: Update of RFC 2606 based on the recent ICAN... Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICAN... SM
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Stephane Bortzmeyer
- Re: Update of RFC 2606 based on the recent ICAN... SM
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- RE: Update of RFC 2606 based on the recent ICAN... Bernard Aboba
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Services and top-level DNS names (was: Re: Upda... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- RE: Services and top-level DNS names (was: Re: ... Bernard Aboba
- Single-letter names (was: Re: Update of RFC 260... John C Klensin
- RE: Services and top-level DNS names (was: Re: ... John C Klensin
- RE: Services and top-level DNS names (was: Re: ... Bernard Aboba
- Re: Services and top-level DNS names (was: Re: ... John Levine
- Re: Services and top-level DNS names (was: Re: ... Dave Crocker
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- RE: Services and top-level DNS names (was: Re: ... John C Klensin
- RE: Single-letter names (was: Re: Update of RFC... JFC Morfin
- Re: Services and top-level DNS names Karl Auerbach
- Re: Services and top-level DNS names (was: Re: ... John Levine
- Re: Services and top-level DNS names Frank Ellermann
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- Re: Services and top-level DNS names Frank Ellermann
- Re: Services and top-level DNS names (was: Re: ... John Levine
- Re: Services and top-level DNS names (was: Re: ... Brian E Carpenter
- Re: Services and top-level DNS names (was: Re: ... John C Klensin
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- Re: Services and top-level DNS names (was: Re: ... John Levine
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- Re: Services and top-level DNS names (was: Re: ... John Levine
- Re: Services and top-level DNS names (was: Re: ... Mark Andrews
- Re: Services and top-level DNS names (was: Re: ... Jaap Akkerhuis
- Re: Update of RFC 2606 based on the recent ICAN... Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICAN... Lyman Chapin
- Re: Update of RFC 2606 based on the recent ICAN... Vint Cerf
- Re: Single-letter names (was: Re: Update of RFC... William Tan
- Re: Single-letter names (was: Re: Update of RFC... Vint Cerf
- RE: Single-letter names (was: Re: Update of RFC... Edmon Chung
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- Re: Services and top-level DNS names (was: Re: ... John C Klensin
- RE: Single-letter names (was: Re: Update of RFC... michael.dillon
- RE: Single-letter names (was: Re: Update of RFC... Ted Hardie
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- Re: Services and top-level DNS names (was: Re: ... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... moore
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Theodore Tso
- Re: Update of RFC 2606 based on the recent ICAN... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Theodore Tso
- Re: Update of RFC 2606 based on the recent ICAN... Willie Gillespie
- Re: Update of RFC 2606 based on the recent ICAN... Karl Auerbach
- Re: Update of RFC 2606 based on the recent ICAN... Theodore Tso
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Frank Ellermann
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... James Seng
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Dave Crocker
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Joe Abley
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Brian E Carpenter
- Re: Update of RFC 2606 based on the recent ICAN... Douglas Otis
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Services and top-level DNS names (was: Re: ... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Services and top-level DNS names (was: Re: ... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... Marshall Eubanks
- Re: Services and top-level DNS names (was: Re: ... John C Klensin
- RE: Services and top-level DNS names (was: Re: ... Cellario Luca
- Re: Update of RFC 2606 based on the recent ICAN... Bob Braden
- Re: Single-letter names Eric Brunner-Williams
- RE: Single-letter names (was: Re: Update of RFC... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Tony Finch
- Re: Update of RFC 2606 based on the recent ICAN... John Levine
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... John C Klensin
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Keith Moore
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Mark Andrews
- Re: Update of RFC 2606 based on the recent ICAN... Bill Manning
- Re: Update of RFC 2606 based on the recent ICAN... Joe Touch
- Re: Update of RFC 2606 based on the recent ICAN... Ted Faber