[Pso-discuss] new TLDs (fwd)

Steve Coya <scoya@ietf.org> Wed, 09 August 2000 15:44 UTC

Received: from optimus.ietf.org (ietf.org [] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id LAA09753; Wed, 9 Aug 2000 11:44:30 -0400 (EDT)
Received: from optimus.ietf.org (localhost []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24778; Wed, 9 Aug 2000 11:44:28 -0400 (EDT)
Received: from ietf.org (odin []) by optimus.ietf.org (8.9.1a/8.9.1) with ESMTP id LAA24751 for <pso-discuss@pso.icann.org>; Wed, 9 Aug 2000 11:44:27 -0400 (EDT)
Received: from scoya.cnri.reston.va.us (scoya.cnri.reston.va.us []) by ietf.org (8.9.1a/8.9.1a) with SMTP id LAA09742 for <pso-discuss@pso.icann.org>; Wed, 9 Aug 2000 11:44:25 -0400 (EDT)
Date: Wed, 9 Aug 2000 11:42:50 -0400 (Eastern Daylight Time)
From: Steve Coya <scoya@ietf.org>
To: pso-discuss@pso.icann.org
Message-ID: <Pine.WNT.3.96.1000809114207.-366889I-100000@scoya.cnri.reston.va.us>
X-X-Sender: scoya@odin.cnri.reston.va.us
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: [Pso-discuss] new TLDs (fwd)
Sender: pso-discuss-admin@pso.icann.org
Errors-To: pso-discuss-admin@pso.icann.org
X-Mailman-Version: 1.0
Precedence: bulk
List-Id: PSO Discussion List <pso-discuss.pso.icann.org>
X-BeenThere: pso-discuss@pso.icann.org

PSO PC Response to request for comments pertaining to new TLDs.

---------- Forwarded message ----------
Date: Wed, 09 Aug 2000 11:40:33 -0400
From: Steve Bellovin <smb@research.att.com>
To: Louis Touton <touton@icann.org>
Cc: pso-pc@ietf.org
Subject: new TLDs

1)      We see no technical problems caused by the creation of a 
        relatively small number of new gTLDs.
2)      We recommend that the root servers be monitored for increased
        load caused by these new gTLDs.
3)      We suggest that they be semantically "far" from existing gTLDs,
        to avoid confusion.  Thus, .corp would be be bad, because it is
        too similar to .com.
4)      Names reserved by RFCs (or near RFCs) should be avoided, notably
        "local" (from the HTTP State Management draft, which is about to 
        be named a BCP) and those names listed in RFC 2606.

		--Steve Bellovin

PSO-Discuss mailing list