ICANN/GNSO
DNSO and GNSO Mailling lists archives

[ga]


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

[ga] Re: "Historically, the goal of the practice has been to improve the quality of data in the DNS."


Jim and all assembly members,

  Jim , it would seem that despite your particular style, you are quite
correct here.  >;)

Jim Fleming wrote:


> http://www.icann.org/correspondence/cerf-lynn-letter-to-names-council-20sep02.htm
> "Historically, the goal of the practice has been to improve the quality of data in the DNS. Pursuing the RFC 1591 policy that the
> IANA should make checks to verify nameserver "operational status and database accuracy", the IANA follows the practice of obtaining
> and technically reviewing TLD zone files as part of the technical checks it performs when nameserver changes are requested. Although
> checks for the most severe database misconfigurations can be performed by other means, many less severe errors have been detected
> through this review. The ordinary result of finding one or more of these less severe errors is to proceed with the root-zone change,
> to alert the ccTLD manager of the error, and to request that it be remedied."
>
> =======
>
> It should not take a rocket scientist to understand that the entire process can be highly automated with software.
>
> Adding layer upon layer of committees to perform a task, best done by computers, is absurd.
>
> One would hope that the new "adult supervision" being brought into the picture by the U.S. Government,
>
> would be able to see this in an instant and direct the root server operators under their control to bring their
>
> servers up to date. In fact, the TLD Managers can communicate directly to ALL root server operators to
>
> signal any changes, in case those TLD Managers do not have the simple software that is able to check TLD
>
> clusters on an ongoing basis, and report changes. Various web-based tools are available to check and
>
> confirm the results, for people that insist that humans have to be paid $250,000 per year to do this. This is
>
> likely a precursor to how the .ORG TLD will be managed. With $18,000,000 per year in revenue, there
>
> can be 72 people sitting around debating how many angels can dance on the head of a pin and all be
>
> very well-paid to do that, while the rest of the world asks, What do they do again ?
>
> http://root-dns.org/vuedig.htm
> http://www.analogx.com/contents/dnsdig.htm
>
> Jim Fleming
> 2002:[IPv4]:000X:03DB:...IPv8 is closer than you think...IPv16 is even closer...
> http://www.netfilter.org/
> http://ipv8.dyndns.tv
> http://ipv8.yi.org
> http://ipv8.dyns.cx
> http://ipv8.no-ip.com
> http://ipv8.no-ip.org
> http://ipv8.no-ip.biz
> http://ipv8.no-ip.info
> http://ipv8.myip.us
> http://ipv8.dyn.ee
> http://ipv8.community.net.au
> http://ipv8.ods.org

Regards,

--
Jeffrey A. Williams
Spokesman for INEGroup - (Over 127k members/stakeholders 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: 214-244-4827 or 972-244-3801
Address: 5 East Kirkwood Blvd. Grapevine Texas 75208


--
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




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