[Meta] Open Screen Protocol 1.0 Specification

[mfoltzgoogle]

This meta-issue tracks the work required to complete the 1.0 specification, outlined in PR #97.

• Second Screen Community Group boilerplate (custom or as part of Bikeshed repo)
• Issue [Spec] Complete introduction and requirements section. #99: Complete requirements and terminology sections
• Issue [Spec] Complete Receiver Discovery section. #100: Incorporate material from mdns.md
• Issue [Spec] Complete Transport Establishment section. #101: Incorporate material from quic.md
• Issue [Spec] Complete Authentication section. #102: Incorporate material from j-pake.md
• Issue [Protocol] Hand-rolled binary protocol? #77: CBOR-based Presentation API protocol
• Issue [Control Protocol] Remote Playback API control protocol #12: Remote Playback API protocol
• Issue [Meta] Propose security mechanisms for Open Screen protocol #13: Security and Privacy section

[mfoltzgoogle]

With the closing of Issue #12 we've completed the first draft of the 1.0 protocol. I believe it should meet the functional requirements laid out for Presentation API. We didn't finish requirements for Remote Playback API, but we should do that (Issue #3).

Over the course of drafting the 1.0 spec, there were about 25 issues opened relevant to the spec itself.

What I propose (in this order).

1. Resolve Issue Requirements: Remote Playback API #3 by adding requirements for Remote Playback.
2. Verify that the spec as-is meets the functional requirements of the APIs and relevant non-functional requirements.
3. Close this issue.
4. Tag additional issues with "v1-spec" if they are relevant to producing a more mature spec for wider review. I imagine some of these we will want to discuss at the F2F.

Let me know if this plan sounds good @louaybassbouss @anssiko @tidoust @chrisn (and other contributors).

[anssiko]

Thank you for your efforts and congrats for reaching this significant milestone. The proposed plan sounds good. F2F is a fine opportunity to review and discuss additional issues.