|
|
This topic comprises 2 pages: 1 2
|
|
Author
|
Topic: KDM timing question
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Carsten Kurz
Film God
Posts: 4340
From: Cologne, NRW, Germany
Registered: Aug 2009
|
posted 10-17-2014 05:06 PM
It could be, from what Steve describes, but on a long continued program like this, it could just as well have been the occasional hickup.
It could easily be tested over night, with the lamp being off.
It's true, though, that the show may not actually stop but only the picture will vanish. I remember that when I recently played with the Doremi and NC900C with HD-SDI/Enigma, I sometimes pulled out the ethernet cable from the projector. I don't know currently wether I had encrypted content running - but I think the audio continued, the picture went black, and the Doremi indicated a 'connection lost'.
Steve is right in that normally you would do something like this with normal single feature SPLs and scheduling.
Of course, that wouldn't work if you intentionally want to spread the key expiration window for one of these features appearing in the later schedules, because scheduling does not keep the keys from expiring after the assigned validity window ;-)
- Carsten
| IP: Logged
|
|
Marcel Birgelen
Film God
Posts: 3357
From: Maastricht, Limburg, Netherlands
Registered: Feb 2012
|
posted 10-19-2014 09:37 AM
quote: Steve Guttag The problem would be when the TLS session is broken/restarted...the show would stop. Why not just put the shows on the schedule back-to-back-to-back rather than one large show (to make a 6-hour performance. What theatre doesn't want periodic breaks to "lets all go to the lobby." Who's bladder is so good that they want to hold it for 6-hours?
It doesn't really make sense to have one >6h feature. So, besides the oddball situation where somebody manages to put a few movies back to back into a single feature (apparently studios manage to do so, at least according to Philip), you would never encounter the problem in production. It's still interesting to know though.
I guess this "limited time-frame of TLS session validity", if it's true (because like you pointed out, the specs are at least a bit ambiguous here), has probably been implemented as a security measure, to avoid data being transferred with the same session key for too long...
Newer implementations of TLS support a "New Session Ticket" extension to the TLS protocol. This allows a renewed key exchange on an open session. Some "SSL VPN" implementations actively use it. It eliminates some overhead, especially over public IP links, but still, the key exchange will introduce some interruption in the actual stream and given the fact that you cannot really buffer much data without causing inherent latency issues, this will probably also cause some noticeable hickups/frame drops if it's actually implemented.
| IP: Logged
|
|
|
|
All times are Central (GMT -6:00)
|
This topic comprises 2 pages: 1 2
|
Powered by Infopop Corporation
UBB.classicTM
6.3.1.2
The Film-Tech Forums are designed for various members related to the cinema industry to express their opinions, viewpoints and testimonials on various products, services and events based upon speculation, personal knowledge and factual information through use, therefore all views represented here allow no liability upon the publishers of this web site and the owners of said views assume no liability for any ill will resulting from these postings. The posts made here are for educational as well as entertainment purposes and as such anyone viewing this portion of the website must accept these views as statements of the author of that opinion
and agrees to release the authors from any and all liability.
|