Weinstein v. Islamic Republic of Iran, 080216 FEDDC, 14-7193

Docket Nº:14-7193, 14-7194, 14-7195, 14-7198, 14-7202, 14-7203, 14-7204
Opinion Judge:Karen LeCraft Henderson, Circuit Judge:
Party Name:Susan Weinstein, individually as Co-Administrator of the Estate of Ira William Weinstein, and as natural guardian of plaintiff David Weinstein (minor), et al., Appellants v. Islamic Republic of Iran, et al., Appellees
Attorney:Meir Katz argued the cause for the appellants. Robert J. Tolchin, Steven T. Gebelin and Scott M. Lesowitz were with him on brief. Jeffrey A. Miller entered an appearance. Noel J. Francisco argued the cause for the garnishee-appellee Internet Corporation for Assigned Names and Numbers. Tara Lynn R...
Judge Panel:Before: Garland, Chief Judge, Henderson, Circuit Judge, and Randolph, Senior Circuit Judge.
Case Date:August 02, 2016
Court:United States Courts of Appeals, Court of Appeals for the District of Columbia Circuit
 
FREE EXCERPT

Susan Weinstein, individually as Co-Administrator of the Estate of Ira William Weinstein, and as natural guardian of plaintiff David Weinstein (minor), et al., Appellants

v.

Islamic Republic of Iran, et al., Appellees

Nos. 14-7193, 14-7194, 14-7195, 14-7198, 14-7202, 14-7203, 14-7204

United States Court of Appeals, District of Columbia Circuit

August 2, 2016

Argued January 21, 2016

Appeals from the United States District Court for the District of Columbia Nos. 1:00-cv-02601, 1:02-cv-01811, 1:08-cv-00520, 1:01-cv-01655, 1:08-cv-00502, 1:00-cv-02602, 1:14-mc-00648

Meir Katz argued the cause for the appellants. Robert J. Tolchin, Steven T. Gebelin and Scott M. Lesowitz were with him on brief. Jeffrey A. Miller entered an appearance.

Noel J. Francisco argued the cause for the garnishee-appellee Internet Corporation for Assigned Names and Numbers. Tara Lynn R. Zurawski and Ryan J. Watson were with him on brief.

Benjamin C. Mizer, Principal Deputy Assistant Attorney General, United States Department of Justice, Beth S. Brinkmann, Deputy Assistant Attorney General, and Douglas N. Letter, Mark R. Freeman and Sonia K. McNeil, Attorneys, were on brief the for amicus curiae United States.

Before: Garland, [*] Chief Judge, Henderson, Circuit Judge, and Randolph, Senior Circuit Judge.

OPINION

Karen LeCraft Henderson, Circuit Judge:

The plaintiffs-victims of terrorist attacks and their family members-hold substantial unsatisfied money judgments against defendants Islamic Republic of Iran (Iran), Democratic People's Republic of Korea (North Korea) and Syrian Arab Republic (Syria) arising out of claims brought pursuant to the Foreign Sovereign Immunities Act (FSIA). To satisfy the judgments, the plaintiffs sought to attach Internet data managed by the Internet Corporation for Assigned Names and Numbers (ICANN) and, accordingly, served writs of attachment on ICANN. On ICANN's motion, the district court quashed the writs, finding the data unattachable under District of Columbia (D.C.) law. We affirm the district court but on alternative grounds.

I.

Background

A. Technical

This case requires substantial explanation of the sought-after data.1 The plaintiffs initiated these proceedings by serving multiple writs of attachment on ICANN seeking the country-code top level domain names (ccTLD) and Internet Protocol (IP) addresses of Iran, Syria and North Korea, respectively. Neither the ccTLD nor the IP address lends itself to easy description.

Both data are parts of the Internet, the "network of networks, " Am. Civil Liberties Union v. Reno, 929 F.Supp. 824, 844 (E.D. Pa. 1996), which is "comprised of numerous interconnected communications and computer networks connecting a wide range of end-users to each other." Register.com, Inc. v. Verio, Inc., 356 F.3d 393, 409 (2d Cir. 2004).2 The IP address is the appropriate starting point. Every device connected to the Internet and every web page on the Internet is identified by an IP address. The IP address appears as a string of numbers separated by periods, for example, "100.200.123.234." It identifies the location, "i.e., a particular computer-to-network connection" of an end-user's computer and also "serves as the routing address for . . . requests to view a web page." Id. The IP address is critical to the Internet's functioning in the same way a telephone number is essential to the functioning of the telecommunications system. One may dial a set of numbers to connect to other individuals through the telecommunications system and the same is true vis-à-vis an IP address and the Internet. Granted, an ordinary Internet end-user does not operate this way. For example, Google has the IP address "173.194.65.113" but few would maintain that entering that address in an Internet browser is the most practical way to access the Google web page. Instead, most end-users simply type "google.com" to access the Google web page.

Because the numeric IP address is difficult to remember, the domain name system (DNS) was created to provide a more user-friendly Internet. At bottom, a "domain name" is the alphanumeric "Web page address[] that end users type into their browsers" and the DNS matches that name (i.e., "google.com") "with the [IP] addresses of the servers containing the Web pages the users wish to access." Nat'l Cable & Telecommn's Ass'n v. Brand X Internet Servs., 545 U.S. 967, 987 (2005). Thus, much of the DNS's value lies in its ability to enable an end-user, with a domain name in hand, to access a desired IP address and, more importantly, its corresponding web page without in fact using the IP address. But unlike an IP address, "a domain name does not signal where a computer [or web page] is . . . located. . . . [A] domain name is not an address as typically understood but instead is a mark identifying a specific person's or organization's site on the Internet." Thomas v. Network Solutions, Inc., 176 F.3d 500, 503 n.2 (D.C. Cir. 1999). In order to reach the "site, " the user's domain name input must be "translate[d] . . . into [a] numerical IP address, " Register, 356 F.3d at 410-11 & n.14, i.e., the domain name must be "resolved, " Name.Space, Inc. v. Network Solutions, Inc., 202 F.3d 573, 577 (2d Cir. 2000).

Understanding the "resolving" process begins with breaking down an Internet web page name-i.e. a domain name ("google.com")-into two parts. The first part appears after the last dot-the "top level domain" (TLD). As relevant here, there are two types of TLDs: generic TLDs and country code TLDs (ccTLDs). The former include ".com, " ".net" and ".org" whereas the latter are distinguished by a national, geographic or political association-for example, ".us" for the United States and, here, ".ir" for Iran, ".sy" for Syria and ".kp" for North Korea.3 The second part precedes the last dot-the second level domain (SLD); i.e., "google" in the "google.com" example.

Broadly speaking, an Internet end-user searching for (the technical term is "querying") a domain name like "google.com" reaches the web page in one of two ways depending on whether he already has visited that web page. In either case, his device ordinarily first sends the query to a nearby DNS "caching server" operated by the end-user's Internet service provider (ISP).4 See Daniel Karrenberg, The Internet Domain Name System Explained for Non-Experts, in Internet Governance: A Grand Collaboration 23 (U.N. ICT Task Force 2004). The caching server knows the location of the web page if it has "cached" it, i.e., "remembered it . . . from a previous transaction." Id. at 24. In that case the query does not go beyond the caching server because it directs the end-user to the desired location. Id. Thus, once an end-user has visited "google.com, " his caching server remembers the web page location for subsequent visits. And if the end-user has never visited the requested SLD-i.e., never visited "google.com"-but has visited another ".com" web page (e.g., "amazon.com"), the caching server recognizes the location of the TLD (".com"), asks it for the location of the SLD ("google.com") and then routes the end-user accordingly. Id. at 26-27.

An end-user can also locate a web page if he has not yet visited the web page or even its TLD. This way involves a caching server that is empty-it does not know the location of ".com, " and even less "google.com, " because it has not yet cached them. But the caching server knows at least one thing: Pursuant to widely adopted pre-programmed DNS protocols, the server knows to query "a special set of authoritative servers" otherwise known as "the DNS root servers, " id. at 27-of which there are thirteen world-wide; namely, one "master root zone server, " which contains "the authoritative root zone file, "5 and "12 duplicate root zone servers, " Name.Space, 202 F.3d at 577. In short, the caching server knows to go to the top of the DNS's "hierarchical tree structure." Id. These thirteen servers-the top of the tree- know the location of all authoritative TLD servers and thus the caching server can locate ".com, " ".ir" or any other TLD by querying the DNS root servers. Once one of the root servers tells the caching server the ".com" location, the caching server can query that TLD for all SLDs within it and does not have to revisit the root servers for subsequent web page searches within the ".com" TLD.6 Thus the root servers form "a critical Internet chokepoint." A. Michael Froomkin, Wrong Turn in Cyberspace, 50 Duke L.J. 17, 50 (2000). To use the entire DNS, a caching server need know nothing more than the location of the DNS's thirteen root servers; the root servers, tied to the root zone file, permit any end-user to access all downstream domains.

As relevant here, the DNS's "hierarchical tree structure, " Name.Space, 202 F.3d at 577, contains...

To continue reading

FREE SIGN UP