IETF Logo Mail Archive

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

Marshall Eubanks <tme@multicasttech.com> Fri, 27 June 2008 19:43 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 7A4853A684F; Fri, 27 Jun 2008 12:43:44 -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 108D63A684F for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 12:43:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.523
X-Spam-Level:
X-Spam-Status: No, score=-103.523 tagged_above=-999 required=5 tests=[AWL=0.076, BAYES_00=-2.599, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 XvKTlXwiwSsf for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 12:43:42 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 3059D3A67CE for <ietf@ietf.org>; Fri, 27 Jun 2008 12:43:42 -0700 (PDT)
Received: from [63.105.122.7] (account marshall_eubanks HELO [IPv6:::1]) by multicasttech.com (CommuniGate Pro SMTP 3.4.8) with ESMTP-TLS id 11925205; Fri, 27 Jun 2008 15:43:47 -0400
Message-Id: <BBB8E0B4-7E45-4BE9-B9DF-DEBE294585D6@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: SM <sm@resistor.net>
In-Reply-To: <6.2.5.6.2.20080627121824.02c55340@resistor.net>
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Re: Update of RFC 2606 based on the recent ICANN changes ?
Date: Fri, 27 Jun 2008 15:43:46 -0400
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com> <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org> <6.2.5.6.2.20080627121824.02c55340@resistor.net>
X-Mailer: Apple Mail (2.924)
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-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


On Jun 27, 2008, at 3:21 PM, SM wrote:

> Hi David,
> At 11:51 27-06-2008, David Conrad wrote:
>> I believe an RFC that provides an IETF-defined list of names (beyond
>> the 4 in 2606) and/or rules defining names the "Internet technical
>> community" feels would be inappropriate as top-level domains would be
>> quite helpful.
>
> Do you mean as in RFC 3675?
>

Well, I can't speak for David, but that was not really what I was  
thinking of, or what I think the people I was discussing
this were thinking.

I was thinking of things like .local, which could cause problems if  
they were
given out.

Regards
Marshall

> Regards,
> -sm
> _______________________________________________
> Ietf mailing list
> Ietf@ietf.org
> https://www.ietf.org/mailman/listinfo/ietf

_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email