Re: Finding the appropriate work stream for draft-nottingham-for-the-users

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On Mar 19, 2019, at 7:31 AM, Stewart Bryant <stewart.bryant@xxxxxxxxx> wrote:

Just to be clear, those are not numbers I plucked out of the air.

1TB/s is needed to do holographic teleconferencing. I would argue that being able to have a fully immersive experience including shaking the hand of your business contact, or hugging a parent or child without burning carbon must be a good thing that many people will want to do. The haptic component of the experience requires surprisingly low latency.

I’ll take bets against those numbers - with a caveat. You can’t deliberately break the system in the wrong place just to kick the numbers up.

The following is a chart from the early 1990s that shows the BW needed for a variety of ways of interacting. The latency budget is 100ms, i.e., intended to provide “realtime” haptic latency, some of which is consumed by propagation delay (depending on the distance between endpoints). 

When the chart was developed, we were shifting from HTML to icons and ISDN-ish speeds were enough. Now, nearly 30 years later, we’re pushing 300dpi displays and everyone is happy enough with 100M-ish speeds, as predicted, but only if you actually need to send the whole screen within the latency+reaction time.

If you push to 3D, you’re still just a factor of 2 above those numbers. 

But we basically stopped paying for 3D movies (http://collider.com/3d-movies-are-dead-again/), so I have doubts about anyone caring about remote holography.

Instead, I’ll bet that in about 15-20 years, when our screens are 1000dpi, we’ll actually start to want 40G speeds.

Tb, not so much.

Joe



[Index of Archives]     [IETF Annoucements]     [IETF]     [IP Storage]     [Yosemite News]     [Linux SCTP]     [Linux Newbies]     [Mhonarc]     [Fedora Users]

  Powered by Linux