hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 2 References | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 2.1 Normative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. Referenced documents which a... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 2.2 Informative references | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the referenced document (including any amendments) applies. NOTE: While any hyperlinks i... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 3 Definition of terms, symbols and abbreviations | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 3.1 Terms | For the purposes of the present document, the terms given in ETSI TS 102 796 [1] and the following apply: AIT server: server that for provides broadcast-related AIT(s) over broadband audio watermark segment: VP1 audio watermark segment as defined in clause 5.2.5 of ATSC A/336 [9] authoritative FQDN: internet domain for... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 3.2 Symbols | Void. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 3.3 Abbreviations | For the purposes of the present document, the abbreviations given in ETSI TS 102 796 [1] and the following apply: STB Set-Top Box TTL Time To Live |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 4 Overview (informative) | The methodology is modelled after RadioDNS [i.1], using certain parameters provided in the broadcast for the identification of services. These could be digital parameters extracted from DVB Service Information, e.g. DVB-SI [3], or parameters encoded in a digital watermark that is inserted for the purpose of enabling th... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5 HbbTV® Application Discovery over Broadband | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.1 Introduction | This clause defines a method for discovery and signalling of broadcast-related applications, which are discovered and signalled via broadband, instead of being signalled as part of the broadcast channel as defined in clause 7.2.3.1 of ETSI TS 102 796 [1]. The structure of this clause reflects the fact that the present ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.2 Discovering broadcaster AIT servers | The terminal shall attempt to discover broadcasters' AIT servers according to the process as described below. This process is independent from service selection by the user and shall be executed in the following cases: • For each service in the terminal's channel list (see ETSI TS 102 796 [1] and the OIPF DAE specifica... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.3 Service Identification | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.3.1 Service Identification in the presence of DVB Service Information | For terminals supporting application discovery over broadband using DVB Service Information, identification of a service shall be provided by a combination of DVB service parameters. The parameters are defined in table 1. Table 1: HbbTVDNS parameters Parameter Description Value Country 3-character country code as speci... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.3.2 Service Identification using ATSC 3 watermarks | For watermarks whose payload is according to clause 5.2.3 of ATSC A/336 [9], services are identified using the server_field (Server Code) from the vp1_payload structure. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.4 HbbTV® DNS FQDN Construction | 5.4.1 HbbTV® DNS FQDN Construction in the presence of DVB Service Information The terminal shall construct a HbbTV® DNS FQDN as follows: <onid>.<servicename>.<country>.dvb.hbbtvdns.org The terminal shall extract and re-encode all the bytes from the service_name field in the service_descriptor in the SDT as transmitted ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.4.2 HbbTV® DNS FQDN Construction using ATSC 3 watermarks | For watermarks whose payload is according to clause 5.2.3 of ATSC A/336 [9], the terminal shall construct an HbbTV® DNS FQDN as follows; <server_field>.a336.watermark.hbbtvdns.org The server_field from the most recently detected audio watermark shall be used, except in the Verified video watermark detected only state (... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.5 Resolution of Authoritative FQDN | The terminal shall perform a DNS request using the HbbTV® DNS FQDN, to acquire the Authoritative FQDN. The response to this request contains a single CNAME record [11] containing the Authoritative FQDN of the service provider. If no CNAME is returned (a "negative response"), then a broadband-discoverable AIT service ha... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.6 AIT retrieval | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.6.1 AIT retrieval in the presence of DVB Service Information | The terminal shall retrieve the AIT by performing an HTTPS GET where the TLS client connection request includes the Authoritative FQDN in the Server Name Indication (SNI) as specified in IETF RFC 6066 [7] request to the following address: https://<domain-name>/xml.aitx?onid=<onid>&network=<network>&servicename=<service... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.6.2 AIT retrieval when ATSC 3 watermarks are used | The terminal shall retrieve the AIT by performing an HTTPS GET request to the following address: https://<domain-name>/xml.aitx?server_field=<server_field>&interval_field=<interval_field> The <domain-name> shall be the Authoritative FQDN obtained as specified in clause 5.5 and cached as specified in clause 5.2. The ser... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 5.6.3 Common AIT retrieval requirements | When performing AIT retrieval according to clauses 5.6.1 or 5.6.2, the following requirements shall apply: 1) The requirements of clause 7.3.2.5 of ETSI TS 102 796 (V1.4.1) [2] shall apply to AIT retrieval regardless of what is ETSI TS 102 796 [1]. 2) The response to this request shall have the following MIME type: app... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6 Service and application model | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.1 Introduction | This clause defines procedure for use by terminals to perform application discovery, signalling, and lifecycle management of applications via broadband. These procedures include: • Priority between application discovery from broadcast AITs, DVB Service Information, and watermarks in scenarios where multiple of these me... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.2 Priority between application discovery mechanisms | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.2.1 Services received via DVB transmission | Broadcast AIT reception as defined in ETSI TS 102 796 [1], application discovery over broadband using DVB Service Information and application discovery over broadband using watermarks (both the latter as defined in the present document) are all applicable techniques for application discovery. When more than one of thes... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.2.2 Services received via HDMI | The only applicable application discovery mechanism for services received via HDMI is application discovery over broadband using watermarks (as defined in the present document). |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.2.3 Services received via other input sources | Application discovery over broadband using watermarks (as defined in the present document) may also be applicable to non-DVB input sources such as IPTV or OTT. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.3 Watermark states and transitions | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.3.1 State machine | Table 4 defines the states and state transitions for watermark detection and how this maps to the HbbTV® application discovery process. States are defined as follows: 1) No watermark detected (initial state) 2) Unverified Video watermark detected only 3) Verified Video watermark detected only 4) Audio watermark detecte... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.3.2 Verification of video watermarks | A video watermark shall be considered verified by an audio watermark when either the server code in the two watermarks is the same or the server code in the two watermarks is not the same but the video watermark identifies components in the same service as defined by the channel element (as defined in clause 7.1.2) of ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.3.3 Monitoring for watermarks | Terminals that support application discovery based on ATSC3 watermarks as defined in the present document shall monitor for audio watermarks [12] and optionally video watermarks [13] when displaying content received over HDMI and optionally SCART, DVB transmission, and other external inputs for which application signal... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4 Application lifecycle when controlled by watermarks | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.1 Introduction | The application discovery process may be undertaken by an HbbTV® Terminal to discover and manage the lifecycle of HbbTV® applications. In accordance with the state machine specified in clause 6.3.1, application discovery is started, followed, and ends based on the detection and loss of watermarks. Clause 6.4.2 specifie... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2 Managing the HbbTV® application lifecycle | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.1 Introduction | Clause 6.3.1 specifies watermark-related events that cause the application discovery process to be started. To do this, the terminal shall acquire and process an AIT as specified in clause 6.4.2.2. After the application discovery process is started, and until loss of watermark occurs per clause 6.3.1, the terminal shal... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.2 Acquire and Process an AIT | The terminal shall acquire and process AITs by performing the following steps, in sequence: 1) If any of the following conditions a) to d) apply: a) AIT acquisition and processing was initiated as a result of a Query Flag change as specified in table 8 of clause 6.3.1; b) the terminal is performing a scheduled AIT upda... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.3 AIT Validity | When application discovery is performed using watermarks, an AIT shall be considered valid for the presently detected watermark when the following conditions are all met: 1) The server code in the presently detected watermark is present in either a videoComponent or an audioComponent (as appropriate for the type of med... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.4 Watermark media timeline | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.4.1 Introduction | The watermark media timeline is a stable reference frame for associating media time to watermarked content (i.e. a timebase timeline per ETSI TS 103 286-2 [i.2], similar to TEMI (see ISO/IEC 13818-1:2018 [i.3]) that enables terminals and HbbTV® applications to precisely synchronize elements of the media presentation, r... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.4.2 Initializing the watermark media timeline | The terminal shall select a current audio component from among those audioComponent elements present in the AIT with watermark@serverField value equal to the server_field value present in the most recently detected audio watermark (the "candidate audio components") as follows: 1) If there are any candidate audio compon... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.4.3 Determining the Media Time of watermarked content | After the watermark media timeline is initialized, it provides a mapping for associating a media time with points in time in the watermarked content. During an audio watermark segment (either with or without the detection of video watermarks), the media time associated with each audio sample in the watermark segment sh... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.2.4.4 Maintaining synchronization to the Watermark Media Timeline | During an audio watermark segment (either with or without the detection of video watermarks), after the watermark media timeline for an audio watermark segment has been initialized in accordance with clause 6.4.2.4.2, upon detection of each subsequent watermark payload in an audio watermark segment, terminals shall cal... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.3 Loss of watermark | Clause 6.3.1 specifies the conditions under which a loss of watermark detection condition is indicated. When this happens, the following shall apply: • If a broadcast-related HbbTV® application is running that the user has not activated (see clause 10.2.2.1 of ETSI TS 102 796 [1]), that application shall be stopped as ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 6.4.4 Transitioning between HbbTV® Application types | Terminals shall support one broadcast-related HbbTV® application starting another broadcast-related HbbTV® application based on "dvb:" URLs and use the AIT retrieved using watermark data for the current channel to resolve the URL. If a broadcast-related HbbTV® application starts a broadcast-independent application then... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7 Formats and protocols | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.1 Signalling of applications | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.1.1 XML AIT for Broadcast-related broadband application discovery | The AIT for broadcast-related applications discovered over broadband shall be encoded in XML similarly to the way defined in ETSI TS 102 796 [1] for broadcast-independent applications. The XML file shall contain an ApplicationDiscovery record containing one or more <application> elements. The semantics of the fields an... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.1.2 XML AIT Extensions | When used with watermarking, the XML AIT format described in clause 5.4 of ETSI TS 102 809 [6] and extended in clause 7.2.3.2 of ETSI TS 102 796 [1] is further extended as defined in the following schema and in tables 11 and 12. The normative definition of this schema is found in the electronic attachments - see annex ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.2 Watermark formats | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.2.1 Introduction | The present document includes one audio watermark format and one video watermark format. The present document is structured to enable addition of other formats in the future. The present document makes extensive use of the data structures defined by ATSC in A/336 [9] - particularly the VP1 payload but also the dynamic ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 7.2.2 ATSC 3 Watermarks | The present document includes the ATSC 3 watermarks defined in ATSC A/334 [12] and ATSC A/335 [13]. If the content with the ATSC video watermark is encoded at very low bitrates (e.g. MPEG-2 at a fixed bitrate of 1 Mbit/s), it may not be possible to reliably extract the video watermark. It is not possible to provide an ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 8 Browser application environment | 8.1 Extensions to the application/oipfApplicationManager embedded object and the Application class The following additional property shall be supported on the Application class. readonly String lifecycleControl Description Indicates which signalling mechanism is controlling the lifecycle of the application reading the ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 8.2 Extensions to the MediaSynchroniser embedded object | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 8.2.1 Properties | The following properties are added to the MediaSynchroniser embedded object. function onTimeUpdate (Number currentTime, String reason) Description The function shall be called by the terminal to notify the application of changes in the media when any one or more of the following conditions apply: • The timeline has adv... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 8.2.2 Events | When any one or more of the listed conditions apply and no event handler for a timeupdate event is currently executing, the intrinsic event onTimeUpdate shall be generated and a corresponding DOM level 2 event shall be generated in the following manner. Intrinsic event Corresponding DOM 2 event DOM 2 Event properties o... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9 System integration | 9.1 Use of video/broadcast API and related classes with watermarking The following shall apply when application discovery using watermarking is employed, once the terminal has obtained a Discovered AIT corresponding to the currently received watermark and an HbbTV® application is running that has or creates a video/bro... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.2 Use of MediaSynchroniser API with watermarking | Terminals supporting application discovery over broadband using watermarking for an input (e.g. HDMI, broadcast, OTT, IPTV) shall support the use of the watermark media timeline defined in clause 6.4.2.4 as a type of timeline for MediaSynchroniser operations when that input is selected. The timeline selector for the wa... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.3 Use of Stream Events API | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.3.1 Stream events in the presence of DVB Service Information | When the broadcast does not carry an AIT, then it is also unlikely that other broadcast-carried HbbTV® functions like application transport with DSM-CC, stream events, etc., will be available in the video broadcast. Methods and properties related to these functions will be handled the same way as in ETSI TS 102 796 [1]... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.3.2.1 General | Applications where Application.lifecycleControl is "xmlait-atsc3" shall be able to register for stream events and receive stream events when detected according to clauses 9.3.2.2 and 9.3.2.3. This applies regardless of whether an application is an autostart application whose launch was initiated by the HbbTV® terminal ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.3.2.2 Events delivered in video watermarks | The dynamic_event_message() defined in ATSC A/336 [9] supports delivery of stream events in video watermarks that conform to the structure of events used in ATSC 3.0 broadcast delivery protocols. For HbbTV®, the A/336 protocol is extended to define the syntax and bitstream semantics of the Video Watermark Event Message... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.3.2.3 Deriving stream events from VP1 payloads | Applications shall be able to register to be notified when the value of the query_flag field changes in VP1 Payloads using the DSM-CC stream event API specified in clause 8.2.1 of ETSI TS 102 796 [1]. The target URL associated with the watermark query_flag event stream shall be urn:hbbtv:streamevent:a336:audio. The eve... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.4 Reliability and resilience | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.4.1 User interaction | Terminals shall operate reliably in response to (rapid) user interaction. Terminals shall keep operating the application discovery over broadband mechanisms reliably in the following events: • For streams obtained from HDMI: - Rapid appearance and disappearance of the video watermark (e.g. equivalent to opening and clo... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.4.2 Malformed or malicious inputs | Terminals shall be resilient to malformed, malicious inputs and/or operational errors that are likely to occur. Specifically, in the following circumstances, the terminal shall discard any malformed inputs and remain responsive to valid inputs in the future, including starting and stopping applications: • Failed DNS CN... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.4.3 Long-term use | On the application level, terminals shall reliably handle the following uses: • An application rapidly switching back and forth between broadcast-independent and broadcast-related modes 200 times. Terminals shall be resilient to transient error conditions that are likely to occur, as well as to conditions of low resour... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.4.4 Watermarks and XML-AIT | Terminals shall remain able to discover applications over broadband according to the present document when: • the VP1 payload query_flag field value is switched 200 times in a row; • there are 200 discontinuities in the VP1 payload Interval Code field; • the VP1 payload Server Code is changed 200 times in a row. and al... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.6 Targeted advertising | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.6.1 Terminal capabilities for targeted advertising | Terminals supporting the combination of targeted advertising (as defined in ETSI TS 103 736-1 [15]) and application discovery over broadband using watermarks (as defined in the present document) in services received via HDMI shall support the following: • Using a video/broadcast object representing video received via H... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 9.6.2 Behaviour of the Fast Media Switch API with watermarks | The watermark media timeline has units of milliseconds and a limit of 253 ticks. The requirements for comparisons and evaluation of inequality relationships specified in clause 4.2 of ETSI TS 103 736-1 [15] with respect to values on MPEG PTS and TEMI timelines shall also apply to the watermark media timeline. The follo... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10 Capabilities | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10.1 Display model | Video received via HDMI shall be displayed in the "Video plane" in the logical plane model defined in clause H.1 of the OIPF DAE specification [4]. Terminals shall support displaying HbbTV® application graphics in the "DAE application graphic plane" of that model, overlayed on top of video received via HDMI. Terminals ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10.2 Terminal capabilities and functions | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10.2.1 Minimum terminal capabilities | Terminals shall support XML AIT files whose size is less than or equal 256 kB. Terminals may support XML AIT files larger than this. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10.2.2 HbbTV® reported capabilities and option strings | The support of application discovery over broadband shall be indicated by the addition of one or more <applicationDiscovery> elements in the XML device capabilities as defined in clause A.2.1. For example: <applicationDiscovery>urn:hbbtv:discovery:atsc3audio</applicationDiscovery> <applicationDiscovery>urn:hbbtv:discov... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 10.2.3 Performance profiles | The present document defines 3 performance profiles for use in the minimumSwitchPerformanceRequired argument of the switchMediaPresentation method when the present document and ETSI TS 103 736-1 [15] are used in combination. URN broadcast-to- broadband accuracy limit (see clause 4.2.3 of ETSI TS 103 736- 1 [15]) broadc... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11 Security | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.1 Introduction | Application discovery over broadband has been designed to limit risks posed by bad actors. Some known security risks are listed here and recommendations for their mitigation in deployments provided. 11.2 Modification of DVB Service Information or the VP1 Payload of the watermark |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.2.1 Risks | When an application is retrieved via broadband, the terminal determines the hostname of the Broadcaster DNS Root via DNS based on either DVB Service Information received from the tuner or the server_field of a VP1 payload retrieved from an audio watermark. Neither received DVB service info nor detected VP1 payload data... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.2.2 Applicable Application Discovery Methods | • Application Discovery using DVB Service Info • Application Discovery using Watermarking |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.2.3 Mitigation Techniques | The risk of DVB service info or VP1 payload data modification causing a malicious application being discovered can be mitigated by ensuring that the operational processes of the administrator of the hbbtvdns.org domain provide adequate safeguards to prevent the inclusion of DNS records that identify compromised or unau... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.3.1 Risks | During application discovery using watermarks, dynamic event messages carried in the watermarks may be delivered to running broadcaster applications. The watermark-based dynamic event message delivery protocol does not provide message authentication by the terminal. If an intermediary has modified the dynamic event mes... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.3.2 Applicable Application Discovery Methods | • Application Discovery using Watermarking |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.3.3 Mitigation Techniques | Broadcasters can mitigate the risk of dynamic event message modification by an intermediary by implementing dynamic event message authentication in in their HbbTV® application. Methods for dynamic event message authentication include carriage of message authentication codes in dynamic events message watermarks or alter... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.4 Attacks on DNS Resolution | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.4.1 Risks | When an application is retrieved via broadband, the terminal discovers the hostname of the Broadcaster DNS Root server and AIT server using DNS resolution. The specified DNS resolution protocol does not by provide a mechanism for the terminal to authenticate the hostnames received via this protocol in a manner that wou... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.4.2 Applicable Application Discovery Methods | • Application Discovery using DVB Service Info • Application Discovery using Watermarking |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 11.4.3 Mitigation Techniques | The HbbTV® organization can mitigate the risk of compromised DNS resolution by ensuring that the administrator of the hbbtvdns.org domain implement the DNSSEC protocol (IETF RFC 4033 [i.4], IETF RFC 4034 [i.5], IETF RFC 4035 [i.6]). Terminal manufacturers are advised to implement DNSSEC authentication (IETF RFC 4033 [i... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12 Privacy | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.1 Introduction | Application discovery over broadband has been designed to protect the privacy of the end user. Service information and server addresses are generally stored within the terminal and DNS transactions are performed asynchronous to viewing activity in order to reduce information observable by third-parties. The information... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.2 Application Retrieval via Broadband | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.2.1 Risks | When an application is retrieved via broadband, the terminal resolves the hostname of the application server using DNS and retrieves the application from the application server using HTTP over TLS. If the hostname of an application server is uniquely associated with a single broadcast service, the DNS resolution of the... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.2.2 Applicable Application Discovery Methods | • Application Discovery using Broadcast AIT • Application Discovery using DVB Service Info • Application Discovery using Watermarking |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.2.3 Mitigation Techniques | Broadcasters can mitigate this risk by avoiding the use of hostnames or IP addresses with application servers that are uniquely associated with a single broadcast service. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.3 AIT Retrieval via Broadband | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.3.1 Risks | When an AIT is retrieved via broadband, the terminal resolves the hostname of the AIT server using DNS and retrieves the AIT from the AIT server using HTTP over TLS. If the hostname of an AIT server is uniquely associated with a single broadcast service, the DNS resolution of the hostname by the terminal could be used ... |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.3.2 Applicable Application Discovery Methods | • Application Discovery using DVB Service Info • Application Discovery using Watermarking |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.3.3 Mitigation Techniques | Broadcasters can mitigate this risk by avoiding the use of hostnames or IP addresses for AIT servers that are uniquely associated with a single broadcast service. |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.4 Authoritative FQDN Resolution Using Watermarking | |
3a3e023f0bbc7bf133c249f8b740dda6 | 103 464 | 12.4.1 Risks | Authoritative FQDN resolution using data from watermarks is generally performed asynchronously to the viewing of the service carrying that watermark. However, the first time a terminal detects a watermark conveying a specific server_field value, it will perform DNS record resolution using that value. The DNS resolution... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.