The scope of the DASH-IF InterOperability Points (IOPs) defined in this document is to provide support for high-quality video distribution for over the top services using H.264/AVC and H.265/HEVC. Both live and on-demand services are supported. The specified features enable relevant use cases including on-demand, live services, ad insertion, trick modes, seek preview, content protection and subtitling. Extensions for multi-channel audio and next generation audio with different codecs as well as extensions to video different codecs and Ultra High Definition are defined.
Any identified bugs or missing features may be submitted through the DASH-IF issue tracker at https://gitreports.com/issue/Dash-Industry-Forum/DASH-IF-IOP.
Note that version 4.2 is published as an add on to v4.1, but with the next version it is expected that a either a multipart version or a restructured version will be generated, with a major editorial updates. The new version is expected to be available by the fall of 2018.
The material contained herein is provided on an "AS IS"
basis and to the maximum extent permitted by applicable law, this material is
provided AS IS, and the authors and developers of this material and DASH-IF
hereby disclaim all other warranties and conditions, either express, implied or
statutory, including, but not limited to, any (if any) implied warranties,
duties or conditions of merchantability, of fitness for a particular purpose,
of accuracy or completeness of responses, of workmanlike effort, and of lack of
negligence.
In addition, this document may include references to documents
and/or technologies controlled by third parties. Those third party
documents and technologies may be subject to third party rules and licensing
terms. No intellectual property license, either implied or express, to
any third party material is granted to you by this document or DASH-IF.
DASH-IF makes no any warranty whatsoever for such third party material.
Note that technologies included in this document and for which no
test and conformance materi-al is provided, are only published as a candidate
technologies, and may be removed if no test material is provided before
releasing a new version of this guidelines document. For the availability of
test material, please check http://www.dashif.org.
Guidelines
for Implementation: DASH-IF
Interoperability Points
Acronyms, abbreviations and definitions
2.1. Relation to MPEG-DASH and other DASH
specifications
2.2. Compatibility and Extensions to Earlier
Versions
2.2.1. Summary of Version 3 Modifications
2.2.2. Backward-Compatibility Considerations
2.3.3. Mapping to DASH-IF Assets
2.4. Definition and Usage of Interoperability
Points
2.4.1. Profile Definition in ISO/IEC 23009-1
2.4.3. Interoperability Points and Extensions
3.2.2. Media Presentation Description constraints for v1
& v2 Clients
3.2.3. Segment format constraints
3.2.4. Presence of Attributes and Elements
3.2.5. MPD Dimension Constraints
3.2.8. Bandwidth and Minimum Buffer Time
3.2.10. Adaptation Set Constraints
3.2.11. Media Time Information of Segment
3.2.12. Content Offering with Periods
3.2.13. Adaptation Set Media Type
3.2.14. Seek Preview and Thumbnail Navigation
3.3. Client Implementation Requirements and
Guidelines
3.3.4. DASH Client Requirements
3.4. Transport and Protocol-Related Issues
3.4.2. Server Requirements and Guidelines
3.4.3. Client Requirements and Guidelines
3.4.4. Transforming Proxies and Other Adaptation Middleboxes
3.5. Synchronization Considerations
3.6. Considerations for Live Services
3.7. Considerations on Ad Insertion
3.8. Switching across Adaptation Sets
3.9. Annotation and Client Model for Content
Selection
3.9.2. Adaptation Set Labeling Options for Selection
3.9.4. Signalling Requirements and Recommendations
3.9.5. Client Processing Reference Model
4.2. Overview Dynamic and Live Media
Presentations
4.3.1. Background and Assumptions
4.3.3. Service Offering Requirements and Guidelines
4.3.4. Client Operation, Requirements and Guidelines
4.3.5. Additional DVB-DASH alignment aspects
4.3.6. Considerations on live edge
4.4. Simple Live Service Offering including MPD
Updates
4.4.1. Background and Assumptions
4.4.3. Service Offering Requirements and Guidelines
4.4.4. MPD-based Live Client Operation based on MPD
4.5. MPD and Segment-based Live Service
Offering
4.5.2. Service Offering Requirements and Guidelines
4.5.3. Client Requirements and Guidelines
4.6. Provisioning of Live Content in On-Demand
Mode
4.6.2. Content Offering Requirements and Recommendations
4.6.4. Transition Phase between Live and On-Demand
4.7. Availability Time Synchronization between
Client and Server
4.7.2. Service Provider Requirements and Guidelines
4.7.3. Client Requirements and Guidelines
4.8.2. Tools for Robust Operations
4.8.3. Synchronization Loss of Segmenter
4.8.6. Swapping across Redundant Tools
4.8.7. Service Provider Requirements and Guidelines
4.8.8. Client Requirements and Guidelines
4.10. Trick Mode for Live Services
4.10.2. Service Offering Requirements and Recommendations
4.10.3. Client Implementation Guidelines
4.10.4. Conversion for Live-to-VoD for Trick Mode Adaptation
Sets
4.11.2. Reliable and Consistent-Delay Live Service
4.11.3. Relevant DASH-IF IOP Technologies
4.11.5. Client Support Considerations
5.3. Server-based Architecture
5.3.5. Use of query parameters