Comments on: Case of the Day: FKA Distributing v. Yisi Technology https://lettersblogatory.com/2017/10/23/case-of-the-day-fka-distributing-v-yisi-technology/ The Blog of International Judicial Assistance Mon, 18 Nov 2024 01:33:15 +0000 hourly 1 https://wordpress.org/?v=7.0 By: Ted Folkman https://lettersblogatory.com/2017/10/23/case-of-the-day-fka-distributing-v-yisi-technology/#comment-2949 Tue, 24 Oct 2017 16:03:00 +0000 https://lettersblogatory.com/?p=25464#comment-2949 In reply to Aaron Lukken.

Page 5: “The vendor who served the documents for Plaintiff stated that China has been taking up to one year or more …”

]]> By: Aaron Lukken https://lettersblogatory.com/2017/10/23/case-of-the-day-fka-distributing-v-yisi-technology/#comment-2948 Tue, 24 Oct 2017 13:37:45 +0000 https://lettersblogatory.com/?p=25464#comment-2948 I’ve got to think that any “vendor” who is per se credible would have mentioned to the litigators that China takes forever (if they even do execute requests anymore, which is questionable). That said, I don’t see any reference to the vendor… where is it?

What I question is why nobody involved in this case even mentioned Schlunk. It’s crystal clear from the 4(f)(3) motion that it was completely ignored– and it seems the judge declined to look behind that disregard. The got Mullane, they got Rio Properties, and they left out Schlunk entirely. Why? Either because it’s adverse or because they don’t know about it– which raises even more questions than the adversity issue..

This would be akin to ignoring Miranda in a criminal confession case.

]]> By: Service of Process and the Unauthorized Practice of Law | Letters Blogatory | Letters Blogatory https://lettersblogatory.com/2017/10/23/case-of-the-day-fka-distributing-v-yisi-technology/#comment-2947 Tue, 24 Oct 2017 10:00:32 +0000 https://lettersblogatory.com/?p=25464#comment-2947 […] advice or where the vendor had not done a good job effecting the service. For example, I’ve seen vendors submitting requests for service to a foreign central authority and then, after the client […]

]]>