ICANN/DNSO
DNSO Mailling lists archives

[ga-full]


<<< Chronological Index >>>    <<< Thread Index >>>

[ga] Re: [ga-roots] MOTION - Consensus-Based Policy on Alt Roots

  • To: General Assembly of the DNSO <ga@dnso.org>
  • Subject: [ga] Re: [ga-roots] MOTION - Consensus-Based Policy on Alt Roots
  • From: Jeff Williams <jwkckid1@ix.netcom.com>
  • Date: Wed, 09 May 2001 14:52:39 -0700
  • Organization: INEGroup Spokesman
  • References: <Pine.BSF.4.21.0105090259200.95774-100000@pan.bijt.net> <4.3.2.7.2.20010509115008.06b9de00@127.0.0.1>
  • Sender: owner-ga-full@dnso.org

Harald and all,

Harald Tveit Alvestrand wrote:

> At 13:10 09.05.2001 +1000, Patrick Corliss wrote:
> >Hi Marc
> >
> >As the role of the DNSO General Assembly is to provide consensus-based
> >policy input to ICANN, I have asked everybody that they think that
> >consensus-based policy should be?  I therefore move the following policy
> >should be adopted by ICANN:
> >
> >"ICANN adopts compliance with the relevant DNS standards as a general
> >principle.  It recognises that there is a likelihood of collision and/or
> >confusion when root operators do not comply with RFC 1591 which suggests
> >that there should be a "unique root zone*.  ICANN will therefore adopt
> >methods and measures to foster co-operation and compliance within the
> >industry."
> >
> >Any seconders?
>
> Motion to amend motion.
>
> Note that debate in the GA can only affect GA statements. Thus, the
> statement should be formulated as a request to the Names Council to propose
> a policy to the ICANN BoD.
>
> In addition, I (like William) think that this statement does not say what
> the majority of the GA wants it to say. I could be wrong about the majority....

  Yes you could be!  >;)  It seems that 16m new.net subscribers would be
a good indication that you are mistaken...

>
>
> Amended motion.
>
> "The DNSO GA recommends that the DNSO NC recommend to the ICANN BoD the
> following policy statement:
>
> ------
> ICANN administers a set of "root" servers that conform to the DNS protocol
> as standardized by the IETF, serving a namespace hereafter referred to as
> the "ICANN namespace".

  There is NO "ICANN namespace".  There IS however a USG Namespace...
As such I believer this motion to amend is our of order....

>
>
> Recognizing the need for an unique namespace at the root of the DNS as
> specified in RFC 2826, ICANN reaffirms that it will not initiate services
> where root servers under ICANN control will return different answers for
> the same domain name; ICANN will operate only one namespace.
>
> Recognizing that there is an urgent request for the addition of names to this
> namespace, ICANN has started establishing procedures for such additions,
> the first of which are scheduled to be added in 2001.
>
> ICANN recognizes that there are other name spaces served by organizations
> unrelated to ICANN, for purposes other than serving as the traditional
> DNS root.
>
> Where the operators of other name spaces are selling services to others,
> ICANN urges the operators of those name spaces to take one or both of two
> steps:
>
> - Make it clear to their customers that these name spaces are unaffiliated
>    with the ICANN namespace in any way. One effective means of doing this
>    is to not include any reference to names registered in the ICANN
>    namespace (such as .com).
>
> - If there are names in their namespace that they wish to have added to
>    the ICANN namespace, follow the procedures for applying for such names
>    as soon as such procedures are reopened following the evaluation of the
>    first round of additions.

  This process has already been panned as being improper...  Hence
such a procedure has to be modified in order to meet the RFC's which
ICANN perports to support.

>
>
> ---------
>
> The logic should be obvious - make clear that the other namespaces are
> REALLY unaffiliated, and must sink or swim on their own.
>
>         Harald, who believes in explicit policies.....
>
> --
> This message was passed to you via the ga-roots@dnso.org list.
> Send mail to majordomo@dnso.org to unsubscribe
> ("unsubscribe ga-roots" 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 >>>