- Test - lists.nanog.org

RE: F.Root-Servers.net and bogus data
by Jim Fleming 25 Feb '97

25 Feb '97

On Monday, February 24, 1997 5:51 PM, Eric Germann[SMTP:ekgermann@cctec.com] wrote: @ At 05:23 PM 2/24/97 -0600, Jim Fleming wrote: @ >If you are using the new TRUE Root Name Servers... @ > @ >J.ROOT-SERVERS.NET @ >K.ROOT-SERVERS.NET @ >L.ROOT-SERVERS.NET @ >M.ROOT-SERVER.NET @ > @ @ @ I can't change the whole Internet overnight. I obviously can resolve @ myself since I go to my own DNS, not needing a root server. But @ statistically, people have an even chance of hitting the Heretics. @ Henceforth, the need to update it. I like the idea of a TXT record or a @ page for contacts at www.root-servers.net Seem like logical solutions. @ I also like the idea of using TXT records and the DNS system in general for more "whois-like" functions. If you ask me, I will provide more detailed proposals. I will not post them to this list to keep the traffic to a minimum. As for as "Heretics", I think the servers above are going to be RFC 2010 compliant. It may not be good to resort to name calling until you have read 2010. @@@@@@@@@@ Network Working Group B. Manning Request for Comments: 2010 ISI Category: Informational P. Vixie ISC October 1996 Operational Criteria for Root Name Servers Status of this Memo This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind. Distribution of this memo is unlimited. Abstract This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. @@@@@@@@@@@@@-- Jim Fleming Unir Corporation e-mail: JimFleming(a)unety.net JimFleming(a)unety.s0.g0 (EDNS/IPv8)

1 0

RE: F.Root-Servers.net and bogus data
by Eric Germann 24 Feb '97

24 Feb '97

At 05:23 PM 2/24/97 -0600, Jim Fleming wrote: >If you are using the new TRUE Root Name Servers... > >J.ROOT-SERVERS.NET >K.ROOT-SERVERS.NET >L.ROOT-SERVERS.NET >M.ROOT-SERVER.NET > I can't change the whole Internet overnight. I obviously can resolve myself since I go to my own DNS, not needing a root server. But statistically, people have an even chance of hitting the Heretics. Henceforth, the need to update it. I like the idea of a TXT record or a page for contacts at www.root-servers.net Seem like logical solutions.

1 0

RE: F.Root-Servers.net and bogus data
by Jim Fleming 24 Feb '97

24 Feb '97

On Monday, February 24, 1997 4:50 PM, Michael Handler[SMTP:handler@sub-rosa.com] wrote: @ In <3.0.32.19970224171008.00727978(a)207.87.243.20>, @ Eric Germann <ekgermann(a)cctec.com> wrote: @ @ > In the process of switching ISP's, I sent some updates off to InterNIC last @ > friday. The new SOA's are in place on all root servers except for @ > f.root-servers.net. Mail to hostmaster(a)internic.net yields no response @ > (who knows, they could be using f.....) @ @ handler@jumpgate ~$ check_soa com. | grep F @ F.ROOT-SERVERS.NET has serial number 1997021900 @ @ hostmaster(a)internic.net is only for updating your data on the master @ root servers. The master root has performed the updates, but @ F.ROOT-SERVERS.NET hasn't loaded new "COM." data since Wednesday @ of last week. (Sorry, Paul). @ If you are using the new TRUE Root Name Servers... J.ROOT-SERVERS.NET K.ROOT-SERVERS.NET L.ROOT-SERVERS.NET M.ROOT-SERVER.NET ....in your root.cache file, then you do not have to get involved with F.ROOT-SERVERS.NET. The Legacy Root Name Servers are being migrated to become Top Level Domain (TLD) Name Servers. If you "dig" at the TRUE Root Name Servers above for a domain in .COM, all you will get is a referral to the .COM TLD Name Servers which are shown below: =============================================== ; <<>> DiG 2.1 <<>> @j.root-servers.net unety.com ; (1 server found) ;; res options: init recurs defnam dnsrch ;; got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 10 ;; flags: qr rd; Ques: 1, Ans: 0, Auth: 9, Addit: 9 ;; QUESTIONS: ;; unety.com, type = A, class = IN ;; AUTHORITY RECORDS: COM. 518400 NS A.ROOT-SERVERS.NET. COM. 518400 NS H.ROOT-SERVERS.NET. COM. 518400 NS B.ROOT-SERVERS.NET. COM. 518400 NS C.ROOT-SERVERS.NET. COM. 518400 NS D.ROOT-SERVERS.NET. COM. 518400 NS E.ROOT-SERVERS.NET. COM. 518400 NS I.ROOT-SERVERS.NET. COM. 518400 NS F.ROOT-SERVERS.NET. COM. 518400 NS G.ROOT-SERVERS.NET. ;; ADDITIONAL RECORDS: A.ROOT-SERVERS.NET. 3600000 A 198.41.0.4 H.ROOT-SERVERS.NET. 3600000 A 128.63.2.53 B.ROOT-SERVERS.NET. 3600000 A 128.9.0.107 C.ROOT-SERVERS.NET. 3600000 A 192.33.4.12 D.ROOT-SERVERS.NET. 3600000 A 128.8.10.90 E.ROOT-SERVERS.NET. 3600000 A 192.203.230.10 I.ROOT-SERVERS.NET. 3600000 A 192.36.148.17 F.ROOT-SERVERS.NET. 3600000 A 192.5.5.241 G.ROOT-SERVERS.NET. 3600000 A 192.112.36.4 ;; Total query time: 62 msec ;; FROM: doorstep.unety.net to SERVER: j.root-servers.net 198.41.0.10 ;; WHEN: Mon Feb 24 17:07:56 1997 ;; MSG SIZE sent: 27 rcvd: 334 =============================================== In summary, once you move your root.cache "up" a level to the TRUE Root Name Servers, then you can forget about who is serving each Top Level Domain. You will note that the above .COM servers do not list the new TRUE Root Name Servers. That would defeat the purpose of deploying the new TRUE Root Name Servers which will only provide referrals to TLD Name Servers. -- Jim Fleming Unir Corporation e-mail: JimFleming(a)unety.net JimFleming(a)unety.s0.g0 (EDNS/IPv8)

1 0

A beginning to control SPAM..
by Rodney Joffe 24 Feb '97

24 Feb '97

Ladies and Gentlemen - and others :-) In the 'normal' world there exists a problem that you've all experienced - it's commonly known as "junk" mail., and "junk telephone" calls. As you all probably know (you're all so bright) before you can go after someone for causing you harm, they have to break a law, or a rule. The Federal Goverment, through various bodies (FCC and FTC) has enacted certain rules that categorize certain unsolicited forms of communication (mail, calls, fax) as being *wrong*. They are helped by an international body that (unlike us!) actually has enormous lobbying power. The body is a non-profit (501.c.3 I think) known as the Direct Marketing Association http://www.the-dma.org . This body has almost every major and minor direct marketer as a member, an enormous operating budget, and a pot load of clout. They've helped the feds draft rules. And their members have their sights aimed at the 'net. Us. They believ(ed) that we'd make a great medium for them to send their advertising (spam). Over the last year, I've managed to make them sensitive to the fact that this is *not* a good idea. Of course, I don't carry that much weight. But they have realized that it would be easier to work with us than against us. As a result, they have drafted the following position paper and rfc, and I volunteered to post it here so that you can know where to go to make your thoughts heard. Ignore the date.... it is still open for comment. I urge you to respond to them. They have the clout to influence a lot of the people who are already causing us problems And please remember; I am *only the messenger, trying to help stop the spamming*. At the conclusion of this email, I am in the same position as y'all -- an unhappy recipient of SPAM. So don't try and involve me in the argument because I brought a partial suggestion. Thanks Rodney Joffe Genuity Inc., a Bechtel company http://www.genuity.net DIRECT MARKETING ASSOCIATION, INC. 1120 Avenue of the Americas, New York, NY 10036-6700 · 212 768-7277 Fax: 212 768-4546 http://www.the-dma.org H. ROBERT WIENTZEN PRESIDENT &. CEO DIRECT MARKETING ASSOCIATION E-MAIL PREFERENCE SERVICE REQUEST FOR INFORMATION DECEMBER 1996 Founded in 1917, the Direct Marketing Association (DMA) is the largest trade association for businesses interested in direct marketing and database marketing. A long-time champion of consumer choice, the DMA has historically sought to ensure that consumers are afforded opportunities both to learn about products and services of interest to them and to express their preferences regarding marketers' use and dissemination of information about them. The sole purpose of this Request for Information is to determine the feasibility of developing a service that will enable U.S. consumers to opt out of receiving unsolicited commercial e-mail. The service would provide the same benefit to consumers that DMA's existing preference services provide in that they enable consumers to reduce the amount of advertising mail or telephone marketing calls they receive at home. This service could be modeled after DMA's existing services, described below. DMA anticipates that this Request for Information is expected to lead to a request for proposals if DMA, at its sole discretion, determines such request to be in its best interest. However, DMA does not request proposals at this time, nor can it make assurances that it will do so in the future. Please return information responses by close of business January 20, 1997, to the Direct Marketing Association, 1111 19th Street, NW, Suite 1100, Washington, D.C. 20036, Attention: Patricia Faley, Vice President for Consumer Affairs. Please direct all inquiries to Patricia Faley at (202) 955-5030 (telephone) or (202) 955-0085 or e-mail at: patriciafaley(a)the-dma.org. BACKGROUND The DMA is the largest trade association for businesses interested in direct marketing, which includes the use of databases. DMA represents mere than 3,000 United States corporations as well as 600 corporations from 47 other countries. DMA members use all media to reach their customers and prospects - mail, telephone, direct response TV, radio, home shopping networks, as well as cyberspace. A recently released three-year study conducted by The WEFA Group found that in 1995 American consumers purchased nearly $600 billion in goods and services, and American businesses purchased nearly another $500 billion in goods and services, via direct response (all media). Over the years, DMA has initiated an array of consumer protection and education programs. Among them, DMA adopted guidelines for ethical business practice and established a peer review committee to respond to cases of alleged guideline violations brought to its attention. It published and distributed in 25 countries the DMA Fair Information Practices Manual - a step-by-step "how to" manual designed to assist businesses in developing and implementing companies' policies and procedures on the use of information about consumers. And it established the Mail Preference Service and Telephone Preference Service, which are offered free of charge to give consumers the ability to remove their names individually from the lists of major marketers, which reduces the amount of advertising mail and telephone marketing calls consumers receive at home. Although many direct marketers are somewhat new to the business of marketing on-line, DMA established a dialogue with its members, policymakers, and cyber consumers about marketing in the new media. It has disseminated to its members privacy principles developed jointly with the Interactive Services Association, participated in Federal Trade Commission workshops, and established a parents' page on its Web site with hyperlinks to the sites of software vendors offering programs that enable parents to take a more active role over what their children view and do on the Internet. DMA also is developing a "how to" package, which can be downloaded from its Web site, that will enable marketers easily to create accurate and effective privacy notices for their Web sites. ***** In order to understand DMA's consumer choice philosophy and to understand DMA's requirements for an E-Mail Preference Service (E-MPS), it is helpful first to examine briefly the current Mail Preference Service (MPS) and Telephone Preference Service (TPS). Please note that it is not important that an E-MPS be identical in structure to the existing services. In light of the capabilities of the new technologies, DMA welcomes all suggestions for accomplishing the goal of reducing unwanted mail. MPS/TPS DMA established the MPS name removal file in 1971 to provide consumers with an opportunity to have their names removed from many national mailing lists. DMA established TPS, a companion service, in 1985 to answer increased consumer complaints and regulatory concerns regarding the use of the telephone to market goods. Consumers are not charged for registering with MPS or TPS. Consumers register with MPS or TPS by postal mail. They register directly; third-party requests are not processed because it is important that each consumer has clearly made his or her own choice to reduce their mail or call. Typically, consumers will not notice a decrease in their volume of mail or number of calls until approximately 3-4 months after their names are entered into the MPS/TPS systems. Consumer names remain on MPS/TPS for five years and may be renewed. When consumers register with MPS/TPS, their names are placed on a name removal file. This "do not mail" or "do not call" file is made available to business subscribers on either a monthly or quarterly basis. Subscribers receive a "master" MPS and/or TPS magnetic tape in January of each year. The January tape is complete, containing the names of all consumers registered with the services. Upon receipt of the January tape, all tapes from the previous year are discarded. The January tape is cleaned of all records over five years old. Each subsequent quarterly and monthly tape contains only those consumers' names and addresses added during that month or quarter. Businesses subscribing mid-year receive the complete tape plus updates. List owners should use MPS/TPS before releasing any lists for rental or exchange. A company that receives a rental list, which has not been run against MPS/TPS, should do so before mailing or calling. Many companies also use MPS/TPS through service bureaus. Service bureaus often run MPS and TPS automatically against client tapes. DMA guards against unauthorized use of the name removal file through several means. First, before receiving the MPS or TPS tapes, potential subscribers are required to sign contractual provisions limiting use of the services to name-removal purposes only. Second, both MPS and TPS are protected by sophisticated decoy systems designed to detect any misuse or unauthorized access. E-MPS The objective of an E-MPS would be to provide a service that enables individual U.S. consumers to reduce significantly the amount of unsolicited commercial e-mail they receive. E-MPS probably will require at least four key phases for DMA: registration and acknowledgment, data maintenance, data distribution and data coordination with other countries. It is anticipated that consumers will register either at the DMA Web site or via e-mail. The DMA forms for Internet registration at its Web site could be duplicated for registration via email by consumers who use dedicated e-mail services. It is essential that the registration data be secure in transmission, storage, and maintenance. Consumers will then receive a registration acknowledgment, which would include a restatement of E-MPS policies and several reminders (e.g., that e-mail addresses must be updated for E-MPS to be effective). The registration information will then be forwarded through secure means to a Data Maintenance Center that maintains the data. Data maintenance will include elimination of duplicate records and checking of e-mail addresses to confirm that they are still valid. It may also include deleting addresses that are more than a predetermined number of years old. The Data Maintenance Center will then forward the E-MPS data to the Data Distributor through secure means. The Data Distributor will be responsible for distributing the E-MPS data to authorized subscribers. The encrypted E-MPS data will be accessible via electronic transfer to parties with a valid password. Subscribers will be able to access complete files or only updates, which they would be expected to download before each e-mail campaign or often enough to ensure that they are being responsive to consumer requests. There will be other ongoing activities in the operation of E-MPS. For example, the Data Maintenance Center or some other entity might periodically remind registered consumers of their status and furnish them with an opportunity to remove their e-mail address from E-MPS. The Data Distributor will also be responsible for operating a system designed to detect any misuse or unauthorized access. For these and other reasons, it would be desirable to consolidate all of the E-MPS functions so as to enable consumers to register directly with the entity responsible for data maintenance and distribution. DMA is also interested in determining the feasibility of offering consumers more flexibility in their opt out choices relative to e-mail than which currently exists in MPS and TPS. For example, what technological capabilities would be needed to offer consumers selective opt-out, that is, the option of receiving e-mail from catalogue companies, but not from auto parts manufacturers. To further international cooperation in the implementation of the E-MPS objective, it is anticipated that there will be both a global E-MPS Web site and national E-MPS Web sites. The global E-MPS Home Page will have language options and point to the national E-MPS Home Pages where registration will take place. DMA has discussed creation of a global E-MPS with direct marketing representatives from 20 countries. They are: Argentina, Australia, Brazil, Canada, Finland, France, Hong Kong, India, Ireland, Japan, Mexico, the Netherlands, New Zealand, the Philippines, Singapore, South Africa, Spain, Sweden, Thailand, and the United Kingdom. Over time, we expect that other countries would join our discussions and our global self-regulatory network. REQUEST FOR INFORMATION DMA seeks information that will help it determine the feasibility of the funding, the development and the implementation of an E-MPS for U.S. residents and, separately, of a global E-MPS. The information provided by respondents to this Request for Information is expected to lead to a request for bids if DMA, at its sole discretion, determines that it is in DMA's best interest to request such bids or proposals. However, DMA makes no assurances that it will request bids or proposals at any time in the future. Information responses should not contain proprietary or sensitive information, and DMA assumes no liability for protecting or safeguarding any information provided. The following questions explore issues DMA expects to address in implementing an E-MPS. Commentary on additional issues is welcome. 1. The combined MPS/TPS files contain about 3.5 million names. How many persons residing in the U.S. might be expected to register for E-MPS during the first two years of its existence? Explain. 2. What information would be needed from consumers? Would it suffice for registration to collect e-mail addresses, or would other identifiers such as name and/or country be needed? 3. What would be some of the approaches to verifying the identity of the person registering for the service? How could DMA ensure that the person requesting to opt out is the actual owner of the e-mail address? 4. Due to the economics of sending bulk e-mail (unlike postal mail, the cost between sending one e-mail solicitation and sending 1,000 nay be inconsequential), it is important that the process by which e-mail addresses are removed from lists be inexpensive and easy for the e-mailer to use. To that end, the automating of the system for registering e-mail addresses and disseminating the list is desirable. To what degree would it be possible to automate the process of collecting and accessing or disseminating e-mail suppression information? What are the pros and cons of doing this? What other automation issues arise? 5. What are the special requirements for security other than using seed names to detect misuse? How would other systems work? 6. What reports should the Data Maintenance Center furnish the DMA at a minimum? 7. What are the global implications of such a service? In a medium such as the Internet, is it feasible to create a localized system Out will serve only residents of a particular geographic area, even if through a common standard the system is capable of interacting with the systems of other countries? Or should one entity operate a global E-MPS for all of the direct marketing associations of the various countries? 8. What are your initial estimates, of costs for this E-MPS project if limited to U.S. residents? If extended globally? 9. What would be the timing for implementation of E-MPS (a) nationally and (b) globally? 10. What is the feasibility of offering consumer flexibility in their opt out choices. For example the ability to reduce e-mail from a certain category of marketer. 11. In addition, we welcome any other suggestions or comments that responders might have to address this issue.

1 0

Flemming posts (*F)
by Todd Graham Lewis 24 Feb '97

24 Feb '97

After adding the .procmailrc entry which someone was so kind as to send to the list last week, I have fortunately not had to read a single word of Jim Flemming's. (My /dev/null keeps complaining what a raving loon he is, but I've /dev/null'ed mail from my /dev/null, too. Of course, my CPU usage is at 100%, and I'm not even running NT, but I digress.) Anyway, Nirvana still awaits, because I still from time to time open a letter from someone responding to Jim Fleming, and are therefore subjected to his lunacy (although much scaled back) as these poor souls continue to play windmill to his Rocinante's rear. Therefore, I make a small request. If you're engaged in a discussion with Jim Fleming, or responding to him, or talking about him, could you please place the "WARNING: FLEMING-RELATED MESSAGE" sticker on the end of your subject line? In ascii, it's rendered thusly: (*F) This message has been so tagged for demonstration purposes. Again, thanks to the kind soul who contributed the .procmailrc line, and thanks in advance to the new participants in the Jim Fleming Warning Network. __ Todd Graham Lewis Mindspring Enterprises tlewis(a)mindspring.com

1 0

FW: Behind the scenes...
by Jim Fleming 24 Feb '97

24 Feb '97

---------- From: Jim Fleming[SMTP:JimFleming@unety.net.] Sent: Saturday, February 15, 1997 11:32 AM To: 'New Newdom' Subject: Behind the scenes... For over 20 years I have been designing serious online information systems. I was fortunate to spend much of that time at AT&T Bell Laboratories as an employee and a consultant. I am proud of the fact that I was able to help launch the Videotex industry and that some of the technology that AT&T patented on my behalf was used in the early Prodigy systems. For the past couple of years, I have become more involved in the behind the scenes activity of the Internet. Like many people, I have used the facilities for many years without much concern for who handled the governance needed to keep the network moving in a positive direction that benefits all people on earth and does not discriminate and degenerate like many societies on earth. I am disappointed to report that the behind the scenes Internet of 1997 looks more like a communist/fascist republic than the democratic system in the U.S. that helped to create the Internet. In my opinion, this is partly because a few individuals have been allowed to rise to positions of visibility and power without the normal checks and balances that are present in a democracy. We now have a situation where the so-called "leaders" of the Internet support people who run around "blacklisting" and denying service to people at the drop of a hat. We see the U.S. Government, via the NSF, funding people who are clearly the Internet equivalent of the mafia. We see prominent Internet societies endorsing people who openly and publicly suggest that people's parents be "killed with fire axes". We see those groups claiming to have the support of the Whitehouse, which I doubt endorses such violence. The list goes on. When I first observed this situation, I will admit that I was naive. I assumed that society would see these problems and quickly correct these situations. I am disappointed to report that not only is this not happening, it is getting worse. It appears that the only solution for rational adults (especially in the U.S.) is to turn and walk away. As this happens, the problem increases, because, what remains are these ego-maniac dictators who now infect the young people launching their careers in the tele- communications industry. Some of these young people then become ISPs, capture the attention of the public, and continue to propogate a system that will clearly lead to large scale social problems around the world. Another solution is to create a new Internet that is "rooted" in democratic governments that have served great countries like the U.S. for many years. It is somewhat ironic that such a new system would have to be created as an alternative to the dictators currently being funded by the U.S. taxpayers via NSF grants and non-profit, tax-avoiding, companies. The system would also have to be created in the face of wide-spread opposition from young people who have already been polluted to think that everything the U.S. does is not in their interest, except for their tuition and salaries paid via government grants. To create a new Internet, new servers and networks are not required. What is required is democractic governance. Because I believe in the U.S. system of democracy and I truely believe that 99.9% of society wants to "do the right thing", I still have hope that democratic societies will take a hard look behind the scenes of the Internet to see the "society" that is pulling the strings. I have faith that the real society and real governments will soon step forward to cut the ties to the dictators and their societies. This will help to ensure that children and adults everywhere have a chance to enjoy the wonderful resources that the Internet can provide in a truely democratic Internet society (small s). Thank you for your time... -- Jim Fleming Unir Corporation e-mail: JimFleming(a)unety.net JimFleming(a)unety.s0.g0 (EDNS/IPv8)

6 5

How to spam nicely?
by Joseph C. Pistritto 24 Feb '97

24 Feb '97

Ok, now that I have your attention. I'd like suggestions from members of the community on the best way to do bulk mailings to our user base (not product recommendations specifically or anything like that), but obvious pitfalls to watch out for. Our "mass mailing" policy in general has been pretty net-friendly, in that we only send mail to people who have registered our product at the address they gave us when they did so (we don't buy lists, etc.), and might be interested in the specific thing we're telling them about, and we only attempt to send each person mail once. We also don't do this very often and keep our mailing lists pretty current. So, any suggestions to make our having to send a bunch of mail more pleasant for the rest of the net? If any of you out there have specific experience with bulk mailing, I'd love to hear about it to avoid stepping on land mines others have already "detected", etc. Thanks in advance. -jcp-

4 3

The Cidr Report
by Tony Bates 24 Feb '97

24 Feb '97

2 1

Career Opportunity/Technical Challenge
by netsrch＠getback.hartley.on.ca 23 Feb '97

23 Feb '97

We are a research firm working with a client that is a major player in the Internet and WAN remote access business. If you would be interested in exploring career opportunities in network engineering with this organization, please click on mailto:netsrch@getback.hartley.on.ca and you will receive additional information. Net Research P.S. We've been careful to ensure that this organization is not your present employer

2 1

NSF-paid ideal
by Jim Fleming 23 Feb '97

23 Feb '97

On Saturday, February 22, 1997 9:24 AM, Kim Culhan[SMTP:kimc@w8hd.org] wrote: @ <snip> @ Jim, please explain your NSF-paid ideal. @ I assume you mean this "NSF-paid" ideal...? If you want to assemble a real "Blue Ribbon Panel" that represents the real Internet society, I suggest that you start with some or all of the people below. These are the people who control the popular Root Name Servers and are the people mandated by the people to "do the right thing". They are also some of the people supported by U.S. taxpayers dollars to make sure that federal government resources such as the Root Name Servers are used properly according to the laws in the United States. We are rapidly approaching March 1, 1997. There will be one year left on the InterNIC agreements developed by the National Science Foundation (NSF). Everyone needs to work together to make sure that those agreements remain stable for one more year and that plans are made to ensure that any transitions are smooth and do not impact the stability of the Internet. The current ARIN attempts to fragment the InterNIC are not in the best interest of the Internet. Instead, the InterNIC should be kept in tact and used as an educational model to help create additional "NICs" across the United States to spread the wealth and jobs around and to ensure better stability via distributed management. I have suggested that the NSF use the $12.6 million to help launch 49 additional NICs, one in each state except for Virginia. By March of 1998, hopefully enough NICs will be operational to allow the current InterNIC as we know it to take its place with the others as a state NIC controlled by the people of Virginia. Many people have worked hard over the past couple of years to demonstrate that cooperating and competing regional NICs can coexist. The technology is well understood and with the stewardship of some or all of the people below, I am confident that the original NSF plan to expand the NICs can be accomplished by the time the NSF agreements with AT&T and Network Solutions, Inc. end. In order to get the regional NICs up to speed, I suggest that states follow the NSF InterNIC model and "ousource" the work to regional companies that have demonstrated their expertise in not only Internet technology but also the emerging registry industry. I suggest that these companies work with their state governments to gain support to work with the elected officials below to get things moving. There is only one year left. Time is getting short. Rather than have anyone rush into dismantling the InterNIC why not join together to clone the InterNIC, not once, but at least 49 times to help the Internet grow. Once this is demonstrated, then obviously the lessons learned will help fuel international growth. No one will be left out. If other countries want to join in this effort, I suggest that they follow a similar plan. Think global but start local. It is the only way that you will make any real progress. I am sure that many people in the U.S. will be glad to lend a hand to get things moving. Hopefully, there will be many examples and more educational programs developed as these efforts unfold. There is no reason why anyone should be left out but there is also no reason why people should hold back waiting for people to catch up. With the clock ticking and $12.6 million in the bank, it is time to duplicate the prototype in Virginia in every state and each country. It is not time to dismantle the prototype. If that occurs then much of the knowledge will be lost and the money the U.S. taxpayers spent to build the InterNIC will be wasted. Again, the following people have the mandate of the people to make sure that money and the efforts are not wasted. They work daily to maximize the return on the taxpayer's investment. Let them know that you want to work with them to make sure you also benefit from those efforts in your states and countries. Thank you for your time... @@@@@@@@@@@@@@@@@@@@@@@@ President Bill Clinton and Vice President Al Gore http://www.whitehouse.gov National Science Board (NSB) http://www.nsf.gov/nsb/nsb.htm The NSB has dual responsibilities as: . National science policy advisor to the President and the Congress . Governing body for the National Science Foundation Chairman NSB - Dr. Richard N. Zare, Stanford University rnz(a)chemistry.stanford.edu http://www-leland.stanford.edu/group/Zarelab/ Office of Inspector General of the NSF (also links to Congress) http://www.nsf.gov/oig/oig.htm Inspector General - Linda G. Sundro - lsundro(a)nsf.gov Investigator - Clara Kuehn - ckuehn(a)nsf.gov National Science Foundation Neal Lane - nlane(a)nsf.gov <http://www.nsf.gov/od/lpa/forum/lane/quscipol.htm> Juris Hartmanis - jhartman(a)nsf.gov <http://www.cise.nsf.gov/oad/jhartman.html> George Strawn - gstrawn(a)nsf.gov <http://www.cise.nsf.gov/ncri/Georgehome.html> Don Mitchell - dmitchel(a)nsf.gov <http://www.cise.nsf.gov/ncri/Donhome.html> ===== @@@@@ http://www.fnc.gov/mission.html "The FNC supports the goals of the CIC, particularly those related to building the national information infrastructure (NII). It also seeks to address Federal technology transition goals and allow the operational experiences of FNC agencies to influence future Federal research agendas. It also contributes funds to important Internet infrastructure organizations, such as the Internet Engineering Task Force (IETF), Internet Assigned Number Authority (IANA), and the Computer Emergency Response Team (CERT)." @@@@@ http://www.fnc.gov/FNC_Members.html Federal Networking Council George Strawn - Chairman GSTRAWN(a)NSF.GOV Walter Wiebe - Executive Director WWIEBE(a)NSF.GOV Bruce Almich ALMICH.BRUCE(a)EPAMAIL.EPA.GOV Bruce Bottomley BBB(a)ROMULUS.NCSC.MIL Dick desJardins DESJARDI(a)EOS.NASA.GOV Frank Hartel HARTEL(a)BOX-H.NIH.GOV Craig Hunt CHUNT(a)NIST.GOV Pamela G. Kruzic PJK(a)NRC.GOV Henry Lai HENRY.LAI(a)GSA.GOV Fred Lee FLEE(a)NSF.GOV Fred Long FLONG(a)SUN1.WWB.NOAA.GOV Hilarie Orman HORMAN(a)DARPA.MIL Camillo J. Pasquariello PASQUARC(a)NCR.DISA.MIL Alexis Poliakoff ALEX_POLIAKOFF(a)ED.GOV Ken Roko KROKO(a)USAID.GOV Elaine Stout ESTOUT(a)USGS.GOV @@@@@ http://www.fnc.gov/FNCAC.html The Federal Networking Council Advisory Committee (FNCAC) is chartered by the National Science Foundation to provide the FNC with technical, tactical, and strategic advice from the constituencies involved in the NREN Program..." FNCAC Members Dr. Sidney Karin KARIN(a)SDSC.EDU Dr. George Brandenburg BRANDENBURG(a)HUHEPL.HARVARD.EDU Dr. Henriette Avram AVRAM(a)IVORY.EDUCOM.EDU Mr. Jim Beall, Jr. BEALL(a)VNET.IBM.COM Mr. Alan Blatecky ALANB(a)MCNC.ORG Mr. Matt Blaze MAB(a)RESEARCH.ATT.COM Ms. Susan Estrada SESTRADA(a)ALDEA.COM Dr. Kenneth S. Flamm FLAMM(a)BROOK.EDU Dr. John Gage JOHN.GAGE(a)ENG.SUN.COM Ms. Carol Henderson CCH(a)ALAWASH.ORG Dr. Kenneth J. Klingenstein KJK(a)SPOT.COLORADO.EDU Mr. Richard Liebhaber 2714743(a)MCIMAIL.COM Mr. Stu Loken SCLOKEN(a)LBL.GOV Dr. Paul Mockapetris PVM(a)SOFTWARE.COM Mr. Robert G. Moskowitz RGM3(a)IS.CHRYSLER.COM Dr. Ike Nassi NASSI(a)SCRUZNET.COM Mr. Carl Edward Oliver OLIVERCE(a)ORNL.GOV Dr. Stewart Personick SDP(a)BELLCORE.COM Mr. Thomas C. Rindfleisch THOMAS_RINDFLEISCH(a)MEDMAIL.STANFORD.EDU. Mr. Mike Roberts ROBERTS(a)EDUCOM.EDU Ms. Connie D. Stout CSTOUT(a)TENET.EDU Brigadier General Harold Thompson THOMPSON(a)ICN.STATE.IA.US Dr. Stephen Wolff SWOLFF(a)CISCO.COM @@@@@ U.S. Senate e-mail addresses Alabama - Shelby, Richard C. (R) - senator(a)shelby.senate.gov Alaska - Stevens, Ted (R) - senator_stevens(a)stevens.senate.gov Arizona - Kyl, Jon (R) - info(a)kyl.senate.gov Arizona - McCain, John (R) - senator_mccain(a)mccain.senate.gov Arkansas - Bumpers, Dale (D) - senator(a)bumpers.senate.gov Arkansas - Hutchinson, Tim (D) - senator.hutchinson(a)hutchinson.senate.gov California - Boxer, Barbara (D) - senator(a)boxer.senate.gov California - Feinstein, Dianne (D) - senator(a)feinstein.senate.gov Connecticut - Dodd, Christopher J. (D) - sen_dodd(a)dodd.senate.gov Connecticut - Lieberman, Joseph I. (D) - senator_lieberman(a)lieberman.senate.gov Delaware - Biden, Joseph R., Jr. (D) - senator(a)biden.senate.gov Florida - Graham, Bob (D) - bob_graham(a)graham.senate.gov Georgia - Coverdell, Paul (R) - senator_coverdell(a)coverdell.senate.gov Hawaii - Inouye, Daniel K. (D) - senator(a)inouye.senate.gov Idaho - Craig, Larry E. (R) - larry_craig(a)craig.senate.gov Idaho - Kempthorne, Dirk (R) - dirk_kempthorne(a)kempthorne.senate.gov Illinois - Moseley-Braun, Carol (D) - senator(a)moseley-braun.senate.gov Iowa - Grassley, Chuck (R) - chuck_grassley(a)grassley.senate.gov Iowa - Harkin, Tom (D) - tom_harkin(a)harkin.senate.gov Kansas - Brownback, Sam (R) - sam_brownback(a)brownback.senate.gov Kentucky - Ford, Wendell H. (D) - wendell_ford(a)ford.senate.gov Kentucky - McConnell, Mitch (R) - senator(a)mcconnell.senate.gov Louisiana - Breaux, John B. (D) - senator(a)breaux.senate.gov Maine - Collins, Susan (R) - senator(a)collins.senate.gov Maine - Snowe, Olympia J. (R) - olympia(a)snowe.senate.gov Maryland - Mikulski, Barbara A. (D) - senator(a)mikulski.senate.gov Maryland - Sarbanes, Paul S. (D) - senator(a)sarbanes.senate.gov Massachusetts - Kennedy, Edward M. (D) - senator(a)kennedy.senate.gov Massachusetts - Kerry, John F. (D) - john_kerry(a)kerry.senate.gov Michigan - Abraham, Spencer (R) - michigan(a)abraham.senate.gov Michigan - Levin, Carl (D) senator(a)levin.senate.gov Minnesota - Grams, Rod (R) - mail_grams(a)grams.senate.gov Minnesota - Wellstone, Paul D. (D) - senator(a)wellstone.senate.gov Mississippi - Cochran, Thad (R) - senator(a)cochran.senate.gov Missouri - Ashcroft, John (R) - john_ashcroft(a)ashcroft.senate.gov Missouri - Bond, Christopher S. (R) - kit_bond(a)bond.senate.gov Montana - Baucus, Max (D) - max(a)baucus.senate.gov Montana - Burns, Conrad R. (R) - conrad_burns(a)burns.senate.gov Nebraska - Kerrey, J. Robert (D) - bob(a)kerrey.senate.gov Nevada - Bryan, Richard H. (D) - senator(a)bryan.senate.gov Nevada - Reid, Harry (D) - senator_reid(a)reid.senate.gov New Hampshire - Gregg, Judd (R) - mailbox(a)gregg.senate.gov New Hampshire - Smith, Bob (R) opinion(a)smith.senate.gov New Jersey - Lautenberg, Frank R. (D) - frank_lautenberg(a)lautenberg.senate.gov New Mexico - Bingaman, Jeff (D) - senator_bingaman(a)bingaman.senate.gov New Mexico - Domenici, Pete V. (R) - senator_domenici(a)domenici.senate.gov New York - D'Amato, Alfonse M. (R) - senator_al(a)damato.senate.gov New York - Moynihan, Daniel Patrick (D) - senator(a)dpm.senate.gov North Carolina - Faircloth, Lauch (R) - senator(a)faircloth.senate.gov North Carolina - Helms, Jesse (R) - jesse_helms(a)helms.senate.gov North Dakota - Dorgan, Byron L. (D) - senator(a)dorgan.senate.gov Ohio - DeWine, Mike (R) - senator_dewine(a)dewine.senate.gov Oklahoma - Nickles, Don (R) - senator(a)nickles.senate.gov Oregon - Wyden, Ron (D) - senator(a)wyden.senate.gov Pennsylvania - Santorum, Rick (R) - senator(a)santorum.senate.gov Pennsylvania - Specter, Arlen (R) - senator_specter(a)specter.senate.gov Rhode Island - Chafee, John H. (R) - senator_chafee(a)chafee.senate.gov South Carolina - Hollings, Ernest F. (D) - senator(a)hollings.senate.gov South Carolina - Thurmond, Strom (R) - senator(a)thurmond.senate.gov South Dakota - Daschle, Thomas A. (D) - tom_daschle(a)daschle.senate.gov Tennessee - Frist, William H. (R) - senator_frist(a)frist.senate.gov Tennessee - Thompson, Fred (R) - senator_thompson(a)thompson.senate.gov Texas - Hutchison, Kay Bailey (R) - senator(a)hutchison.senate.gov Utah - Bennett, Robert F. (R) - senator(a)bennett.senate.gov Utah - Hatch, Orrin G. (R) - senator_hatch(a)hatch.senate.gov Vermont - Jeffords, James M. (R) - vermont(a)jeffords.senate.gov Vermont - Leahy, Patrick J. (D) - senator_leahy(a)leahy.senate.gov Virginia - Robb, Charles S. (D) senator(a)robb.senate.gov Virginia - Warner, John W. (R) - senator(a)warner.senate.gov Washington - Gorton, Slade (R) - senator_gorton(a)gorton.senate.gov Washington - Murray, Patty (D) - senator_murray(a)murray.senate.gov West Virginia - Byrd, Robert C. (D) - senator_byrd(a)byrd.senate.gov West Virginia - Rockefeller, John D., IV (D) - senator(a)rockefeller.senate.gov Wisconsin - Feingold, Russell D. (D) - senator(a)feingold.senate.gov Wisconsin - Kohl, Herb (D) - nator_kohl(a)kohl.senate.gov Wyoming - Enzi, Mike (R) - senator(a)enzi.senate.gov Wyoming - Thomas, Craig (R) - craig(a)thomas.senate.gov @@@@@@@@@@@@@@@@@ U.S. GOVERNMENT (NSF, etc.) Contact: Dr. George Strawn Division Director Division of Networking and Communication Research and Infrastructure National Science Foundation 4201 Wilson Boulevard, Room 1175 Arlington, VA 22230 Phone: (703) 306-1950 Fax: (703) 306-0621 Email: gstrawn(a)nsf.gov http://www.cise.nsf.gov/ncri/Georgehome.html NS.INTERNIC.NET 198.41.0.4 Network Solutions, Inc. (NS45-HST) AOS.ARL.ARMY.MIL 128.63.2.53 Army Research Laboratory (BRL-AOS) NS.NASA.GOV 192.203.230.10 Moffett Field (NS-NASA) NS.NIC.DDN.MIL 192.112.36.4 GSI (DIIS-NS) STATE UNIVERSITIES NS1.ISI.EDU 128.9.0.107 University of Southern California (ISI2) Contact: Dr. Stephen B. Sample President ADM 110 University of Southern California University Park, mc-0012 Los Angeles, CA 90089-0012 (213) 740-2111 http://www.usc.edu/cgi-bin/uscinfo/directory-2?STAF+6630 http://www.usc.edu/People/snailmail.html TERP.UMD.EDU 128.8.10.90 University of Maryland (UMD-TERP) Contact: Dr. William E. Kirwan President, University of Maryland at College Park <http://www.inform.umd.edu:8080/CampusInfo/Departments/PRES/> <http://inform.umd.edu/kirwan-biography.html> Legal Affairs Dr. J. Terrance Roach <mailto: troach(a)deans.umd.edu> U.S. PRIVATE INDUSTRY & INDIVIDUALS C.PSI.NET 192.33.4.12 Performance Systems International Inc. (C-NYSER) Contact: PSINet, Inc (PSI-NET-DOM) 510 Huntmar Park Drive Herndon, VA 22070 USA NS.ISC.ORG 192.5.5.241 Internet Software Consortium (ISC) Contact: Internet Software Consortium (ISC2-DOM) c/o UUNET Communications Services 3110 Fairview Park Drive Suite 570 Falls Church, VA 22042 Domain Name: ISC.ORG SWEDEN Contact: (See below) NIC.NORDU.NET 192.36.148.17 [No name] (NORDU) @@@@@@ SERVER NS.ISC.ORG 192.5.5.241 Internet Software Consortium (ISC) Hostname: F.ROOT-SERVERS.NET Address: 192.5.5.241 System: DEC ALPHA running BIND 4.9.5 Host Administrator: Vixie, Paul (PV15) paul(a)VIX.COM +1 415 747 0204 Domain Server Record last updated on 09-Oct-96. ------- SERVER NS.INTERNIC.NET 198.41.0.4 Network Solutions, Inc. (NS45-HST) 505 Huntmar Park Drive Herndon, VA 22070 Hostname: A.ROOT-SERVERS.NET Address: 198.41.0.4 System: SUN running SUNOS Host Administrator: Kosters, Mark A. (MAK21) markk(a)NETSOL.COM (703) 742-4795 (FAX) (703) 742-4811 Record last updated on 31-Aug-95. ------- SERVER NS1.ISI.EDU 128.9.0.107 University of Southern California (ISI2) Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292 Hostname: B.ROOT-SERVERS.NET Address: 128.9.0.107 System: ? running ? Host Administrator: Koda, Jim (JK7) koda(a)ISI.EDU 310) 822-1511 Record last updated on 12-Aug-95. ------- SERVER TERP.UMD.EDU 128.8.10.90 University of Maryland (UMD-TERP) Computer Science Center College Park, MD 20742 Hostname: D.ROOT-SERVERS.NET Address: 128.8.10.90 System: MICROVAX-II running UNIX Coordinator: Sneeringer, Gerry (GS307) sneeri(a)NI.UMD.EDU (301) 405-2996 domain server Record last updated on 12-Aug-95. ------- SERVER AOS.ARL.ARMY.MIL 128.63.2.53 Army Research Laboratory (BRL-AOS) Aberdeen Proving Ground, MD 21005-5066 Hostname: H.ROOT-SERVERS.NET Address: 128.63.2.53 System: SUN running UNIX Host Administrator: Fielding, James L. (JLF) jamesf(a)ARL.MIL (410)278-8929 (DSN) 298-8929 (410)278-6664 (FAX) (410)278-5077 domain server Record last updated on 17-Aug-95. ------- SERVER C.PSI.NET 192.33.4.12 Performance Systems International Inc. (C-NYSER) Hostname: C.ROOT-SERVERS.NET Address: 192.33.4.12 System: SUN running UNIX Coordinator: Administration, PSINet Domain (PDA4) psinet-domain-admin(a)PSI.COM (703) 904-4100 domain server Record last updated on 17-Apr-96. ------- SERVER NIC.NORDU.NET 192.36.148.17 [No name] (NORDU) Hostname: I.ROOT-SERVERS.NET Address: 192.36.148.17 System: SUN-4/60 running UNIX Coordinator: Rendahl, Matti [President] (MR164) matti(a)COMEDIA.SE +46 8 612 49 26 +46 70 533 13 56 (FAX) +46 8 612 49 36 Record last updated on 24-Aug-95. ------- SERVER NS.NASA.GOV 192.203.230.10 Moffett Field (NS-NASA) NASA Ames Research Center, Mail Stop 233-8 Moffett Field, CA 94035-1000 USA Hostname: E.ROOT-SERVERS.NET Address: 192.203.230.10 System: SUN running SUNOS Host Administrator, Coordinator: Schlapfer, Marcel (MS4039) marcel(a)NSIPO.NASA.GOV 1-415-604-0955 (FAX) 1-415-604-0036 domain server Record last updated on 25-Oct-96. ------- SERVER NS.NIC.DDN.MIL 192.112.36.4 GSI (DIIS-NS) Suite 200 14200 Park Meadow Dr. Chantilly, VA 22021 Hostname: G.ROOT-SERVERS.NET Address: 192.112.36.4 System: SUN running UNIX Coordinator: McCollum, Robert W. (RM584) bobm(a)NIC.DDN.MIL (703) 802-8476 (FAX) (703) 802-8376 Root Domain Server Record last updated on 18-Aug-95. ------- -- Jim Fleming Unir Corporation e-mail: JimFleming(a)unety.net JimFleming(a)unety.s0.g0 (EDNS/IPv8)

2 1