19 May
2014
19 May
'14
9:13 p.m.
On Mon, 19 May 2014, Carsten Kurz wrote:
That's why TKR looks so simple (and seems to be
favoured by
now): The Equipment can obtain KDMs for it's own certificate
all on itself, automatically or manually triggered, with the
'coresponding lookup address' comunicated in the CPL, so you
don't need to trust anyone, you do not even need to know where
the cinema is. It creates more lookup traffic, but no properly
maintained database is needed. The KDMs are created or stored
at the site who owns the right for the content. That could be
content owners, indies themselves, or service companies.
What identifier does the TKR system offer when asking for a KDM?
How does the content owner know that the requesting system is
cinema A, which has booked the film, not cinema B which hasn't?
I think, for now it would be sufficient to put up a
help page
on the dcp-o-matic site depicting how certificates can be
retrieved for various type of equipment, what the difference
is between serial number and certificate, etc. That would also
be compatible with DCP-o-matics current way to create KDMs
from locally stored certificates.
That would be a good idea.
Best regards
Carl