Legal Opinion
Lockheed Martin Corp. v. Network Solutions, Inc.
District Court, C.D. California
Decided November 17, 1997No. CV 96-7438 DDP (ANX)PublishedCited by 44 opinions
1Opinion of the Court
Order Granting Defendant’s Motion for Summary Judgment
PREGERSON, District Judge.
The motion by defendant Network Solutions, Inc. (“NSI”) for summary judgment came before the Court on October 6, 1997. After reviewing and considering the materials submitted by the parties and hearing oral argument, the Court grants the motion in its entirety.
I. Background
The issue presented by this litigation is whether NSI violated federal trademark law by accepting registrations of Internet domain names that are identical or similar to Lockheed Martin Corporation’s (“Lockheed”) SKUNK WORKS service mark.…
2Cases cited38 opinions
- Anderson v. Liberty Lobby, Inc.Supreme Court of the United States · 1986
- Celotex Corp. v. Catrett, Administratrix of the Estate of CatrettSupreme Court of the United States · 1986
- Feist Publications, Inc. v. Rural Telephone Service Co.Supreme Court of the United States · 1991
- Inwood Laboratories, Inc. v. Ives Laboratories, Inc.Supreme Court of the United States · 1982
- Reno v. American Civil Liberties UnionSupreme Court of the United States · 1997
33 more not listed; retrieve them via the Exa API.
3Cited by44 opinions
- Panavision International, L.P., a Delaware Limited Partnership v. Dennis Toeppen Network Solutions, Inc., a District of Columbia CorporationCourt of Appeals for the Ninth Circuit · 1998
- Darrell J. Bird v. Marshall Parsons, Stephen Vincent, George Decarlo, Dotster, Inc., and afternic.com, Inc.Court of Appeals for the Sixth Circuit · 2002
- Columbia Insurance v. Seescandy.ComDistrict Court, N.D. California · 1999
- Lockheed Martin Corporation, Plaintiff-Counter-Defendant-Appellant v. Network Solutions, Inc., Defendant-Counter-Claimant-AppelleeCourt of Appeals for the Ninth Circuit · 1999
- register.com, Inc. v. Verio, Inc.Court of Appeals for the Second Circuit · 2004
39 more not listed; retrieve them via the Exa API.