IETF Logo Mail Archive

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

David Conrad <drc@virtualized.org> Fri, 27 June 2008 18:51 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 0F0383A67E7; Fri, 27 Jun 2008 11:51:43 -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 9B3393A67E7 for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:51:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.351
X-Spam-Level:
X-Spam-Status: No, score=-6.351 tagged_above=-999 required=5 tests=[AWL=0.248, BAYES_00=-2.599, 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 3oNB8jyDXHnW for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:51:40 -0700 (PDT)
Received: from virtualized.org (trantor.virtualized.org [204.152.189.190]) by core3.amsl.com (Postfix) with ESMTP id E5D3C3A67E2 for <ietf@ietf.org>; Fri, 27 Jun 2008 11:51:38 -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 7F37625EE8F; Fri, 27 Jun 2008 11:51:43 -0700 (PDT)
Message-Id: <74E3E26A-FCFB-45C1-989A-DD7EA5752974@virtualized.org>
From: David Conrad <drc@virtualized.org>
To: Marshall Eubanks <tme@multicasttech.com>
In-Reply-To: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
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 11:51:42 -0700
References: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
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

Hi,

On Jun 27, 2008, at 11:43 AM, Marshall Eubanks wrote:
> I am curious as to  whether others feel like this is a potential
> problem to be addressed (and, not least, whether there is a better  
> mail list for this discussion).

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.

Regards,
-drc
(speaking personally)
_______________________________________________
Ietf mailing list
Ietf@ietf.org
https://www.ietf.org/mailman/listinfo/ietf

v2.23.0 | Report a Bug | By Email