|
329 | 329 |
|
330 | 330 | <main role="main" class="container"> |
331 | 331 |
|
332 | | - <h3 id="2nd-community-review-and-public-special-session-for-candidate-technical-specification-dash-if-forensic-ab-watermarking">2nd Community Review and public Special Session for Candidate Technical Specification: DASH-IF Forensic A/B Watermarking</h3> |
333 | | -<p>On February 2nd, 2023, DASH-IF published the 2nd Community Review for the new Candidate Technical Specification: DASH-IF Forensic A/B Watermarking. The details of the community review are available <a href="https://dashif.org/guidelines/others/#dash-if-candidate-technical-specification-dash-if-forensic-ab-watermarking">here</a> and the published document is available <a href="https://dash-industry-forum.github.io/docs/IOP-Guidelines/DASH-IF-CTS-00XX-AB-Watermarking-0.9.pdf">here (pdf)</a> .</p> |
334 | | -<p><a href="" target="_blank" rel="noopener noreferrer"><img height="300px" src="https://dashif.org/img/Watermarking-Concept.png" alt="https://dashif.org/guidelines/others/#dash-if-candidate-technical-specification-dash-if-forensic-ab-watermarking" /></a></p> |
335 | | -<p>This second version is a significant update addressing all comments received during the initial community review.</p> |
336 | | -<p>The scope of this work is the definition of an architecture and an Application Programming Interface (API) for supporting A/B forensic watermarking for Over-The-Top (OTT) on content that is delivered in an Adaptive Bitrate (ABR) format. To the possible extend, the proposed solutions do not make assumptions on the ABR technology that is being used, it can be for example, DASH or HLS. A/B forensic watermarking means that at least two watermarked versions of content (variant A and variant B) are delivered up to a CDN edge server from the encoder. The edge server is responsible for delivering either the A or B variant of every segment to the device. While digital watermarking can be used for different use cases, this work will focus on forensic use cases. In this context, it is used to define the origin of content leakage. The watermarking technology modifies media content in a robust and invisible way in order to encode a unique identifier, e.g., a unique session ID. The embedded watermark provides means to identify where the media content, that has been redistributed without authorization, is coming from. In other words, the watermark is used to forensically trace the origin of content leakage.</p> |
337 | | -<p>This document is a candidate Technical Specification. DASH-IF is expecting to publish this initially, but to submit the specification ETSI, for which DASH-IF has a PAS agreement. It is expected that the final document will be published as an ETSI technical specification.</p> |
338 | | -<p>Community review is open until February 28, 2023. Publication is expected by March 31, 2023 as DASH-IF version and by June 30, 2023 as ETSI TS. Comments may be submitted through the <a href="https://github.com/Dash-Industry-Forum/Watermarking/issues">github</a>.</p> |
339 | | -<p>In order to support the public community, the specification will be introduced in a <a href="https://dashif.org/events/special-sessions/#february-10-2023-dash-if-ab-watermarking">public special session</a> on February 10, 2023 at 9am pacific, calendar details are <a href="https://members.dashif.org/wg/DASH/calendar/event/103/2023-02-10">here (Causeway)</a> and <a href="https://github.com/Dash-Industry-Forum/Watermarking/wiki/Special-Session-Announcement">here (github)</a>.</p> |
340 | | -<p>This is the result of the work in the Content Protection and Security task force in DASH-IF lead by <a href="https://www.linkedin.com/in/laurentpiron/">Laurent Piron</a> from NAGRA and has been done in collaboration between watermarking technology providers (NAGRA, Synamedia, Irdeto, Verimatrix), CDN providers (Akamai, AWS) and other DASH-IF members.</p> |
| 332 | + <h3 id="dash-if-announces-public-community-review-for-candidate-specification-watermarking-api-for-encoder-integration">DASH-IF announces Public Community Review for Candidate Specification: Watermarking API for Encoder Integration</h3> |
| 333 | +<p>On December 6th, 2024, DASH-IF published the “<a href="https://github.com/user-attachments/files/18038517/DASH-IF-CTS-Watermarking-API-v0.9.0.-.Community.Review.pdf">DASH-IF Candidate Specification: Watermarking API for Encoder Integration</a>” for community review.</p> |
| 334 | +<p>DASH-IF and UHD Forum have updated the “Watermarking API for encoder integration” to cope with the latest updates on watermarking. The main updates to the document comprise:</p> |
| 335 | +<ul> |
| 336 | +<li>the definition of interfaces to manage watermark pace information and be interoperable with DASH-IF Forensic A/B Watermarking (ETSI TS 104 002)</li> |
| 337 | +<li>the support for multiple processing pipelines to process several ABR representations in a single WMP instance;</li> |
| 338 | +<li>the clarification of ABR segmentation signaling to help the WMP enforcing its watermark pace making logic;</li> |
| 339 | +<li>the explicit signaling of Variant labels to avoid ambiguity in the specification; |
| 340 | +This updated specification is expected to fill the gap with the real needs of the market today.</li> |
| 341 | +</ul> |
| 342 | +<p><a href="https://github.com/user-attachments/files/18038517/DASH-IF-CTS-Watermarking-API-v0.9.0.-.Community.Review.pdf" target="_blank" rel="noopener noreferrer"><img height="300px" src="https://dashif.org/img/watermarking%20API.png" alt="" /></a></p> |
| 343 | +<p>This is the result of the work in the Content Protection and Security task force in DASH-IF lead by <a href="https://www.linkedin.com/in/laurentpiron/">Laurent Piron</a> from NAGRA and has been done in collaboration between watermarking technology providers (Elemental, Irdeto, Nagravision and Synamedia) and other DASH-IF members.</p> |
| 344 | +<p>The community review is open until January 15th, 2025. Publication is expected by February 26, 2025. Comments may be submitted through the <a href="https://github.com/Dash-Industry-Forum/Watermarking/issues">github</a>.</p> |
341 | 345 |
|
342 | 346 |
|
343 | 347 | </main> |
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?v=4&size=40){kind=avatar}
0 commit comments