Richard, As people can see, the .COM TLD is no different from the other TLDs. Changes are made from time to time. Hopefully, these changes will continue and .COM will become free of the legacy Root Name Servers in the IPv4 address space. It looks like Network Solutions is starting to make some of the recommended changes. I think that we all knew that adult supervision would play more and more of a role in the management of TLDs. It is great to see that NSI is playing a leadership role and moving away from the legacy root "playground". While on the subject of .COM, it seems useful to review the .COM neighborhood or "neighbor net" from an IPv8 point of view. As you can see below, .COM is between a vacant seat 0:200 and the .ISLAND TLD 0:202. I have not been able to locate any Trustees for .ISLAND, but I have a feeling they are out there. The Trustees for 0:199, .LTD have been in communication so the neighborhood is taking shape. Hopefully, we can find a group to pick up the 0:200 seat and things will start to fill in and the base of contacts will grow. This will help to keep people informed about what the status is of the various TLDs (including .COM). http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt 0:199 LTD 1. David Rogers - djrogers at enterprise.net 2. Jason Hendeles - jnh at skyscape.net 0:200 <<<<<< AVAILABLE >>>>> 1. __________________________ 2. __________________________ 0:201 COM 1. Jim Fleming - JimFleming at unir.com 2. Richard Sexton - richard at vrx.net 0:202 ISLAND 1. __________________________ 2. __________________________ Hopefully, the RSCs and the GRS people will pick up on the changes that NSI has described below. Also, I hope that NSI continues to make more changes. It is good to see that the .COM TLD is moving away from the legacy roots and taking shape. If we all work together using the neighbor net approach, we can keep each other informed of these changes. Then, if someone has a question, people can go to the people that have been providing stewardship for a particular TLD. We should keep in mind that root server operators (RSCs) do not generally pay much attention to the day to day issues of a particular TLD. They have to look at all of the TLDs. People should not be surprised that RSCs may not be the best source of info about a particular TLD. Jim Fleming Unir Corporation - http://www.unir.com 0:201 .COM http://www.ntia.doc.gov/ntiahome/domainname/130dftmail/unir.txt
To: dholtz at internic.net ("David H. Holtzman") cc: nanog at merit.edu Subject: open letter (Re: NSI Bulletin 098-013 | gtld server) From: Paul Vixie <paul at vix.com> Date: 05 Oct 1998 22:25:50 -0700 Lines: 28 Sender: owner-nanog at merit.edu
I have three questions about:
dholtz at internic.net ("David H. Holtzman") writes:
In a continuing effort to enhance service to the community, Network Solutions has added another gTLD server, f.gtld-servers.net (207.159.77.18) at PAIX, Palo Alto, CA. The server will be operation in the next couple of days. This server will serve the .com, .net and .org domains only. _____________________________________ David H. Holtzman (dholtz at internic.net) Sr Vice President of Engineering Network Solutions, Inc.
1. As the operator of F.ROOT-SERVERS.NET, which is also at PAIX, I'm curious to know whether your reselection of the letter "F" in your host's name indicates a relationship between your "F" and my "F"?
2. In the past, changes in the COM delegation have been made via IANA. Since IANA was not involved in this announcement, should I interpret this as a unilateral move on NSI's part?
3. Does NSI still think of COM, NET, and ORG as its intellectual property? And is this belief bolstered in some way by the ICANN announcements? -- Paul Vixie La Honda, CA "Many NANOG members have been around <paul at vix.com> longer than most." --Jim Fleming pacbell!vixie!paul (An H.323 GateKeeper for the IPv8 Network) --
-------- Logged at Wed Oct 7 01:07:40 MET DST 1998 ---------