Merge pull request #16 from webscreens/issue-8-transport-template

Template for transport evaluation

templates/README.md

@@ -0,0 +1,7 @@
+# Evaluation Templates
+
+This folder has a templates with initial criteria to evaluate Open Screen
+Protocol alternatives.  Discussion should not be restricted by the templates;
+when applied, they should be extended as needed on a case by case basis to
+capture all of the relevant findings.
+

templates/transport.md

@@ -0,0 +1,68 @@
+# Transport Name
+
+Describe tranport at a high level here.
+
+# Design and Specification
+
+Add links to specifications and design docs.
+
+# Presentation API functionality
+
+Describe how the transport meets [functional requirements for the Presentation
+API](../requirements.md#req-p2-initiation), especially requirements 2-6.
+
+# Remote Playback API functionality
+
+Describe how the transport meets functional requirements for the Remote Playback
+API.
+
+**TODO:** Fill in when Remote Playback equirements are known.
+See [Issue #3](https://github.com/webscreens/openscreenprotocol/issues/3).
+
+# Reliability
+
+Data describing reliability in different network requirements.
+
+# Latency to establish a new connection
+
+Data on connection establishment latency.
+
+# Latency to transmit a messages
+
+Data on latency of message transmission.
+
+# Ease of implementation / deployment
+
+Including availability of open source implementations.
+
+# Privacy
+
+What device or application information is exposed to network observers by the
+transport?
+
+# IPv4 and IPv6 support
+
+# Hardware requirements
+
+The minimum specifications needed to use the transport, and whether the devices
+in [Sample Device Specifications](../device_specs.md) are sufficient.
+
+# Network and power efficiency
+
+Any data about power and network overhead.
+
+# Standardization status
+
+Describe standardization process, timeline, and link to working group's IPR
+policy, if any.
+
+# Security
+
+Describe security architecture and what encryption and authentication mechanisms
+are supported.
+
+# User Experience
+
+Describe any specific impact on
+meeting [user experience requirements](../requirements.md#req-nf3-ux) not covered
+by the points above.