Mercury Luggage Manufacturing Company v. Domain Protection LLC

CourtDistrict Court, N.D. Texas
DecidedJanuary 6, 2022
Docket3:19-cv-01939
StatusUnknown

This text of Mercury Luggage Manufacturing Company v. Domain Protection LLC (Mercury Luggage Manufacturing Company v. Domain Protection LLC) is published on Counsel Stack Legal Research, covering District Court, N.D. Texas primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Mercury Luggage Manufacturing Company v. Domain Protection LLC, (N.D. Tex. 2022).

Opinion

IN THE UNITED STATES DISTRICT COURT NORTHERN DISTRICT OF TEXAS DALLAS DIVISION

MERCURY LUGGAGE § MANUFACTURING COMPANY, § a Florida corporation, § Plaintiff, § No. 3:19-cv-1939-M-BN § V. § § DOMAIN PROTECTION, LLC, a § Texas limited liability company, § § Defendants. § §

MEMORANDUM OPINION AND ORDER

This case has been referred to the undersigned United States magistrate judge for pretrial management under 28 U.S.C. § 636(b) and a standing order of reference from Chief Judge Barbara M. G. Lynn. See Dkt. No. 131. Plaintiff Mercury Luggage Manufacturing Company (“Mercury Luggage”) seeks leave to file a First Amended Complaint to add an additional party. See Dkt. No. 122. Defendant objects to the amendment. For the reasons and to the extent explained below, the Court GRANTS Mercury Luggage’s Motion for Leave to File First Amended Complaint [Dkt. No. 122]. Background Mercury Luggage sued Defendant Domain Protection, LLC (“Domain Protection Texas”) in August 2019, alleging violations of the Anticybersquatting Consumer Protection Act, 15. U.S.C. § 1125(d) and seeking to recover sewardtruck.com (“the Domain”) from the current registrant. The initial discovery period concluded on July 10, 2020, and the deadline for joinder of parties and to amend the pleadings expired on April 2, 2020. But, on January 29, 2021, Domain Protection Texas stated, purportedly for the first time during the nearly year-and-a-

half-long proceedings, that it does not control the Domain and that a trial would be pointless because Domain Protection Texas would be unable to transfer the Domain to Mercury Luggage if the court ordered it to do so. Finding good cause, the Court granted Mercury Luggage’s motion to continue trial and reopen discovery for 75 days to allow Mercury Luggage to attempt to identify who has owned and/or controlled the Domain since this suit was filed in 2019. In its proposed Amended Complaint, Mercury Luggage seeks to add, in

addition to Domain Protection Texas, an identically named entity organized under the laws of Virginia: “Domain Protection Virginia.” Mercury Luggage asserts that Domain Protection Virginia was formed on the same date as Domain Protection Texas, by the same organizer, Lisa Katz, who managed both entities through at least 2020 and maintained the principal place of business for both entities in Dallas, Texas. Mercury Luggage further alleges that, in addition to sharing a manager and principal

place of business, the Domain Protection entities share an attorney and store their records at that shared attorney’s office. Mercury Luggage alleges that the registrant of the Domain from at least March 1, 2018 through December 1, 2019, nearly four months after Mercury Luggage initiated suit, was listed as Domain Protection, LLC, with Lisa Katz listed as the contact. And, on June 18, 2018 and November 14, 2019, respectively, Domain Protection Texas and/or Domain Protection Virginia renewed the Domain’s registration, and the renewals were sent to, and paid for by, Lisa Katz. On December 1, 2019, the Domain was transferred to a new registrar, Name Silo, LLC, paid for

using a credit card in the name of “L. Katz,” with the same listed address as Domain Protection Virginia’s registered agent. Mercury Luggage alleges that the Domain’s nominal registrant listed with Name Silo is RCL Systems but that there is no entity nor any fictitious name filings with the name RCL Systems registered with the Virginia Secretary of State. And, according to Mercury Luggage, the registered agent’s office listed as the contact address for RCL Systems allegedly has no record of providing services to any entity using that name, and the telephone number listed

for the Domain registrant is the same telephone number for Domain Protection Defendants’ shared attorney. Mercury Luggage asserts that, in light of these alleged facts, along with the purported fact that Domain Protection Texas offered in the course of settlement negotiations to sell the Domain to Mercury Luggage, “the current registrant and owner of the Domain is Domain Protection Texas, Domain Protection Virginia, or an

entity that is under the control of the Domain Protection Defendants, their agents, their owners, or some combination thereof.” Due to the conflicting evidence over who owned and/or had control over the Domain since the lawsuit was filed in August 2019, and since the purported transfer in December 2019, Mercury Luggage seeks to amend its complaint to add Domain Protection Virginia as a defendant “to avoid any further claims that [it] sued the wrong entity” and to prevent what it characterizes as further attempts to “obfuscate the true owners/registrants of the domains in [the Domain Protection Defendants’] control.” Legal Standards

Because the standards by which the Court evaluates a motion for leave to amend the pleadings vary according to whether the motion was filed before or after the deadline established in the scheduling order, the court must determine, as an initial matter, whether the motion was filed before or after the deadline. See, e.g ., Orthoflex, Inc. v. Thermotek, Inc., Nos. 3:11-cv-08700-D & 3:10-cv-2618-D, 2011 WL 4398279, at *1 (N.D. Tex. Sept. 21, 2011) (“Motions for leave to amend are typically governed by Rule 15(a)(2), or, if the time to seek leave to amend has expired, by Rule

16(b)(4) and then by Rule 15(a)(2).”). When the deadline for seeking leave to amend pleadings has expired, the Court must first determine whether to modify the scheduling order under the Fed. R. Civ. P. 16(b)(4) good cause standard. See S&W Enters., L.L.C. v. SouthTrust Bank of Ala., N.A., 315 F.3d 533, 536 (5th Cir. 2003). To meet the good cause standard, the party must show that, despite her diligence, she could not reasonably have met the

scheduling order deadline. See id. at 535. The Court assesses four factors when deciding whether to grant an untimely motion for leave to amend under Rule 16(b)(4): “‘(1) the explanation for the failure to timely move for leave to amend; (2) the importance of the amendment; (3) potential prejudice in allowing the amendment; and (4) the availability of a continuance to cure such prejudice.’” Id. at 536 (quoting Reliance Ins. Co. v. La. Land & Exploration Co., 110 F.3d 253, 257 (5th Cir. 1997)). If the movant satisfies Rule 16(b)(4)’s requirements, the court must then determine whether to grant leave to amend under Fed. R. Civ. P. 15(a)(2)’s more liberal standard, which provides that “[t]he court should freely give leave when justice so

requires.” FED. R. CIV. P. 15(a)(2); see S&W Enters., 315 F.3d at 536. When the party is not subject to an expired deadline for seeking leave to amend, Rule 15(a) requires that leave to amend be granted freely “when justice so requires.” FED. R. CIV. P. 15(a)(2). Leave to amend is not automatic, Jones v. Robinson Prop. Grp., L.P., 427 F.3d 987, 994 (5th Cir. 2005), but the federal rules’ policy “is to permit liberal amendment to facilitate determination of claims on the merits and to prevent litigation from becoming a technical exercise in the fine points of pleading,”

Dussouy v. Gulf Coast Inv. Corp., 660 F.2d 594, 598 (5th Cir. 1981).

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Cite This Page — Counsel Stack

Bluebook (online)
Mercury Luggage Manufacturing Company v. Domain Protection LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/mercury-luggage-manufacturing-company-v-domain-protection-llc-txnd-2022.