3.1.1 Abstract Data Model

  • Article

 This section describes a conceptual model of possible data organization that an implementation maintains to participate in this protocol. The described organization is provided to facilitate the explanation of how the protocol behaves. This document does not mandate that implementations adhere to this model, provided their external behavior is consistent with that described in this document.

The Sink should be configured with the following global state:

  • Friendly Name: A friendly name for the Sink so that it can be easily identified by the user of a Source device.

  • PIN Verification Enabled: Whether the Sink has enabled PIN verification for the incoming connections.

  • Container ID: A container ID GUID to identify the Sink.

For a given Source device, the Sink should track the following state:

  • State: The current state of the connection establishment protocol, as defined in the diagram below. Defaults to not connected.

  • Security Options: The security options TLV (section 2.2.7.5), if any, received from the Session Request message (section 2.2.4). Defaults to none.

  • DTLS Encryption Key: The key, if any, that is derived from the DTLS handshake. Defaults to none.

  • RTSP Connection: The RTSP connection, if any, to the Source. Defaults to none.

State diagram

Figure 4: State diagram