diff --git a/doc/MediaSigning.xml b/doc/MediaSigning.xml
index 9cd42f640..2c13ea45c 100644
--- a/doc/MediaSigning.xml
+++ b/doc/MediaSigning.xml
@@ -4,19 +4,19 @@
Media Signing SpecificationMedia Signing
- 24.12
+ 25.06ONVIF™www.onvif.org
- December, 2024
+ June, 2025
- 2022-2024
+ 2022-2025ONVIF™ All rights reserved.
@@ -48,6 +48,14 @@
First release
+
+ 25.06
+ Dec 2025
+
+ Ottavio Campana
+
+ Added Annex D for C2PA interoperability
+
@@ -1379,5 +1387,246 @@
IETF RFC 3447 Public-Key Cryptography Standards (PKCS) #1: RSA Cryptography Specifications
Version 2.1<>
+ C2PA Specifications Version 2.1
+ <>
+
+
+ C2PA interoperability
+ In C2PA, provenance generally refers to the facts about the history of a piece of digital
+ content assets (image, video, audio recording, document). Content Credentials enables the
+ secure binding of statements of provenance data to instances of content. These provenance
+ statements are called assertions in a Content Credential. They may include assertions about
+ who created the content and how, when, and where it was created.
+ This Annex defines the assertions necessary to embed an ONVIF-compliant digitally signed
+ video feed into a C2PA compliant file.
+
+ Overview
+ The ONVIF-defined assertion are split in two group in order to be able to keep track of
+ two possible use cases:
+
+
+ The video is generated and signed by a device, but the MP4 file is generated by a
+ client.
+
+
+ The video is generated and signed by a device that support local recording and that
+ generates the MP4 autonomously.
+
+
+ Therefore, the org.onvif.c2pa.device assertion must always be
+ populated by the device, while the org.onvif.c2pa.client assertion shall
+ be populated either by the client or by the device.
+
+
+ C2PA assertions
+ The following C2PA assertions are defined to extend the standard C2PA ones:
+
+
+
+
+ ONVIF device information
+ This assertion is used to embed in teh C2PA file informtion about the device that generated the signed video feed.
+
+
+ ONVIF-defined C2PA device assertions
+
+
+
+
+
+
+
+
+ Name
+
+
+ Type
+
+
+ Required
+
+ Property description
+
+
+
+
+
+ FirmwareVersion
+
+
+ String
+
+
+ No
+
+
+ The version of the FW running on the device that generated the RTSP stream
+ with the digital signatures.
+ If this field is populated, it must match the value in the tag.
+
+
+
+ SerialNumber
+
+
+ String
+
+ No
+
+ The serial number of the device that generated the RTSP stream with the
+ digital signatures.
+ If this field is populated, it must match the value in the tag.
+
+
+
+
+ Manufacturer
+
+
+ String
+
+ No
+
+ The manufacturer of the device that generated the RTSP stream with the
+ digital signatures.
+ If this field is populated, it must match the value in the tag.
+
+
+
+
+ Certificate
+
+
+ String
+
+ Yes
+ The certificate chain in PEM format
+ If this field is populated, it must match the value in the tag.
+
+
+
+
+
+
+
+ ONVIF client information
+ This assertion is used to embed in the C2PA file information about the client that exported the signed video feed.
+
+
+ ONVIF-defined C2PA recorder assertions
+
+
+
+
+
+
+
+
+ Name
+
+
+ Type
+
+
+ Required
+
+ Property description
+
+
+
+
+
+ SoftwareVersion
+
+
+ String
+
+
+ No
+
+
+ The version of the software that generated the C2PA-compliant MP4
+ file.
+ If this field is populated, it must match the value in the tag.
+
+
+
+ Software
+
+
+ String
+
+ No
+ The name of the software that generated the C2PA-compliant MP4
+ file.
+
+
+
+ ExportUnitMac
+
+
+ String
+
+ Yes
+ The unique physical MAC address of the entity that generated the MP4 file.
+
+
+
+