RE: [wg-c] Application Requirements

["Christopher Ambler" <cambler@iodesign.com>]

Please add:

1. Proposed initial TLD
2. Published TLD meaning or purpose
3. Supporting documentation relating to trademark status of TLD

Let's face it, if SLDs are causing such a ruckus with regards to
trademarks, TLDs fall into the same boat. There's no functional
difference in the trademark issues between ibm.com and .ibm

--
Christopher Ambler
chris@the.web


-----Original Message-----
From: owner-wg-c@dnso.org [mailto:owner-wg-c@dnso.org]On Behalf Of
Kendall Dawson
Sent: Saturday, March 25, 2000 7:37 PM
To: wessorh@ar.com
Cc: wg-c@dnso.org
Subject: [wg-c] Application Requirements


Hi Rick,

Were you thinking something along these lines? I have also posted a HTML
version of this list here: http://paradigm.nu/dnso/ and would be happy to
maintain and update it as the document evolves with feedback from other
WG-C members.

If we could agree on some of the common elements that would part of such an
application now - it will save time in the future while we discuss more
important issues such as Registry Models. Please let me know if you have
any suggestions for this list and I will add them.

Does anyone else have any suggestions?

Kendall

-----------Original message -----------
From: Rick H Wesson <wessorh@ar.com>
Date: Sat, 25 Mar 2000 08:10:42 (PST)

how about we separate out the common items and make that a general section
to the application and then develop appropriate questions for each instance
where policy could be different.

==============================


Application Requirements (Working Draft)

------------------------
General Information :
(Common Elements)
------------------------

Full name
Mailing Address
Phone and Fax Numbers
Public key
List of directors

Overview of the business
Business plan
Technical capabilities
Estimated volume of registrations.

Description of network capabilities
Description of telephone systems
Description of computer systems
Description of technical support
Backup and disaster recovery plan

------------------------
Undecided Issues:
(Registry Models)
------------------------

Shared vs. Non-shared:

Certificate authority (SSL)
Directory, "whois" and Directory services
Name conflicts and Addressing
Compliance to certain minimum software standards
What reports are generated for registrars?
How are the gTLD root servers operated and updated?
Service Level, and QOS issues

------------------------

Security Issues:

Probationary phase
Audit/review process
Requirements that a TLD registry MUST meet, a minimum TLD SLA
Protocol used for registrations
Physical security mechanisms
Insurance and bonds

------------------------

Chartered vs. Non-chartered:

Restrictions of current registrar status
Would the applicant run the root for the gTLD(s) in question?
What gTLD(s) do they propose to run?
Trademark and ownership issues (WIPO recommendations)

------------------------

Commercial vs. Non-commercial:

Fees - price and billing requirements, how will the registry bill their
clients?
What should happen in the case of business failure or bankruptcy ?
Business and revenue model

------------------------