HTTP/2 302 date: Mon, 14 Jul 2025 13:45:18 GMT content-type: text/html; charset=utf-8 location: https://archive.icann.org/tlds/pso-statement-09aug00.htm x-ratelimit-remaining: 195 x-ratelimit-requested-tokens: 5 x-ratelimit-burst-capacity: 200 x-ratelimit-replenish-rate: 100 x-frame-options: SAMEORIGIN cache-control: max-age=120, public referrer-policy: origin-when-cross-origin content-security-policy: frame-ancestors *.icann.org strict-transport-security: max-age=48211200; preload cf-cache-status: DYNAMIC set-cookie: __cf_bm=tjzjDZGCec5Ud0u9OjJ4QJ7lIpu1vSSjw7FOLt7eUXQ-1752500718-1.0.1.1-tgR08H_2gyoY9YtxaknyCuXMzc.K3QEZsKkhE8YTpKzpuZL6dx0WoyL4E.LNio.miHvWwMrdjNuKhNgHMnQsyBCzttL2RJFXOyU.U5iUjJw; path=/; expires=Mon, 14-Jul-25 14:15:18 GMT; domain=.icann.org; HttpOnly; Secure; SameSite=None server: cloudflare cf-ray: 95f175aa9a7ba403-BLR HTTP/1.1 301 Moved Permanently Date: Mon, 14 Jul 2025 13:45:19 GMT Server: Apache Strict-Transport-Security: max-age=157680000; preload Content-Security-Policy: upgrade-insecure-requests X-Frame-Options: SAMEORIGIN Location: https://archive.icann.org/en/tlds/pso-statement-09aug00.htm Cache-Control: max-age=3600 Expires: Mon, 14 Jul 2025 14:45:19 GMT Content-Length: 266 Content-Type: text/html; charset=iso-8859-1 HTTP/1.1 200 OK Date: Mon, 14 Jul 2025 13:45:19 GMT Server: Apache Strict-Transport-Security: max-age=157680000; preload Content-Security-Policy: upgrade-insecure-requests X-Frame-Options: SAMEORIGIN Vary: Accept-Encoding Accept-Ranges: bytes Cache-Control: max-age=3600 Expires: Mon, 14 Jul 2025 14:45:19 GMT Content-Encoding: gzip Referrer-Policy: origin-when-cross-origin Content-Length: 1359 Content-Type: text/html; charset=UTF-8 Content-Language: en

Statement of Protocol Supporting Organization on New TLDs The Protocol Council of the Protocol Supporting Organization submitted the following statement on new TLDs: Subject: new TLDs Date: Wed, 09 Aug 2000 11:40:33 -0400 From: Steve Bellovin <smb@research.att.com> To: touton@icann.org (Louis Touton) CC: pso-pc@ietf.org 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 Comments concerning the layout, construction and functionality of this site should be sent to webmaster@icann.org. Page Updated 05-March-2001 (c) 2001  The Internet Corporation for Assigned Names and Numbers. All rights reserved.