-> new draft WG charter
by Kent Crispin
----------------------------------------------------------------------
Date: 13 Aug 1996 02:01:35 -0700
From: Simon Higgs
Subject: Re: Shared AND Exclusive TLDS !!!
Kent,
>Got a chance to review your draft over the weekend -- generally
>excellent work, BTW, except you persistently misspelled "categories"
>-- and the sections that caught my eye earlier were "5.2 Specialized
>TLD Class" and, even more, "5.3 Corporate TLD Class". I interpreted
>these to be monopoly TLDs, and, if I had my druthers, I would
>disallow corporate TLDs entirely, and put stronger controls on
>"specialized TLDs".
>
You found the main typo in the draft. This will change. There's a
difference between a tightly controlled TLD (such as .INT), and an
exclusively held TLD (such as .GOV, or .MIL). This is what this is intended
to explain. Forget corporations. 5.3 should read (see 03 when it gets
released):
5.3. Single Organization TLD Class
Each Single Organization TLD is operated by a single organization
who has exclusive use of the TLD. It is that organization's
responsibilty for all registrations under this TLD, including a
charter.
>Your draft was completed before I got involved in the list, 'tis
>true. I am amazed to hear that there was consensus on anything...
>
>I would like to use potentially large gobs of stuff from your draft
>as a part of a draft strictly related to shared TLDs, so I moved this
>over to the shared-tld list -- like I said, I think you did an excellent
>job, and a lot of the material does directly related to just shared
>tlds.
>
>Given the legal miasma that has developed over these issues, I think
>there should be some changes in the proposed oversight structure --
>things like the Board of Trustees for a TLD, and so on. And of course
>there are a number of technical details to be discussed. So would you
>be game for working on a new draft specifically concerning shared
>TLDs?
>
Yes, but it should explain in detail the brief statements made in the
current draft. The current draft is intended to replace RFC1591 (I have
Postel's permission) and describes the overall NS picture. I think a
shared-tld draft should explain how the shared-tld process works within the
context of the larger picture. I sorta designed it that way, so shared-tlds
could just plug into the main DNS infrastructure without a lot of extra
work being created.
_____S_i_m_o_n___H_i_g_g_s_________________H_i_g_g_s___A_m_e_r_i_c_a_____
... "I'm fine - it's the others" ......... President/CEO ................
_____e-mail: simon@higgs.com _____________ http://www.higgs.com/ ________
... http://ds.internic.net/internet-drafts/draft-higgs-tld-cat-02.txt ...
----------------------------------------------------------------------
Date: 13 Aug 1996 02:41:07 -0700
From: kslim@merlion.singnet.com.sg (KOON SANG LIM)
Subject: FW: Re: FW: Re: FW: Shared TLD's Will NOT Work
Dear Bob
By your argument, I believe that the incompetent registries would die a
natural death. You still need not worry.
Best regards
KS Lim
- ---------------Original Message---------------
On Sun, 11 Aug 1996, KOON SANG LIM wrote:
> Well, if you are arguing for a free,non-profit, charitable type of
> services then I believe you need not worry about any commercial
> competition! Your TLD will be as good as exclusive or non-shared!
> However, you still did not address the point how the registries of
> a shared-TLD can not be operated as humanly as an exclusive one.
Non-shared TLD's that are
geared to specific groups,
professions or organizations
will gear all of their procedures
to their clients. For example
World TeleVirtual Network will
organize it's entire .WTV TLD
registry and directory services
to independant and small Web
Television clients.
When the client picks up the
phone or sends E-mail or registers
they will be dealling with a closed
house process. We can control for
quality and content at every step.
Introduce third parties into the
picture and the circle is broken
by people who don't have a clue
about the clientelle or the
specific media.
In order to provide the requisite
high quality of service we will
not allowISP's or other, generic
TLD's to handle our clientelle.
They will bungle the job no matter
how many charters we send them.
TeleVirtually Yours,
Bob Allisat tor@wtv.net
Director,
World Televirtual Network http://www.wtv.net
----------------------------------------------------------------------
Date: 13 Aug 1996 15:01:16 -0700
From: Kent Crispin
Subject: new draft WG charter
I am enclosing a new copy of the draft WG charter. I have
incorporated the SINGLE suggestion I got for changes (though in a
different place than suggested), and made serveral additions.
Please review. In light of our discussions so far, I think it is
actually fairly important that someone from IANA chair the WG, and I
have added language in support of that.
Here it is:
- ---------------------------------------------------------------------
DRAFT
Shared Top Level Domains Working Group (STLDWG) Charter
Chair(s)
o TBD
(Someone from IANA?)
Internet Area Director(s)
o Frank Kastenholz
o Jeffrey Burgan
Mailing List Information
o General Discussion: shared-tld@higgs.net
o To Subscribe: shared-tld-request@higgs.net
o Archive:
http://www.higgs.net/mail/lists/shared-tld/shared-tld-digest.html
Description of Working Group
The Shared Top Level Domains Working Group is concerned with the
technical and logistic requirements of creating shared domain name
registration databases, and the administration of delegated top level
domains by multiple domain name registries. The motivation for this
concern is to minimize centralized management of all components of
the name space.
Since the proposals of this WG would directly impact the workings of
the IANA, it is recognized that the IANA must actively participate.
The primary products of this WG are three: First the STLD Draft, and
second, a test implemtation of the ideas using the .SHARED TLD as a
test, and three, a revised STLD draft incorporating the lessons from
the experiment, which should become an RFC
In more detail, the areas of concern include
o fostering an appropriate blend of competition and
cooperation between cohort registries
o the relationship between STLD registries and the DNS
o the relationship between STLD registries and the IANA,
including suggested procedures for licensing a registry,
and the associated policies
o technical issues regarding management of the various
databases involved in running and coordinating registries.
This includes issues like distribution of updates, locking
of a shared coordination database, and so on
o the adminstrative procedures involved in running
a registry serving a Shared TLD
o authentication and authorization issues
o minimizing possible legal complexities
o as much as possible, making the relationships between
cohort registries self-regulating -- that is, minimizing
IANA's role in regulation or dispute resolution.
Goals and Milestones
Jan 1997
Submit a Shared Top Level Domain IETF Draft that outlines
one or more technical and policy solutions, along with
a fairly detailed discussion of the tradeoffs that led to
if (them).
Jan 1997
Establishment of the .SHARED TLD for purposes of testing
STLD proposals.
Apr 1997
STLD RFC
- --
Kent Crispin "No reason to get excited",
kent@songbird.com,kc@llnl.gov the thief he kindly spoke...
PGP fingerprint: B6 04 CC 30 9E DE CD FE 6A 04 90 BB 26 77 4A 5E
