Proposal for connecting ONVIF and C2PA #508
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -4,19 +4,19 @@ | |||||||||
| <info> | ||||||||||
| <title>Media Signing Specification</title> | ||||||||||
| <titleabbrev>Media Signing</titleabbrev> | ||||||||||
| <releaseinfo>25.06</releaseinfo> | ||||||||||
| <author> | ||||||||||
| <orgname>ONVIF™</orgname> | ||||||||||
| <uri>www.onvif.org</uri> | ||||||||||
| </author> | ||||||||||
| <pubdate> June, 2025</pubdate> | ||||||||||
| <mediaobject> | ||||||||||
| <imageobject> | ||||||||||
| <imagedata fileref="media/logo.png" contentwidth="60mm"/> | ||||||||||
| </imageobject> | ||||||||||
| </mediaobject> | ||||||||||
| <copyright> | ||||||||||
| <year>2022-2025</year> | ||||||||||
| <holder>ONVIF™ All rights reserved.</holder> | ||||||||||
| </copyright> | ||||||||||
| <legalnotice> | ||||||||||
|
|
@@ -48,6 +48,14 @@ | |||||||||
| </author> | ||||||||||
| <revremark>First release</revremark> | ||||||||||
| </revision> | ||||||||||
| <revision> | ||||||||||
| <revnumber>25.06</revnumber> | ||||||||||
| <date>Dec 2025</date> | ||||||||||
| <author> | ||||||||||
| <personname>Ottavio Campana</personname> | ||||||||||
| </author> | ||||||||||
| <revremark>Added Annex D for C2PA interoperability</revremark> | ||||||||||
| </revision> | ||||||||||
| </revhistory> | ||||||||||
| </info> | ||||||||||
| <chapter xml:id="chapter_zhs_njq_bwb"> | ||||||||||
|
|
@@ -1379,5 +1387,246 @@ | |||||||||
| <para>IETF RFC 3447 Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications | ||||||||||
| Version 2.1</para> | ||||||||||
| <para role="reference"><<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://tools.ietf.org/rfc/rfc3447.txt"/>></para> | ||||||||||
| <para>C2PA Specifications Version 2.1</para> | ||||||||||
| <para role="reference"><<link xmlns:xlink="http://www.w3.org/1999/xlink" xlink:href="https://c2pa.org/specifications/specifications/2.1/index.html"/>></para> | ||||||||||
bjornvolcker marked this conversation as resolved.
Show resolved
Hide resolved
|
||||||||||
| </appendix> | ||||||||||
| <appendix> | ||||||||||
| <title>C2PA interoperability</title> | ||||||||||
|
Contributor
There was a problem hiding this comment. I think it is a good idea to put this here in an annex of Media Signing, but there are alternatives. Here are a few example use cases
I'm skipping for now discussions on efficiency in terms of bitrate increase and how using C2PA scales with devices. The main question is if this proposal PR should include also C2PA assertions without ONVIF Media Signing? |
||||||||||
| <para>In C2PA, provenance generally refers to the facts about the history of a piece of digital | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| content assets (image, video, audio recording, document). Content Credentials enables the | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| secure binding of statements of provenance data to instances of content. These provenance | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| statements are called assertions in a Content Credential. They may include assertions about | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| who created the content and how, when, and where it was created. </para> | ||||||||||
| <para>This Annex defines the assertions necessary to embed an ONVIF-compliant digitally signed | ||||||||||
| video feed into a C2PA compliant file.</para> | ||||||||||
| <section> | ||||||||||
| <title>Overview</title> | ||||||||||
| <para>The ONVIF-defined assertion are split in two group in order to be able to keep track of | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| two possible use cases:</para> | ||||||||||
| <itemizedlist> | ||||||||||
| <listitem> | ||||||||||
| <para>The video is generated and signed by a device, but the MP4 file is generated by a | ||||||||||
| client.</para> | ||||||||||
| </listitem> | ||||||||||
| <listitem> | ||||||||||
| <para>The video is generated and signed by a device that support local recording and that | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| generates the MP4 autonomously.</para> | ||||||||||
| </listitem> | ||||||||||
| </itemizedlist> | ||||||||||
| <para>Therefore, the <emphasis>org.onvif.c2pa.device</emphasis> assertion must always be | ||||||||||
| populated by the device, while the <emphasis>org.onvif.c2pa.client</emphasis> assertion shall | ||||||||||
| be populated either by the client or by the device.</para> | ||||||||||
| </section> | ||||||||||
| <section> | ||||||||||
| <title>C2PA assertions</title> | ||||||||||
| <para>The following C2PA assertions are defined to extend the standard C2PA ones:</para> | ||||||||||
| <para> | ||||||||||
| <table frame="all"> | ||||||||||
| <title>ONVIF-defined C2PA assertions</title> | ||||||||||
| <tgroup cols="4" align="left"> | ||||||||||
| <colspec colname="c1" colnum="1"/> | ||||||||||
| <colspec colname="c2" colnum="2"/> | ||||||||||
| <colspec colname="c3" colnum="3"/> | ||||||||||
| <colspec colname="c4" colnum="4"/> | ||||||||||
| <thead> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Type</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Assertion</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Schema</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Serialization</para> | ||||||||||
| </entry> | ||||||||||
| </row> | ||||||||||
| </thead> | ||||||||||
| <tbody> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>ONVIF device information</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>org.onvif.c2pa.device</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>ONVIF</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>JSON-LD</para> | ||||||||||
| </entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>ONVIF client information</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>org.onvif.c2pa.recorder</para> | ||||||||||
|
Contributor
There was a problem hiding this comment. It says |
||||||||||
| </entry> | ||||||||||
| <entry>ONVIF</entry> | ||||||||||
| <entry> | ||||||||||
| <para>JSON-LD</para> | ||||||||||
| </entry> | ||||||||||
| </row> | ||||||||||
| </tbody> | ||||||||||
| </tgroup> | ||||||||||
| </table> | ||||||||||
| </para> | ||||||||||
| <section> | ||||||||||
| <title>ONVIF device information</title> | ||||||||||
| <para>This assertion is used to embed in teh C2PA file informtion about the device that generated the signed video feed.</para> | ||||||||||
|
Contributor
There was a problem hiding this comment.
Suggested change
Contributor
There was a problem hiding this comment. @ocampana-videotec I have also provided a different suggestion to this sentence just an additional minor update over jmelancongen suggestion which is equally good.
Contributor
There was a problem hiding this comment.
Suggested change
|
||||||||||
| <para> | ||||||||||
| <table frame="all"> | ||||||||||
| <title>ONVIF-defined C2PA device assertions</title> | ||||||||||
| <tgroup cols="4" align="left"> | ||||||||||
| <colspec colname="c1" colnum="1"/> | ||||||||||
| <colspec colname="c2" colnum="2"/> | ||||||||||
| <colspec colname="c3" colnum="3"/> | ||||||||||
| <colspec colname="c5" colnum="4"/> | ||||||||||
| <thead> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Name</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Type</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Required</para> | ||||||||||
| </entry> | ||||||||||
| <entry>Property description</entry> | ||||||||||
| </row> | ||||||||||
| </thead> | ||||||||||
| <tbody> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>FirmwareVersion</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>No</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>The version of the FW running on the device that generated the RTSP stream | ||||||||||
| with the digital signatures.</para> | ||||||||||
| <para>If this field is populated, it must match the value in the <xref linkend="section_r3s_njq_bwb"/> tag.</para></entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>SerialNumber</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry>No</entry> | ||||||||||
| <entry> | ||||||||||
| <para>The serial number of the device that generated the RTSP stream with the | ||||||||||
| digital signatures.</para> | ||||||||||
| <para>If this field is populated, it must match the value in the <xref linkend="section_r3s_njq_bwb"/> tag.</para> | ||||||||||
| </entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Manufacturer</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry>No</entry> | ||||||||||
| <entry> | ||||||||||
| <para>The manufacturer of the device that generated the RTSP stream with the | ||||||||||
| digital signatures.</para> | ||||||||||
| <para>If this field is populated, it must match the value in the <xref linkend="section_r3s_njq_bwb"/> tag.</para> | ||||||||||
|
Contributor
There was a problem hiding this comment. The multiple paragraphs don't seem to render properly in the tables according to Not sure if that's a general issue of specific to the developer website? |
||||||||||
| </entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Certificate</para> | ||||||||||
|
Contributor
There was a problem hiding this comment. Adding the certificate chain is a good idea, and probably some kind of minimum, or could it be enough to add a hash of the certificate chain to lower the size? I see one problem with only adding the certificate chain because it is the same for all videos from that camera. For provenance that is enough, but if we also want to add some kind of "check" of authenticity we need something unique from the video, for example, hashes of the SEI frames. We could add another entry here for that. |
||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry>Yes</entry> | ||||||||||
| <entry><para>The certificate chain in PEM format</para> | ||||||||||
| <para>If this field is populated, it must match the value in the <xref linkend="section_v3s_njq_bwb"/> tag.</para></entry> | ||||||||||
| </row> | ||||||||||
| </tbody> | ||||||||||
| </tgroup> | ||||||||||
| </table> | ||||||||||
| </para> | ||||||||||
| </section> | ||||||||||
| <section> | ||||||||||
| <title>ONVIF client information</title> | ||||||||||
| <para>This assertion is used to embed in the C2PA file information about the client that exported the signed video feed.</para> | ||||||||||
| <para> | ||||||||||
| <table frame="all"> | ||||||||||
| <title>ONVIF-defined C2PA recorder assertions</title> | ||||||||||
| <tgroup cols="4" align="left"> | ||||||||||
| <colspec colname="c1" colnum="1"/> | ||||||||||
| <colspec colname="c2" colnum="2"/> | ||||||||||
| <colspec colname="c3" colnum="3"/> | ||||||||||
| <colspec colname="c5" colnum="4"/> | ||||||||||
| <thead> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Name</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Type</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>Required</para> | ||||||||||
| </entry> | ||||||||||
| <entry>Property description</entry> | ||||||||||
| </row> | ||||||||||
| </thead> | ||||||||||
| <tbody> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>SoftwareVersion</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>No</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>The version of the software that generated the C2PA-compliant MP4 | ||||||||||
| file.</para> | ||||||||||
| <para>If this field is populated, it must match the value in the <xref linkend="section_o3s_njq_bwb"/> tag.</para></entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>Software</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry>No</entry> | ||||||||||
| <entry>The name of the software that generated the C2PA-compliant MP4 | ||||||||||
| file.</entry> | ||||||||||
| </row> | ||||||||||
| <row> | ||||||||||
| <entry> | ||||||||||
| <para>ExportUnitMac</para> | ||||||||||
| </entry> | ||||||||||
| <entry> | ||||||||||
| <para>String</para> | ||||||||||
| </entry> | ||||||||||
| <entry>Yes</entry> | ||||||||||
| <entry><para>The unique physical MAC address of the entity that generated the MP4 file.</para></entry> | ||||||||||
| </row> | ||||||||||
| </tbody> | ||||||||||
| </tgroup> | ||||||||||
| </table> | ||||||||||
| </para> | ||||||||||
| </section> | ||||||||||
| </section> | ||||||||||
| </appendix> | ||||||||||
| </book> | ||||||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to specify a version? It would be great if don't have to maintain this to get the latest C2PA version all the time, or do we want to stay at 2.1?