IETF Logo Mail Archive

Update of RFC 2606 based on the recent ICANN changes ?

Marshall Eubanks <tme@multicasttech.com> Fri, 27 June 2008 18: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 75DCC3A68E8; Fri, 27 Jun 2008 11:43:15 -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 EB40A3A68E8 for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:43:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -103.518
X-Spam-Level:
X-Spam-Status: No, score=-103.518 tagged_above=-999 required=5 tests=[AWL=0.081, 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 u1wgkE40Lzc1 for <ietf@core3.amsl.com>; Fri, 27 Jun 2008 11:43:13 -0700 (PDT)
Received: from multicasttech.com (lennon.multicasttech.com [63.105.122.7]) by core3.amsl.com (Postfix) with ESMTP id 1E5C13A68DD for <ietf@ietf.org>; Fri, 27 Jun 2008 11:43:13 -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 11924565 for ietf@ietf.org; Fri, 27 Jun 2008 14:43:18 -0400
Message-Id: <4C0AE13D-4CA6-4989-A6B0-555A014DE464@multicasttech.com>
From: Marshall Eubanks <tme@multicasttech.com>
To: ietf@ietf.org
Mime-Version: 1.0 (Apple Message framework v924)
Subject: Update of RFC 2606 based on the recent ICANN changes ?
Date: Fri, 27 Jun 2008 14:43:17 -0400
X-Mailer: Apple Mail (2.924)
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

I have been having a discussion on NANOG about possible problems with  
the
new Top Level Domains coming out of ICANN. It seems like additional  
TLD domains, beyond
just the 4 in RFC 2606, should be either reserved or blocked.  
Suggestions include .local (apparently
used heavily by Microsoft), .internal, as well as maybe translations  
of .test .example .invalid .localhost into
other languages / character sets.

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).

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

v2.23.0 | Report a Bug | By Email