DNRC Submission in Response to Questions From the Committee
August 27, 1999
1) I understand that you participated in the Boston Working Group, who submitted a proposal to the Department of Commerce in response to the White Paper. When the Department of Commerce announced its acceptance of ICANN's proposal, it also said that there were portions of other proposals, including the Boston Working Group's which the Department felt might be integrated into ICANN's governing documents. Do you think that ICANN sufficiently altered its articles and bylaws to reflect the changes requested by the Department of Commerce?
Unfortunately, the bylaws and articles were hardly changed at all in response to the recommended changes, and those changes that were adopted have been largely ignored in practice.
Many of the fears that both the Boston Working Group, and the Open Root Server Confederation expressed have indeed come to pass. Today, despite ICANNs telling Congress that the Santiago Board Meeting would be open, other board meetings remain closed.
ICANN does not provide nearly enough prior notice or comment periods before adopting by-laws changes or other substantive changes.
The ICANN board has failed to establish "on the record" voting.
ICANN picks and chooses between constituencies and its executives make defamatory statements about those who attempt to participate in the process. (This writer is among those who have been subjected to such abuse.)
ICANN has failed to replace the interim board with an elected board. Even worse, ICANNs board now proposes to continue the unelected interim board until September of 2000. In fact, it posted its proposal to do so only few days prior to the Santiago meeting.
Perhaps most damning, however, was the utter failure of the ICANN board to address the creation of an individual constituency, or to mandate that individuals be allowed to participate in other, already formed and provisionally approved constituencies. Neither individuals, nor non-commercial entities have any voice whatsoever in ICANN. Both the BWG and ORSC bylaws clearly mandated that ICANN fully admit individuals and non-commercial entities.
But it goes further, the ASO (Address Supporting Organization) and PSO (Protocol Supporting Organization) exclude any but a few select entities, entities which have not public accountability, are largely neither transparent nor open. Given that ICANN has repeatedly mentioned the possibility of charging for address allocations, a closed ASO could become even more non-competitive and dangerous than the irresponsibility shown by ICANN regarding the DNSO (Domain Name Supporting Organization)
The new ICANN Board ignored the concerns of BWG and the ORSC. Commerce wrote the following email to the ICANN regarding the desire that ICANN work with both groups to achieve a consensus document:
October 20, 1998
Dr. Herb Schorr, Executive Director
Dear Dr. Schorr:
On October 2, 1998, the Internet Assigned Numbers Authority (IANA) made aSincerely,
J. Beckwith Burr
Associate Administrator (Acting)
Unfortunately, specific points made by the BWG went ignored by ICANN. These points include the following:
|
BWG Points |
ICANN Response |
|
Added Preamble and Statement of Purpose |
Rejected by ICANN
|
|
Removed text that established the purpose of the corporation to be solely for "lessening the burdens of government" |
Rejected by ICANN |
|
Mandated that the Interim board create a membership structure, without exception |
Has not occurred almost a year later and may never occur or be so gutted as to lose the original intent |
|
Defined "fundamental" assets expected to be received from the US and added constraints upon what the corporation can do with those assets. |
Rejected by ICANN |
|
Removed President from the Board of Directors |
Rejected by ICANN |
|
Re-cast Supporting Organizations to be essentially permanent advisory committees with very strong role in initiating and defining corporation policies. |
Rejected by ICANN |
|
Eliminated Supporting Organizations ability to appoint Directors to either the Initial or the Final Board |
Rejected by ICANN |
|
Clarified that individuals may be members of Supporting Organizations |
Initially partially accepted by ICANN, then amended out of their organic documents |
|
Added "On-The-Record," role call voting on matters before the Board |
Rejected by ICANN |
|
Added additional public access |
Partially accepted by ICANN, but in practice ICANN is operated as an opaque and unaccountable body with no true public input despite assurances by ICANN to the House Sub-Committee to the contrary |
|
Broadened rights to Board Reconsideration |
Rejected by ICANN |
|
Eliminated special and unique recognition of contracts between the US and NSI and between the US and the University of Southern California |
Accepted by ICANN |
|
Added a more robust business planning and cost recovery model |
Partially accepted by ICANN, but as their current massive debt and near insolvency demonstrate, they have not implemented any of it |
|
Required that conflict-of-interest statements be made public subject to reasonable privacy limitations. |
Rejected by ICANN |
|
Recommended the reduction in the number of officers to the legal minimum, as well as other minor matters of clarification of language and structure |
Rejected by ICANN |
When it became apparent that ICANN would not seriously entertain making any of the changes recommended by BWG and ORSC, Commerce decided to give ICANN the go-ahead, and issued an MoU (Memorandum of Understanding) between them to provide for continuing oversight. Unfortunately, there was seemingly no substantive oversight being performed, and both groups became very discouraged. While Commerce was telling BWG and ORSC that it was not yet ready to "turn over the reins" to ICANN, another hand attempted to transfer authority through a single source offering through NIST that was added to the docket during the holiday season. Curiously, this was authority over the IANA functions that Mike Roberts had already announced were under ICANNs control in November of 1998 at the first ICANN meeting in Boston.
Formal complaints regarding this process, and the lack of Commerce Department supervision as described in its MoU went largely unanswered. Here is one example:
>Date: Fri, 05 Feb 1999 01:45:19 -0500
>To: Becky Burr <bburr@ntia.doc.gov>For a more graphic representation of the difference between the BWG proposed bylaws, the ORSC proposed bylaws, and the first set of ICANN bylaws, I have attached Ellen Ronys.(1) analysis located at
http://www.domainhandbook.com/comp-bylaws.html . Ms. Rony is co-author of "The Domain Name Handbook," an authoritative text in the field of Domain Names. Ms. Ronys work is a side by side comparison of the three sets. Please note that after this first set of bylaws was promulgated, ICANN made significant changes behind closed doors and without accountability, bringing their bylaws even further out of line with those proposed by BWG and ORSC. Ms. Rony has also created a comparison of the US Government DNS Policy Statements (including the Commerce Departments MoU and the ICANN bylaws located at http://www.domainhandbook.com/comp-policy.html 2) How are individual and non-profit domain name holders impacted by ICANN's dispute resolution policies?Individual and non-profit domain name holders are impacted in a significant and negative manner.
Both have been placed at significant risk of expropriation of their existing domain names, without compensation and without benefit of any form of legal hearing or due process. And both have been placed in a position of being second-class citizens when attempting to obtain new domain names.
Neither yet has any position with any meaningful voice within ICANN's structure: ICANN has explicitly rejected the participation of non-commercial interests and has taken multiple steps to prevent individuals from having any meaningful voice at any level of ICANN.
DNRC feels that ICANN, as a body of technical administration, has no business mandating domain name dispute policies in any way, especially given the lack of representation for individuals, non-commercial entities, and others. A petition formulated prior to the Berlin ICANN meeting and signed by 85 individuals (many having been deeply involved with Internet policies in the mid 80s) was presented to ICANN asking them to postpone consideration of the WIPO proposals until non-commercial entities and individuals were more represented. This petition was ignored.
Although ICANNs specific dispute resolution policies have not yet been chosen, DNRC has reviewed the latest draft that has been circulated and offers the following specific comments:
ICANNs dispute resolution policy could stifle political speech, parody, and criticism. If a trademark or service mark is used as part of the domain name, or the domain name is thought in any way to be similar to a trademark or service mark, the ICANN policy may call this "bad faith" and subject the domain name holder to cancellation and/or transfer the name to the challenger.
This is significant when you consider that critics, political pundits, religious groups and others with significant non-commercial messages are seeking the very same audience as corresponding trademark, service mark, or other intellectual property holders. The only way to reach this audience is often to draw the readers attention via a catchy title, slogan, or in the case of the Internet, through the domain name. While in publishing, one can use a title such as "Microsoft : Why I Dont Like Their Software," the corresponding method on the Internet would be something like "Ihatemicrosoft.com." Under the ICANN dispute policy, if any commercial use whatsoever is found, then the domain name could be cancelled or transferred, and the arbitration panels fees may be charged to the domain name holder. Essentially, this would be a penalty for otherwise protected speech.
While the ICANN policy is said to be predicated on commercial messages, it is important to note that in the case of Jews for Jesus v. Brodsky (3)the court found that a mere hyperlink to an organization that sold religious tracts created commercial use, and stripped Steven Brodsky of his domain name. The DNRC is concerned that such twisting of the spirit of the Lanham Act and intellectual property law could be extended to stifle other religious, political, and non-commercial commentary. This would indeed crush the very robust means of communication that has made the Internet so desirable to large corporations.
4) Does the current makeup of the ICANN Domain Name Supporting Organization fully reflect the diversity of the Internet community?ICANN's "constituency model" is a model of gerrymandering overwhelmingly in favor of commercial interests. In addition, ICANN has allowed the DNSO to be operated with overt exclusion. Perhaps most importantly, individuals and non-commercial interests are still absent from the DNSO community. Further, virtually an entire Internet community has dropped out of the ICANN process, due to the perceived "fixed" nature of many of the proceedings.
This is most apparent in the current makeup of the DNSO. Instead of some sound representational structures as were proposed in the Paris Draft, the ICANN Board approved a constituency model where the constituencies themselves are arbitrarily defined by ICANN. This is underscored by ICANNs refusal to put a petition by the Individual Domain Name Owners constituency on the agenda for their Santiago meeting(4). This decision was made in a closed meeting with no accountability. By contrast, the Non Commercial Domain Name Holders constituencys petition was placed on the agenda, even though it was received after the IDNOs. This may well be due to the ISOC friendliness of many key players involved in the NCDNHC. The ISOC (Internet Society) has long been an advocate of a powerful ICANN, and more Internet governance located outside the United States.
The vast non-commercial community of the Internet (a network founded for non-commercial research and speech) is underrepresented in the make-up of the ICANN Domain Name Supporting Organization. For each vote that it has, the commercial sector has two, and the service providers have 4. We believe this does not bode well for fair use and free speech issues that will arise in the future before this body. Many of the commercial interests given preferred seats at the table of governance have historically taken positions inimical to the unfettered growth of the Internet and the new technologies and access it represents. This not only disenfranchises individuals and the non-commercial community, but it includes the budding "new wave" of authors and artists, small businesses and new technology developers who, because of their relative political and sociological immaturity have not mobilized their infant resources with the same agility possible for an ITU, a WIPO, or an ETSI
Further, although the non-commercial community is engaged in a good faith effort to self-organize, it is the most heterogeneous and far-flung group, and has taken a little longer to organize then the commercial interests (who have more resources to dedicate). Nonetheless, the Non-Commercial Domain Name Holders Constituency (the NCDNHC) is now organized and accepting applications and will have elected representatives before the Santiago meeting. The IDNO, likewise, has elected representative, the first Internet based fully functional voting system, and policy statements ratified by its membership. To date, neither have been accepted as a full constituency.
Regardless, ICANN moved forward on the domain name dispute and cybersquatting proposals, a set of substantive law and mandatory arbitration procedures , without elected representation from either the non-commercial organizations or individuals.
We would like Congress to urge the Department of Commerce and ICANN to return these cybersquatting proposals without adoption for review and assessment which includes the non-commercial, small business and individual communities
Instead of defining a basis of representation, with objective standards by which constituencies qualified for recognition, the ICANN approach was to approve 7 constituencies, 6 of which were recognized in Berlin. All 6 had a large business bias. The resulting DNSO is a captured organ, composed of former gTLD-MoU supporters, and a very few remaining members from the at-large Internet community. This DNSO is making substantive policy decisions without any input whatsoever from non commercial domain name holders or individuals, that combined group being the largest number of users of the Internet who will be directly impacted by these decisions. This is ironic Vice President Al Gores vision for all educational organizations in the United States to be connected to the Internet. While they may become connected, they will have no say whatsoever in the decisions that ICANN has already put into motion.
Individuals
In the drafting process that led up to the formation of the DNSO, one draft (called the "BMW Draft") did not allow for the participation of individual domain name holders. Another draft (called the "Paris Draft") did allow for the participation by individual domain name owners. This was a major source of contention in the development of the DNSO.
At the Singapore ICANN meeting, there was a compromise in which ICANN acknowledged the Paris Draft principles by writing, in the DNSO formation document: "Individual domain name holders should be able to participate
in constituencies for which they qualify." (See, http://www.icann.org/dnso-formation.html).
Unfortunately, this concept that has been written out of every single constituency proposal accepted by ICANN to date. The phrase acknowledged by ICANN at the SIngapore meeting "Individual domain name holders should be able to participate in constituencies for which they qualify" is now without meaning. Constituency drafters simply viewed that sentence as something to be routed around, and the ICANN Board did not place any pressure on constituency organizers to open their groups.
As a result of this exclusion, a new group of "Individual Domain Name
Owners" has now organizing a new proposed constituency. Unfortunately, the IDNOs petition has been "postponed" by the ICANN board at their Santiago meeting. Again it was questioned whether individuals should have any say outside of the dilution of the General Assembly. An independent constituency for individuals is preferable, but if not allowed, ICANN should at least to have mandated that Supporting Organizations may not exclude individuals from the current. Individuals operating a for-profit commercial web site have more in common with the members of the "Business and Commercial Constituency" than they do with individuals using the Internet as a "home page." Individuals holding trademark rights on a name may have more in common with the Intellectual Property constituency than they do with another individual who is operating an informational web site.
The DNRC believes that corporate and organizational interests have excluded individuals from their constituencies not because individuals have no interest in their work, but because they fear they will be outnumbered and outvoted. The distinctions that have been drawn are artificial and should be dropped.
Non-Commercial Interests
At the creation of the DNSO in Singapore, the ICANN Board recognized seven initial constituencies, one of which was the non-commercial domain name owner constituency(5) .
Following Singapore, there was some confusion and debate as to whether this constituency would be for individuals and non-profit entities or non-profit entities alone. By the time of ICANN's Berlin meeting, at which constituency recognition was to be a central issue for the DNSO, competing proposals with very different models were presented for this constituency. Because the parties could not reach agreement themselves, the ICANN Board declined to recognize any constituency in this area.
Despite the absence of any non-commercial interests on the DNSO Names Council, the ICANN Board directed work to begin the in the DNSO.
The DNRC believes that ICANN should have shown the same leadership that it did in Singapore in bringing two competing DNSO drafts together for developing a compromise in Berlin on the two non-commercial interest proposals. The decision to approve *no constituency* has left us with an incomplete DNSO charged with developing policy recommendations on some of the most contentious issues facing ICANN (dispute resolution and trademark issues).
5) Does Network Solutions Incorporated ("NSI") have a sufficient dispute resolution policy, or are there reforms that NSI needs to make?NSIs dispute policy is fatally flawed, and in serious need of reform. In a nutshell, the problem with the Domain Dispute Policy are as follows:
Use of "May" Instead of "Will"
NSI calls the document on which it explains its position, the "Domain Dispute Policy." However, a policy is generally a document which lays out the steps an entity will take when faced with particular situations. The new NSI "policy" states specifically that NSI *may *use this policy to handle domain disputes. This, of course, means that they also may not. Needless to say, this is hardly something most businesspeople would wish to stake their business identity upon. There are other significant problems with the domain dispute policy:
Lack of Procedure
One of the most damning criticism of Network Solutions, Inc's domain dispute policy is that it was created without normal procedures. On the Internet, when one wishes to make a dramatic or sweeping change that affects the net "across the board," one at least used to employ the RFC process (pre-ICANN, that is). RFC stands for "Request for Comment" and is the general method used to inform the Internet community what you wish to do, ask for comments and suggestions, and solicit cooperation for your plan. NSI, on both occasions that it has implemented its domain dispute policies, has released them only after they were "done deals." Although David Graves of NSI has said that comments and suggestions were taken into consideration for the formulation of the second domain name dispute policy(6) , the community as a whole was given no notice of any discussions being held by NSI, or of any coordinated method for providing suggestions or comments.
NSI Is Not the Arbiter of Disputes
NSI has attempted to make it very clear that they do not desire to be brought into the middle of domain name disputes. They have gone so far as to state twice in their new policy, once up front and once in the middle, that they do not act as arbiter of disputes between "Registrants and third party complainants." However, the policy itself removes control of a domain from the original domain name holder, and puts it "on hold" while the dispute is settled by a court, or settled under the NSI policy. In these cases, the domain name holder is automatically penalized, and the challenger succeeds in depriving a domain name holder of business opportunities merely because they hold a trademark and have sent a letter alleging infringement and harm. Unlike the court system, the challenger does not have to prove infringement and harm in order for the domain name holder to have been deprived of his or her property. As has been noted, being deprived of one's domain name, even for a short period of time, can have serious business consequences.
As much as NSI wishes to claim that it is not arbitrating disputes, it is very clear that regardless of the outcome, a domain name holder must either file a lawsuit to keep the name, or hope that the trademark holder files a suit. If the trademark holder's goal is merely to prevent use of the name, it is in their best interest *not *to file suit, since the domain name holder's only recourse would then be to hire a lawyer and file their own lawsuit, prior to NSI putting the domain on hold. Given that the domain name holder only has 30 days in which to respond, the legal costs for filing will be much higher since any time you wish an attorney to work quickly, you will probably pay extra for it.
Ironically, the policy as written also acts as a deterrent to arbitration of the dispute rather than taking it to court. The policy specifically states that the domain name will not be put on hold if one of the parties files suit. It does not say that the name will not be put on hold if the parties seek arbitration. The policy also does not provide for instances where the challenger may agree (although it may be against their best interests) to allow for continued use of the domain name by the domain name holder while the dispute is settled. Perhaps this is one of the areas where NSI may use its "may" provisions of the policy.
Notice of Policy Changes
Most contracts between parties contain a "notice" provision. The notice provision generally tells people where and how they must send notice to the other party, generally when some sort of action is required to be performed. Most contracts also provide that the contract can only be changed by a writing signed by both parties, but it is clear that NSI did not wish to grant that authority to domain name holders.
Both domain name policies promulgated by NSI provide that the only notice that needs to be given of contract changes, is by making a file available on NSI's FTP site.
This means that unlike other contracts, where the onus is on the person who wishes to change the contract, the people being affected by a unilateral decision are required to take the affirmative action of periodically checking the NSI FTP site.
Trademarks and Domain Names
The purpose of a trademark is to identify the maker of a good or a service. The mark is to be displayed on brochures or on labels, or on the goods themselves to keep from confusing the consumer as to where a product was made.
While more information about trademarks and how to obtain them will be provided in a subsequent article in this series, here is an overview of the trademark process and its costs:
This whole process can take anywhere from 8 months or so to years. During this time, you may have a "common law" trademark if you were the first person to use the name. You can also apply for a state trademark, giving you certain rights in that state. However, neither a common law trademark, nor a state trademark will help you with the InterNIC. It is quite interesting, however, that NSI's first domain name dispute policy
did not specify that trademarks would have to be federal. This change did not occur until the policy of November, 1995.The InterNIC and Trademarks
It is curious that in a recent speech, David Graves of NSI stated that there was no known correlation between trademark law and domain names. A domain name is a verbal address that is used by humans in place of the numeric IP address that computers and network routers care about. As such, a domain name is much more an identifier than a mark one would place on a good or service to determine its origin. Congress has not as yet spoken to some trademark holder's claims that ownership of the trademark made automatic their ownership of a domain name, regardless of whether someone else had registered that name.
Regardless of the lack of legislative action, and the normal workings of the law in trademark disputes, NSI has decided that trademark can be used as a sort of "trump card," ensuring that trademark holders receive special treatment with regard to domain name holders. In all other legal situations, in order for a trademark holder to stop someone from using a similar or identical name, the trademark holder would have to show that its mark was being infringed. That is not necessary in NSI's policy. In order to get a domain name taken away, essentially all that is needed is for a trademark holder to send a domain name holder a letter alleging that that mark is being infringed. The domain name holder is then put on the defensive, and risks significant chance of losing the domain name regardless of what actions are taken.
In US trademark law, many different people can have the same name trademarked for different purposes, or in different "classes." A "class" consists of a grouping of similar products, such as class 10 for surgical, medical, dental and veterinary apparatus and instruments, artificial limbs, eyes and teeth; orthopedic articles and suture materials. Since the primary purpose of trademark law is to protect the consumer from being fooled as to the source of a product, these class designations make sense. It would be difficult for most people to believe the Cadillac cars also made Cadillac cat food. This branch of law was clearly created to protect the less sophisticated consumer from making errors of this type.
In the normal course of business in trademark law, in order to succeed with a claim of infringement, a trademark holder must show infringement in the class in which the trademark is held. This is, of course, impossible in an arena where there are no classes, such as the Internet. Applying trademark law to the Internet immediately raises two important distinctions. The first is that on the net, there is only one possible use for any given name in the .COM domain. Since .COM is the most used and therefore most coveted address, competition between US federally registered trademark holders and foreign registered trademark holders, will surely make for an impossible situation if NSI insists on its current procedure of using federal trademark as a "trump" card. The second is that domain names are not necessarily used for goods or services, which are the only two categories which the Lanham Act speaks to.
Given that NSI itself feels that there is no real correlation between trademark law and ownership of domain names, and the ill fit between trademark law and domain identifiers from both a legal perspective as well as a technical one, NSI's insistence on providing certain trademark owners (arguably the first who comes along) with the de facto authority to have a domain made unavailable to its registrant is largely incoherent and without foundation in either law or logic.
International Issues
NSI is responsible for registration all domain names in the most coveted .COM domain. Of course, this includes international commercial entities as well. However, trademark law is not international. Each country's trademark laws differ enough that many trademark lawyers specialize in specific countries for companies dealing multi nationally. Large US corporations may hold trademarks in 10 or more different countries, each with differing expiration dates, requirements for maintaining the trademark, quirks in the registration process, etc.
6) Regarding the possible addition of new generic Top Level Domains ("gTLDs"):
a) What concerns do you think trademark holders have regarding the addition of new gTLDs?
The purported concerns that trademark holders have regarding the addition of new gTLDs are threefold. First, they are concerned about policing their trademarks. Second, they wish a uniform dispute resolution policy prior to addition of new gTLDs. Third, they say they are concerned with "cyberpiracy." I will address each of these in turn.
Policing Trademarks
Given current search technology and Internet search companies that routinely scan the Internet for trademark violations, additional gTLDs will make that job no different. There are currently over 275 TLDs in use worldwide. Search robots and other technology is gTLD independent. It would work whether there are 275, or 275,000 TLDs. The trademark argument makes no more sense than it would in the physical world were there to be concern about the number of print publications allowed because it would be more difficult for intellectual property owners to search through the greater number of publications to police their trademarks. Communication should not be stifled for the convenience of a small faction of the business community.
Uniform Dispute Policy
I have already stated DNRC's concerns regarding uniform dispute policies in the answer to Question 2 above. I would like to reiterate here that the trademark interests are again asking for more protection on the Internet than they have in any other medium. Further, the trademark interests who purport to speak for all trademark holders are generally a small group who have not even consulted with their membership to find out the prevailing opinion.
Cyberpiracy
No "cyberpirate" has ever prevailed in any court in the world against a trademark holder. DNRC feels that this argument is solely a means to the end of getting further trademark protection than currently exists, and an in road to obtaining greater protection for all intellectual property. The current Intellectual Property constituency (of which I am a member) is made up of trademark attorneys as well as copyright attorneys and organizations. There are no representatives for small business, none for individuals, and exactly one for the public interest community (DNRC.) ASCAP and BMI are taking the lead in much of the discussions and deliberations of the Intellectual Property Constituency. DNRC feels that this is the first step towards content control. Groups like ASCAP and BMI stand to lose tremendous power if artists can go directly to the public via the Internet.
Attached is a copy of DNRC's dissent to the testimony provided to the Committee from the Intellectual Property constituency. This will provide further explanation for our positions(7).
b) How would the addition of new gTLDs increase competition in the registration and use of domain names?
Currently, there are three gTLDs that are available to individuals, small businesses, and corporations: .net, .org, and .com. While there can be dozens, if not hundreds of entities that wish to use a certain domain name, there is only one .com, one .net, and one .org. Increasing the number of gTLDs, especially if they become meaningful markers that assist consumers and others to find what they are looking for, will do nothing but assist both the communicative and commercial interests of the Internet. Examples of the useful markers include .per for personal domains, .arts for artistic domains, .auto for automobile dealers, manufacturers and part suppliers, .air for air freight, airlines, and other aircraft related industries, .firm for legal and consulting firms, .etc. This would serve the purpose of allowing different registrars for different gTLDs, or assist in "carving up the pie" so that more registrars and registries could operate in consort across multiple gTLDs. An increase in product would help fulfill the demand(8).
c) Does ICANN presently have the authority to add new gTLDs?
As far as DNRC is aware, the Commerce Department has not relinquished their claimed authority to perform this function to ICANN. We say "claimed authority" in part due to the following letter that was received by Karl Auerbach of the Boston Working Group from the NSF:
December 24, 1997
Mr. Karl Auerbach
218 Carbonera Drive
Santa Cruz, CA 95060-1500
Dear Mr. Auerbach:
Thank you for your patience in awaiting our response. We felt it was important, however, to answer fully your November 16, 1997 letter, especially since it is not uncommon for individuals unfamiliar with federal disclosure statutes to confuse the Privacy Act with the Freedom of Information Act (FOIA). For example, you mistakenly maintain that the statutory response dates applicable to FOIA requests similarly apply to the Privacy Act, and that clearly is not the case. Although National Science Foundation regulations certainly state that the agency will attempt to respond to Privacy Act requests within ten working days, there is no statutory deadline. And I am sure you appreciate the legal and factual difference between asking for whether records exist and seeking to amend a Privacy Act record pertaining to you.
Specifically, you ask us to inform you "of the existence of records pertaining to [you]" in what you assert to be a Privacy Act system of records referred to as the "domain name database." NSF maintains no such system of records and, consequently, cannot have "failed to publish notice of this system of records in the Federal Register" as you incorrectly state.
The Privacy Act's provisions apply to systems of records maintained by a Federal agency. 5 U.S.C 552a(e). A "system of records" includes only records under the control of the agency from which information is retrieved by an individual identifier. 5 U.S.C 552a(a)(5). The Privacy Act's definition of "agency" at 5 U.S.C 552a(a)(1) is the same as is defined in the Freedom of Information Act. See 5 U.S.C 552(f)(1)
The United States Supreme Court in Department of Justice v. Tax Analysts, 492 U.S. 136 (1989), established a two-pronged test for determining whether material constitutes an agency record". First, a federal agency must "either create or obtain" the materials. Id. at 144, citing Kissinger n Reporters Committee for Freedom of the Press, 445 U.S. 136 (1980), and Forsham v. Harris, 445 U.S. 169 (1980). Second, the agency "must be in control of the requested materials at the time the FOIA request is made." Tax Analysts, 492 U.S. at 145. Moreover, the Court held, "[b]y control we mean that the materials have come into the agency's possession in the legitimate conduct of its official duties." Id.
Network Solutions, Inc. (NSI) maintains records for its own use in administering certain domain names under a cooperative agreement with NSF, NCR-9218742. The so-called domain name database to which you refer consists of information collected, maintained and used by NSI pursuant to that cooperative agreement, which is a type of federal assistance award made by NSF under the Federal Grant and Cooperative Agreement Act of 1977, 4 U.S.C. 503, where the agency transfers money to the recipient to accomplish a public purpose of support or stimulation. NSF Grant Policy Manual 210.
NSF has neither created nor obtained the records NSI uses in day-to-day administration of domain name registration activities. The agency does not possess the database and cannot access it electronically (except in the same manner that is available to you and the general public through the Internet). Neither does NSF control the requested database. NSF has never acquired the database and, accordingly, has never integrated the database into NSF's files. Neither does the agency nor its employees retrieve, use, or rely on the data in conducting official agency duties or accomplishing any agency function. Thus, the requested database is not an agency record. See id. at 145-47.1
Private organizations like NSI that receive federal financial assistance grants are not within the definition of "agency," Forsham v. Harris, 445 U.S. 169, 179 (1980), and the documents created by a grant recipient are the property of the recipient, not the Federal Government. Id. at 180-81.2 The "written data generated, owned, and possessed by a privately controlled organization receiving federal study grants are not 'agency records' within the meaning of the Act when copies of those data have not been obtained by a federal agency subject to the FOIA." Id. at 171. Nor does the agency's right of access to the materials change this result. Tax Analysts, supra at 144. Rather, "the FOIA applies to records which have been in fact obtained, and not to records which merely could have been obtained." Id. at 186 (emphasis in original).3
Similarly, the records of recipients of federal grants fall outside the purview of the Privacy Act. General federal supervision of grantees remains insufficient to establish the substantial federal control and supervision necessary to characterize the grantee as a "federal" entity or instrumentality. Dennie v. University of Pittsburgh School of Medicine, 589 F. Supp. 348, 352 (D.V.I. 1984), aff'd, 770 F. 2d 1068 (3d Cir. 1985) citing Forsham. Applying Forsham to a claim under the Privacy Act, the Dennie court concluded that "absent extensive detailed and virtually day-to-day supervision" -- the standard of Forsham, "the recipient of public funds does not become a federal instrumentality" for Privacy Act purposes. Thus, the Federal agency has no obligation to insure that records held by its grantee are maintained in compliance with the Privacy Act. Id at 352-53.4
NSF maintains no such supervision and control over NSI databases. The terms of the cooperative agreement make clear that NSI -- as the awardee -- has primary responsibility for carrying out the agreement while NSF conducts oversight, monitoring, and evaluation of the awardee's performance. As in Forsham, supra at 172-73 and Dennie, supra at 352, NSF exercises limited oversight over the funded activity including review of periodic reports submitted by the grantee and agency approval of major program or budgetary changes, while NSI conducts the day-to-day administrative activities under the agreement. NSF's general oversight does not establish agency control of the database. See Forsham at 182 and Dennie at 352-53.
Thus, your assertion that the "domain name database" is an NSF system of records is incorrect, and NSF maintains no system of records responsive to your request.
Sincerely,
Herman G. Fleming
Privacy Officer
------------------------------------------------------------------------
1 Compare Tax Analysts, supra at 145-148 (agency had records in its possession at the time of the request, had placed them in its official case files, and was routinely using the records in the performance of its official duties); Burka v. HHS, 87 F.3d 508,515 (D.C. Cir. 1996) (agency exercised control over data tapes in the possession of its contractor sufficient to render them "agency records" for FOIA purposes where the agency ordered creation of the records, plans to take physical possession of the tapes at the end of the project, has indicated it will disclose the information after the agency's publication schedule is completed and prohibited the contractor from making any independent disclosures, and has read and relied significantly on the information in writing articles and establishing agency policies); and St Paul's Benev. Educ. Inst v. U.S., 506 F. Supp. 823, 829 (ND. Ga. 1980) (computer tape possessed by the agency; facts reveal the agency did "create or obtain a record," which is now in its possession, and that it may certainly rely or use this record in the future because of the importance of the data).
2 Compare Hurcules Inc. v. Marsh, 839 F.2d 1027(4th Cir. 1988) (where an agency directory prepared by a contractor for the agency and marked as the property of the government agency was held to be an agency record).
3 See also Animal Legal Defense Fund v. Secretary of Agriculture, 813 F. Supp. 882 (D.D.C. 1993) (regulated entities' plan stored "on-site" does not constitute an "agency record" under the meaning of the FOIA).
4 See also 5 U.S.C 552a(m)(1) and Office of Management and Budget Guidelines, 40 Fed. Reg. 28,948, 28,951,28,975 76 (July 9, 1975) (Privacy Act applies only to a system of records controlled by an agency within the terms of the Act, i.e., to those systems operated under a federal procurement contract "by or on behalf of the agency to accomplish an agency function". "The qualifying phrase 'to accomplish an agency function' limits the applicability of subsection (m) to those systems directly related to the performance of Federal agency functions by excluding from its coverage systems which are financed, in whole or part, with Federal funds, but with are managed by state or local governments for the benefit of state or local governments." Similarly, "[t was not intended to cover private sector record keeping systems" including those of federal grantees funded to support a public purpose.)
It is our interpretation of the above letter that NSF did not have the authority to give the Commerce Department in the first place, making any claims regarding the chain of authority from Commerce to ICANN dubious at best. If NSF has totally and completely relinquished ownership control of the whois database to NSI, it will be difficult to put that genie back in its bottle.
Further, Glen B. Manishen, Esq. Has done his own analysis of the DOCs ability to give ICANN authority. What follows are excerpts from an interview Mr. Manishen conducted with Gordon Cook and published in the May 1999 "Cook Report",(9)
The basic problem with the approach of the Department of Commerce (DOC) to privatization of DNS is that DOC lacks any recognized legal authority either over the global Internet or the Internet's Domain Name System. DOC's communications-related functions are limited by statute to policy development, and (except for the assignment of
domestic telecommunications frequencies) do not include any regulatory or rulemaking powers. The DOC White Paper is not, as DOC emphasized, a mandatory rule, but rather only a general statement of policy without the force or effect of law.
There is thus substantial doubt as to the legal authority of DOC and the National Telecommunications & Information Administration (NTIA) to direct, regulate or supervise the operations of ICANN. The Memorandum of Understanding (MOU) between DOC and ICANN asserts that "DOC has authority to participate in the DNS Project with ICANN" under 15 U.S.C. 1512, 1525 and 47 U.S.C. 902. Yet even a superficial examination of these statutes shows that they do not empower DOC to control the Internet's DNS system or to regulate a US non-profit corporation (such as ICANN) in setting rules for international competition for Internet domain names.
As an executive branch agency, DOC's powers are controlled by its so-called "enabling statute." 15 U.S.C. 1512 authorizes DOC to "foster, develop and promote foreign and domestic commerce." 15 U.S.C. 1525 permits DOC to engage in "joint projects . . . on matters of mutual interest" with nonprofit organizations. Even if the international nature of gTLDs were within the scope of DOC's powers over "foreign" commerce - an extra-territorial application of U.S. law that appears to have no precedent - these general provisions do not authorize DOC to promulgate rules for DNS, either directly or by delegation of that power to a private corporation. The fact that DOC and ICANN styled the MOU as a "joint project" cannot be bootstrapped into the power to control DNS, for example by ordering NSI to transfer the Root A server to ICANN.
A review of the DNS proceedings before DOC reveals that, until recently, DOC itself appears to have agreed that it lacks the affirmative power to regulate DNS operations on the Internet. The February 1998 Green Paper initially proposed that DOC would promulgate rules opening up new gTLDs and would order NSI to transfer the root to a neutral third-party. Yet the June 1998 White Paper did not establish any rules, and was issued solely as a "general statement of policy." This is entirely consistent with the limited scope of NTIA's statutory powers. As a part of DOC, NTIA is charged with performance of DOC's "communications and information functions." 47 U.S.C. 901(b)(1). These include:
1. Serving as "the President's principal advisor on telecommunications policies;"
2. Developing "telecommunications policies pertaining to the regulation of the telecommunications industry;" and
3."Coordinating the telecommunications activities of the executive branch and assisting in the formulation of policies and standards for those activities."
47 U.S.C. 901(b)(2)(C)-(I). Except for frequency assignment, NTIA therefore does not create rules or regulations for and telecommunications provider or industry segment. It's role is advisory and policy development, not substantive regulation.
The history of DNS development over the past several years merely underscores that until entry of the ICANN MOU, neither DOC nor NITA, like their predecessor NSF, has asserted any substantive powers to direct operation of the DNS system. In the 1998 Thomas v. NSI case, NSF stated that the Cooperative Agreement, the NSI contract that has since been transferred to DOC, requires NSI to "follow the policy guidance of a non-governmental body [IETF] in consultation with the Internet Assigned Numbers Authority, another non-governmental entity." Likewise, the White Paper took pains to emphasize that it was not "a substantive regulatory regime for the domain name system . . . . [It] is not a substantive rule, does not contain mandatory provisions and does not itself have the force and effect of law." 63 Fed. Reg. at 31748. It is thus quite curious, to say the least, that the MOU describes the White Paper as providing legal authority for DOC to "transition DNS management to the private sector."
When an agency acts in ways that exceed its statutory authority, the Administrative Procedure Act (APA) allows the federal courts to enjoin or set aside the agency's actions. The concept of a "general statement of policy" is established by the APA, and an agency's application of such a policy statement as a binding rule is clearly unlawful. Should DOC attempt to transfer operations of the DNS root to ICANN, therefore, it would be acting "ultra vires," or beyond its legal powers. Moreover, in the event an APA challenge to DOC's actions were initiated in a federal district court, the court would have ample authority to prevent transfer of the root in order to preserve the status quo pending the court's decision on the merits. (In contrast, a newly initiated lawsuit aimed solely at securing a preliminary injunction against transfer of the root would be more difficult to win, because the law requires a plaintiff to show "irreparable injury" before the grant of preliminary injunctive relief.)
COOK Report: the DOC's bootstrapping of its authority over ICANN opens it up to potential legal challenge from folks who want gTLDs opened sooner than ICANN plans. IAHC, ISOC, NSF, and NSI have all been sued over DNS. What should make ICANN and DOC any different, particularly since there has been virtually no substantive progress on DNS gTLD competition in the past two years?
We also think those who say ICANN must be made to succeed because, if it does not, the governments will step in, are misguided. ICANN is acting as a black box through which governments can already exert policy influence on critical parts of the internet in such a way as to avoid all public responsibility for their actions. Out of one side of ICANN's mouth come anti-regulatory sentiments while, on the other side, the moves taken under ICANN aegis restrict and control in the best regulatory manner imaginable.
7) Regarding the registration of one of the so-called "seven dirty words" as part of a domain name:
No. This doctrine is not applicable to the Internet. The Internet is not a broadcast medium, and is much more like publishing a newspaper or a magazine. Registrars should not be allowed to determine what is appropriate or inappropriate registration. Given the international nature of the Internet, some words and/or parts of words that Americans may find offensive may be descriptive words in other languages.
b) Should registries have the right to refuse to accept a registration containing any of these words?
Please see the response to part "a" of this question. DNRC feels that registries should be under the same obligation as registrars to register domain names without subjective determinations of appropriateness.
8) Does the Department of Commerce have the authority to recompete the .com, .net and .org registries? How would such recompetition affect the Internet's stability and competition for domain name registration and related services?The Department of Commerce has no known authority to be involved in Internet matters other than developing policy recommendations for the Executive Branch - nor should it have such authority. The Department's Internet related activities have occurred through the NTIA - which was created by and historically served to represent the interests of the Executive Branch and the White House, not the interests of the private sector or industry.
The latter role, regarding the interests of the private sector and industry, is that of the FCC which has long taken a "hands off" policy with respect to the Internet under its Computer I, II, and III policies. This policy significantly enabled and fostered the development of the Internet, in the face of actions by the Dept of Commerce which was attempting to force acceptance of other networking technologies such as OSI.
Further, if one agrees that the Internet is, by definition, an international activity, one would have to question the ability for the United States government to "compete" an award for this type of operation. Even assuming that there was USG authority, we would have to question the mechanics for determining a "responsive and responsible" offeror in parts of the world away from the U.S.
There is no technical reason why any number of TLD registries cannot be created immediately for what is generically a simple Internet host tagging service using a distributed domain database architecture for resolving tags. The COM, ORG, and NET business and intellectual property was acquired by NSI through an NSF award - in the same fashion as 820 awardees have acquired similar assets through 5,280 projects over the past fifteen years. Virtually every major contemporary Internet business sector today was build on such awards.
The Internet community has been consulted on numerous occasions regarding the need for a domain name dispute policy. In each consensus call at each IFWP meeting, no consensus was achieved as to the necessity of these policies. Court systems in most countries have extensive experience in trademark dispute issues. They are best qualified and experienced to address these disputes. Please note that WIPO has done exactly zero domain name dispute arbitrations to date.
10) There has been much discussion about the role of the Governmental Advisory Committee ("GAC") to ICANN. Regarding the GAC:
Has the GAC taken any actions to date that are inconsistent with its official role?
Yes, the GAC both in its creation and its conduct has taken numerous actions inconsistent with the intended role of governmental representatives. An example published 8/25/99 from the ICANN Santiago meeting is as follows:
B. With regard to principles for the delegation of
management for country code top level domains:
1. The Committee reaffirmed its May
resolution that the Internet naming system is a
public resource and that the management of a
TLD Registry must be in the public interest.
2. Accordingly, the GAC considers that no
private intellectual or other property rights
inhere to the TLD itself nor accrue to the
delegated manager
of the TLD as the result of
such delegation.
Point #2 is especially troublesome to countries that already have a strong tradition of protecting intellectual property rights, regardless of where they may be found. This provision would essentially create new law with no accountability or legislative review, and would strip countries like the United States of any proprietary rights in their Top Level Domains, including the .US domain. This was done despite J. Beckwith Burrs involvement as the United States representative to the GAC.
The basis for a GAC was established in the Dept of Commerce White Paper requirement that "governments and intergovernmental organizations [should participate] as Internet users or in a non-voting advisory capacity." As such, it was expected that individuals employed with government agencies or intergovernmental organizations worldwide would participate independently in some fashion in ICANN's various activities as "users." Furthermore, it s not apparent what other legitimate interest governments might have in the coordination of network names and addresses among the millions of private networks that constitute the Internet, other than as users.
However, at the initiative of the European Union, certain provisions were placed in ICANN's Articles of Incorporation and Bylaws that created the GAC as an autonomous global intergovernmental body nominally within ICANN, and invested it with the power to make "findings and recommendations...on the activities of the Corporation as they relate to concerns of governments, particularly matters where there may be an interaction between the Corporation's policies and various laws, and international agreements(10)."
This role was further enhanced by an explicit interlocking requirements in ICANN's Articles of Incorporation that "the Corporation shall operate..., carrying out its activities in conformity with relevant principles of international law and applicable international conventions and local law."
ICANN's Bylaws actually require that prior to making any substantive decision, "the Board will notify the chairman of the Governmental Advisory Committee...and will consider any response to that notification prior to taking action." Thus, the ICANN Board is obliged to constantly interact with this new intergovernmental body and obtain its findings and recommendations on all substantive matters.
The GAC was constituted in early 1999 by appointing the head of Australia's central telecom and information network regulatory body, who in turn used the membership contact list of the UN intergovernmental telecom ministry and regulatory organization - the International Telecommunication Union - to constitute the GAC membership. The European Union appointees to the ICANN Board - Eugenio Triana and Hans Kraaijenbrink - have served as the Board liaisons to the GAC since its inception. Kraaijenbrink also an Executive Board member of the European organization of public telecommunication providers.
From its inception, the GAC Chair has repeatedly asserted that the GAC provides ICANN with its "legitimacy," has the right to act autonomously and has done so in defining its jurisdiction, authority, and members, in adopting its own rules of procedure and membership requirements, and in promulgating general DNS related norms as Operating Principles. The last makes the rather extreme finding that "the Internet naming and addressing system is a public resource."
The GAC has adamantly opposed any open activities except an occasional open PR briefing, claiming that this secrecy is necessary for effective collaboration among governments. It has also self-asserted its existence as an intergovernmental body by amending its membership requirements to constitute only nations, and ejecting from its meetings, those who did not meet the requirements of being a plenipotentiary of a nation State.
Is the GAC subject to its own rules or to the rules of ICANN?
The GAC asserts that it is subject to its own rules.
What reforms to the GAC, if any, should be made to ensure that it will act only as an advisory body to ICANN and not as a policy-making body?
The GAC is not needed and should never have been created. Most parties assumed that the White Paper participatory statement would simply be met by "government users" participating in policy committees and discussion groups like everyone else.
Assuming its continued existence, the GAC should not exist as an intergovernmental body (i.e., its members constituting nations), but as an advisory committee of individuals having an association with or otherwise representing expertise or interests of governmental and intergovernmental entities.
The GAC should not be allowed to make formal findings and recommendations as an intergovernmental body on matters of international and domestic law.
The GAC should not be allowed to be autonomously chaired by a government official who determines and accredits its membership and maintains its secretariat.
The GAC should not be allowed to be conduct any of its activities or maintain documents in secret, and operate fully in the open. A representative from Ralph Naders consumer organization was ejected from the GAC meeting in Santiago, despite GACs decision to allow observers from the World Intellectual Property Organization.
11. If ICANN ultimately does not charge its now suspended $1.00 per domain name fee, how should ICANN fund its operation?
First of all, ICANN must get its expenses under control. ICANN's role and practices are potentially subject to enormous abuse as a non-profit organization. If it played the minimalist coordinating role of its predecessor IANA Secretariat, ICANN would need only sufficient money to pay two part-time researchers.
The Internet community was told that Jones Day was providing legal fees on a "pro-bono" basis. Imagine our surprise when we found that $500,000 was owed in back legal fees. Further, a salary of $18,000 per month for a CEO with no relevant experience, in a position that both BWG and ORSC proposed to cut out of the ICANN bylaws is grossly excessive.
Once ICANNs costs are under control, one way to control ICANN's potential adverse and abusive behavior is to insist on a funding arrangement that derives from services actually directly performed that its clients will pay for. The worst approach is what they have attempted - simply assess an arbitrary tax on their clients' assets.
We propose that ICANN draw up a neutral, non-discriminatory schedule of fees for specific services that reflects ICANNs actual costs. This cost should then be passed on to its client base. Unfortunately, ICANN has shown a complete inability to keep costs under control that would have sunk any other start-up company without the significant favoritism that has been shown to ICANN.. As a co-founder of a successful Internet start-up, I am personally highly concerned regarding some of ICANNs expenditures. A small group is all that is necessary to manage the function of "technical coordination." Further, a technical group charged with management of Internet assets should utilize the medium it is managing for all meetings. There is no need for the lavish expenditures necessary to fly board members, technicians, and their outside counsel to expensive locations around the world.
Perhaps the most confusing expenditures, however, are those for a public relations firm, over $500,000 for an anti-trust attorney who has stated he has no corporate experience, and $18,000 for a CEO. If my company, InterCon Systems Corporation, had attempted to contract for these types of expenses, its would not have lasted 2 months. It would never have received loans from companies such as MCI and Cisco, would never have received over half a million dollars in "credit" from the Jones Day law firm (since paid through the loans from MCI and Cisco), and would never have been able to afford a public relations firm. Such an insolvent company would never have received a US government contract to control such a vast and important resource as the Internet.
Further, ICANN has largely ignored the mandates of the Department of Commerce in the White Paper, and its subsequent letters calling for consensus with BWG and ORSC would have brought the contract itself into question. Under ordinary US Government contracting procedures, ICANN would be considered to be in violation of the terms of its contract in a manner requiring the contracting agency to assume direct, immediate control of the activity or else to determine the continuing availability of competing bidders to take immediate control of the work in a manner that ensures full contract compliance.
ICANNs mismanagement of funds, inability to keep its cost down to a reasonable level, and inability to perform the functions it was contracted to do, should call for an immediate recompetition of the contract. The concept of ICANN is a good one. This particular implementation is so badly flawed that it would be far simpler to start over than to attempt to salvage this organization.
Respectfully submitted,
Michaela (Mikki) Barry /S/
President3. Jews for Jesus v. Steven C Brodsky US District Court, District of NJ (1999)
4. Their webpage and further information is located at http://www.idno.org
5. See http://www.icann.org/dnso-formation.html.
7. See http://www.domain-name.org/dissent723.html