openscreenprotocol
openscreenprotocol copied to clipboard
w3c
Open Screen Protocol
This PR addresses #218: Adjust cipher and signature algorithm preference list for hardware. The required-to-implement algorithms in TLS 1.3 are suitable for the vast majority of hardware released in the...
This PR addresses Issue #235: Update SPAKE2 section according to current IETF draft The IETF draft has had several updates since the SPAKE2 section was first written. I am taking...
This addresses Issue #276: Agent Certificate has a circular dependency on itself We can't use the certificate fingerprint as the serial number, because the serial number is embedded in the...
Addresses and closes Issue #327: Representation of time in remote-playback-state The current spec uses the per-frame media synchronization timestamps to control and update the media playback state and handle other...
There are a few things that would simplify the time related fields in `remote-playback-state`. Currently they all use `media-time` which is the internal clock used by the media renderer to...
It seems worth considering the work of the [Media Over QUIC WG](https://datatracker.ietf.org/group/moq/about/), specifically the [Media over QUIC Transport](https://datatracker.ietf.org/doc/draft-ietf-moq-transport/).
@chrisn mentioned in https://github.com/w3c/openscreenprotocol/issues/80#issuecomment-1761745074 > I think that's fine. The original intent behind the suggestion was for OSP to potentially support tightly synchronized playback between agents (e.g., sub 10ms). That...
I was reading the Matter spec an it occurred to me how similar some of the protocol is to OSP. Matter also does mDNS discovery and secure channel using PAKE...
If two agents are using the protocol to manage shared state, and there is a complete network disconnection followed by a reconnection, the spec should have something to say about...
I opened this ticket to continue the exploration of splitting the OSP protocol up into parts: a Connection spec and a Messaging spec. **OSP Connection (OSP-C)** The connection spec would...