They can and would implement something as close to that as possible. I gave current, real-world terms. In Traveller, they would naturally have to modify the idea some. For example, whenever in a system with xboat service, transmit, prior to jump, your movement report. If you don't show up, it helps narrow down where and when you went missing. If there's no xboat, is there a Scout base? An IN base? Or a military data drop on planet?

Yes, it won't work *as well* as it does today, but that's no excuse for throwing up hands and declining to even try to apply some risk mitigation.

From: "Bruce Johnson" <xxxxxx@Pharmacy.Arizona.EDU>
To: "TML" <xxxxxx@simplelists.com>
Sent: Friday, February 12, 2016 6:06:59 PM
Subject: Re: [TML] Instant city

The Imperium CANNOT DO THIS. The most recent information the IN can possibly have of a ship that is not in a particular system is 7 days old. That increases by 7 days for every two parsecs (presuming the use of J2 Scouts/Couriers for comms) farther away the ship is. And they cannot get something *back* to where the ship was supposed to be except in the same time.

The existence of jump lag prevents this kind of close command and control; HQ might be *months* behind the front lines.

The absolute worst case of a misjump is 36 parsecs, which is 107 days away from where a ship is supposed to be at J2.

That’s roughly 4 months.

The IN operates like Admiral Nelson’s Navy, not Admiral Halsey’s.
--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group

Institutions do not have opinions, merely customs

-----
The Traveller Mailing List
Archives at http://archives.simplelists.com/tml
Report problems to xxxxxx@simplelists.com
To unsubscribe from this list please goto
http://archives.simplelists.com

-----
The Traveller Mailing List
Archives at http://archives.simplelists.com/tml
Report problems to xxxxxx@simplelists.com
To unsubscribe from this list please goto 
http://www.simplelists.com/confirm.php?u=dcVEexd3Y1tm8q7XETdwyQ1b8NoTIQhr