<<<
Chronological Index
>>> <<<
Thread Index
>>>
Re: [ga] Re: [council] Collisions in Namespace
Erica, Milton and all remaining assembly members,
I think that such a WG would be a good idea if there are specific criterion
in advance that this WG is task to address. I also feel that such a
WG is also a very risky idea also. So, I would suggest that this
PARTICULAR WG be task and governed by the following
criterion:
1.) That any and all interested parties or stakeholers are able to
participate unfettered.
2.) That this WG address ONLY the areas surrounding introduction
OF new TLD's, Registry practice, Registry/Registrar relationship,
Registrant issues and concerns.
3.) That a full report at the end of a prescribed time be required and sent
to the NC for their review and subsequently passed on to the ICANN
BoD unmodified or otherwise edited. And that this report be posted
on the DNSO Web site.
4.) That the Chair of this WG be chosen by majority vote of the WG
Participants in the first week of it's inception.
If any of you have other specific suggestions to make this WG more
effective please feel free to add to the criterion above....
Erica Roberts wrote:
> Hi Milton,
> Following th election of Patrick Corliss to the GA Alt Chair, the relevance
> of this topic is clear. However, while I tend to agree with your comment
> that:
> ,given enough time and some clear guidance, such a group might achieve some
> consensus points that could bring about a temporary ceasefire .....
> the key issue is the guidance that should be provided to such a TF.
> Do you have any thoughts on this?
>
> erica
>
> ----- Original Message -----
> From: "Milton Mueller" <mueller@syr.edu>
> To: <philip.sheppard@aim.be>; <webmaster@babybows.com>; <council@dnso.org>;
> <ga@dnso.org>
> Sent: Friday, April 13, 2001 1:15 PM
> Subject: Re: [council] Collisions in Namespace
>
> > The problem of alternate or competing roots is a highly complex one. I
> would support the idea of a new, open Working Group being convened on this
> topic. I say this fully understanding that the debate on this topic often
> takes the form of a religious war and that it is unlikely that any coherent
> policy would come out of such a working group soon.
> >
> > However, there is some possibility that, given enough time and some clear
> guidance, such a group might achieve some consensus points that could bring
> about a temporary ceasefire, if not an end, to the war. And I see little
> downside. At worst, the group will waste bandwidth and time and accomplish
> nothing. At best, it might come up with some useful ideas. Why not give it a
> try? The incremental cost of a new mailing list is pretty low.
> >
> >
> >
> > >>> "babybows.com" <webmaster@babybows.com> 04/12/01 17:26 PM >>>
> > "Constituencies or GA participants may propose that
> > the NC consider domain name policies or
> > recommendations."
> >
> > As two principles addressed by the White Paper, stability and competition,
> > have been raised in the course of this debate, and whereas the Department
> of
> > Commerce has previously expressed concern regarding any actions which may
> > lead to the possibility of consumer "confusion", I now ask that the NC
> > consider the ICANN domain name policy with respect to collision with names
> > in the alternate root community.
> >
> >
> >
>
> --
> This message was passed to you via the ga@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga" in the body of the message).
> Archives at http://www.dnso.org/archives.html
Regards,
--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 118k members strong!)
CEO/DIR. Internet Network Eng/SR. Java/CORBA Development Eng.
Information Network Eng. Group. INEG. INC.
E-Mail jwkckid1@ix.netcom.com
Contact Number: 972-447-1800 x1894 or 214-244-4827
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208
--
This message was passed to you via the ga-full@dnso.org list.
Send mail to majordomo@dnso.org to unsubscribe
("unsubscribe ga-full" in the body of the message).
Archives at http://www.dnso.org/archives.html
<<<
Chronological Index
>>> <<<
Thread Index
>>>
|